HTTP Remote IP configuration
Moderator: MADRIX Team
-
steve@eoslightmedia
- Posts: 19
- Joined: Fri Dec 10, 2010 12:23 am
HTTP Remote IP configuration
We have a large Madrix / Artnet installation with 40 universes which we are controlling with the HTTP remote. The HTTP calls are being lost in the network traffic due to all the art-net packets being sent.
We are going to add a second ethernet port to our device and we need to be able to switch the IP address of the HTTP remote to our second IP device. Is there a configuration file where we can set the default address of the HTTP remote?
We are going to add a second ethernet port to our device and we need to be able to switch the IP address of the HTTP remote to our second IP device. Is there a configuration file where we can set the default address of the HTTP remote?
Re: HTTP Remote IP configuration
Ok,
some words about network, Art-Net and remote http.
If MADRIX remote http is enabled MADRIX listen to all network ports. So if you have two network devices installed MADRIX will react on each http remote call.
This means it is not necessary to tell MADRIX a default IP address for remote http.
But we gues you issue has a different reason.
If your http remote calls are lost because of the bunch of Art-Net packets it seams your windows network socket has a overflow. The reason for this could be a too small memory on the network device you have installed.
If so, a second network card for remote http will not solve your issue and we recommend to install a new network adapter with more memory.
Or, in case you send Art-Net in broadcast it would be a solution to change this into direct ip mode to reduce the traffic dramaticaly
some words about network, Art-Net and remote http.
If MADRIX remote http is enabled MADRIX listen to all network ports. So if you have two network devices installed MADRIX will react on each http remote call.
This means it is not necessary to tell MADRIX a default IP address for remote http.
But we gues you issue has a different reason.
If your http remote calls are lost because of the bunch of Art-Net packets it seams your windows network socket has a overflow. The reason for this could be a too small memory on the network device you have installed.
If so, a second network card for remote http will not solve your issue and we recommend to install a new network adapter with more memory.
Or, in case you send Art-Net in broadcast it would be a solution to change this into direct ip mode to reduce the traffic dramaticaly
LEDs are nothing without control
-
steve@eoslightmedia
- Posts: 19
- Joined: Fri Dec 10, 2010 12:23 am
Re: HTTP Remote IP configuration
Thanks for the reply.
My instinct tells me that you are correct: that http remote calls are lost due to the art net packets.
I am not currently on site to test your solution at the moment. However, we have been able to solve this issue in the past with another lighting controller that has two separate ip addresses and ethernet ports. The network control traffic is then isolated from the art net traffic -- 40 universes of art net at 50 frames per second is a lot of traffic and a single remote command can get dropped.
If we need to, can we reconfigure Madirx to use a separate IP for the remote commands. Perhaps the development team can release a custom version for our installation that isolates the http remote ip from the art net output.
Please let me know, we will need to have a working solution rather soon -- as this installation has a set opening date.
My instinct tells me that you are correct: that http remote calls are lost due to the art net packets.
I am not currently on site to test your solution at the moment. However, we have been able to solve this issue in the past with another lighting controller that has two separate ip addresses and ethernet ports. The network control traffic is then isolated from the art net traffic -- 40 universes of art net at 50 frames per second is a lot of traffic and a single remote command can get dropped.
If we need to, can we reconfigure Madirx to use a separate IP for the remote commands. Perhaps the development team can release a custom version for our installation that isolates the http remote ip from the art net output.
Please let me know, we will need to have a working solution rather soon -- as this installation has a set opening date.
Re: HTTP Remote IP configuration
Hi Steve,
How is the current status of this. Have you tried some of the suggestions?
- You could try using two, separate network cards. But if the network stack in Windows overflows indeed, this won't help either.
- A new network adapter with more memory could help
- You can activate Direct IP Mode for Art-Net in order to reduce the network traffic.
- When using one network card, there is no way to isolate Art-Net or Remote HTTP data from each other, because the data flows through one cable/socket
- The Windows firewall of the device receiving the remote HTTP commands might be configured in such a way that it dismisses Art-Net data
Thanks!
How is the current status of this. Have you tried some of the suggestions?
- You could try using two, separate network cards. But if the network stack in Windows overflows indeed, this won't help either.
- A new network adapter with more memory could help
- You can activate Direct IP Mode for Art-Net in order to reduce the network traffic.
- When using one network card, there is no way to isolate Art-Net or Remote HTTP data from each other, because the data flows through one cable/socket
- The Windows firewall of the device receiving the remote HTTP commands might be configured in such a way that it dismisses Art-Net data
Thanks!