Lasercube with build 0.7.3

Testing the lasercube protocol out and I am seeing some weird behavior…

LaserCube 2.5 Ultra connected via an ethernet switch to Win10 pc with Liberation build 0.7.3
I put the LaserCube in LAN Client mode per the guide and while Liberation recognized the DAC and seemed to indicate everything was working, I could not get any output.

I then changed the LaserCube to LAN Server mode, and now I’m getting output (although, when I press the button on the back of the LaserCube to make it show firmware, IP, mode, etc - nothing happens now & the button won’t work again until I cycle power on the cube).

So I guess my question is, is this just a typo in the wiki or is there something deeper going on here?
Thanks!

Hey Ian,

Do you have a router on the network as well as a network switch?

The behaviour you’re describing would happen if your computer is on a different subnet from your LaserCube, and this would happen if there was no router giving out IP addresses (via DHCP).

When the LaserCube is in “server mode” it acts as a DHCP router and will give your computer an IP address itself.

cheers!

Seb

The laser was just connected to a Linksys SE2800 switch, which was wired to my RJ45 port on my laptop.
Separately my wifi was still connected to my home network - I thought my laptop would set those two up as separate things, but maybe not? I only have a surface-level knowledge of networking.
Or are you saying I need a router in there too that the lasercube is on?

I understand. Networking is unfortunately something that is really important to learn - I bet you never expected so much network IT support when you were dreaming about becoming a superstar laserist huh? :sweat_smile:

IP addresses need to be on the same subnet

For your computer and laser to talk to each other they need to be on the same subnet. That’s just a fancy way of saying that their IP addresses need to have the first three numbers matching. So :

192.168.1.100 and
192.168.1.52 are both on the same subnet.

Whereas
192.168.1.100 and
192.168.0.52 are not, because the first three numbers don’t match.

How do the devices get an IP address?

It depends on how your network is set up. The options are :

1 - Add a router to your network

If you have a router on your network, it will likely be set up as a DHCP server, and this DHCP system gives out IP addresses to devices on the network that ask for it.

This is my preferred set up as you don’t have to worry about any IP conflicts and it’s flexible. You will need to make sure that all your devices are set up to use DHCP, this is the default with Ether Dreams, and LaserCube “LAN client” mode will do this.

2 - Use fixed static IP addresses

Without a router on your network (or other DHCP server) then nothing is giving out IP addresses. (Note that a switch is not the same thing as a router but if you have enough ports on your router, you don’t also need a separate switch.)

For this to work, you need to make sure that every device on the network has a fixed IP address on the same subnet. (I’m not sure you can even do this on LaserCubes and on Ether Dreams it’s fiddly)

You will also need to set up your computer with a fixed IP address. (And then remember to disable that when you try to connect to another network!)

This set up is very common in the events industry, and if it were easier to change the static IP addresses on Ether Dreams I would be happier about recommending it. But I personally find it error prone, and I just have less trouble by bringing a cheap router.

3 - Use one of your LaserCubes as a DHCP server

If you put one of your LaserCube in ‘LAN Server’ mode then it does the job of issuing IP addresses to all of your devices, even your computer. So this is why it worked for you when you didn’t have a separate router.

I don’t think there’s anything really wrong with this set up, but I haven’t tested it much. I guess there are a few possible pitfalls with this set up, if there’s already a router on your network then there could be conflicts. And you need to make sure that only one of your Laser Cubes is the LAN server, and all others are LAN client.

But let me know how it works for you!

They are separate things. On Mac you can set the network priority list and I think Liberation uses the top network on this list when it starts up. On Windows, I’m not really sure, sorry!

I hope this is helpful.

Seb

This is super helpful Seb, thank you!
I will test out the #3 option a bit and report back. in addition to using #1 as you suggest.

1 Like

Following up here, I ran the new beta version with configuration #3 above for 7 hours on Friday with no issues whatsoever. Interestingly when I wired the lasercube straight into the RJ45 port on my laptop, liberation didn’t recognize it in either lan server or client mode - when I put a switch (not router) in between with lasercube in lan server mode, liberation recognized it.

Amazing!

Very strange, there shouldn’t functionally be any difference whether there’s a switch between or not, but it would never work in client mode without a router.

But in server mode it should work. But I strongly suspect a network set up issue rather than a Liberation bug - but next time also try with LaserOS and see if there’s a difference.

As ever my recommendation - if you’re not very experienced with networks, always use a router!

Thanks!

Seb

Got to play with some more networking things tonight, including having a couple of Etherdreams in the mix…

-Can confirm, with Lasercube in LAN server mode wired straight into the laptop, Liberation is not seeing the DAC, however it’s working fine in LaserOS. Once I put a switch in between, Liberation then sees the DAC. LaserOS works both ways.

-Separately I tested a network with one Lasercube in LAN client mode plus 2x Etherdreams plugged into a router, everything was happy & Liberation found them all.

-Also separately and just out of curiosity I tested a network with one Lasercube in LAN server mode, 2x Etherdreams, and a laptop all plugged into a switch, and Liberation was still happy and found everybody.
Not sure I’d want to rely on that but seems like a good workaround to keep in the back pocket when the router dies or never gets thrown in the truck!

1 Like

Hi @Enablers.inc, thanks for your continued testing!

I’ve tried this exact set up :

  • Cube in LAN server mode
  • Connected directly to the computer’s network socket (in my case a USB-C adaptor)

On a Mac this worked straight away. On Windows, it would only work if I disabled the WiFi, could be a network priority list thing? Same for both Liberation and LaserOS. In fact I could rarely get LaserOS to see the laser at all, whether it was via a switch or not.

I feel like there’s some Windows networking things that I don’t fully understand, so that’s something to look forward to!

In the meantime, do whatever works, but adding a router is recommended. :grinning:

Seb