I have four Etherdreams connected to Liberation. Three of them are fine. One shows up in the available controller list and can be assigned to a laser but shows red status and doesn’t output anything.
I’m pretty sure it was working with MadLaser but I don’t have that to hand to test. Could it be a firmware issue? What things can cause red status but still see and identify the controller?
I’m running on an APIPA network (my MadLaser rig has a DHCP server so that’s one difference) and I’ve tried connecting to different ports, and also in isolation
No this isn’t my full rig as it’s on a second stage (actually a pyro truss) so I’m running APIPA. I statically assigned the Macintosh and ArtNet boxes in 169.254.x.x and left the Etherdreams to generate their own. They should check for a collision if they implement the spec correctly. Liberation can see the problematic controller and shows its UID so I don’t think it’s a network issue. I can try throwing in a DHCP server incase there’s something I haven’t thought of.
Glad you got it sorted @RobV ! Honestly it seems like 90% of the work on my installations is network troubleshooting. Who knew that being a laserist is mostly the same as being IT support…
Seb is sick of me harping on about this, but I hate DHCP and use static all the time. Not had any network issues with my etherdreams, I had similar issues with a DHCP server on my network with older network enabled controllers and setting static fixed all issues instantly. Aside from anything else ,having a router in the setup is another piece of kit to rig/forget/go wrong.
Rob
I agree with you in general, but static can be hard to manage with a lot of hired in fixtures, or sometimes house fixtures since native DMX is becoming less of a thing. For my lighting and video rig I run DHCP from an Ubiquity router that’s permanently installed in my console flightcase and assign permanent addresses to all my own fixtures and servers. Seems to work out but my gigs are pretty small.
The good to come out of my problem yesterday is I now have my Etherdreams on much more recent firmware, and I’m no longer putting tight radiuses into patch cables in rack cases!
I can see the benefit of static IPs (and it does seem to be somewhat of a standard in entertainment industry networks) but I have so many ether dreams (over 50) and often add other people’s lasers / ether dreams to my shows as well.
If it was easier to set the IP address of the ether dreams (particularly when they’re inside lasers) then it would be less of a problem.
Can we get back to talking about cool laser things now please?
