Lonet not connecting to Aximmetry

bsmith

Stopped production for a few weeks with the indiemark 2 encoder working before with Aximmetry but now it doesn't with no obvious changes made to the system. Before, we were using lonet 2.7 AND 2.6.2 as both would intermittently stop working. Do you have any suggestions or insight as to what could be causing inconsistent connection? Let me know all what information I can provide to give more clarification on this issue.

Windows firewall and antivirus is NOT blocking the lonet software, glassmarkserver, etc.

AndyJarosz

bsmith Double check the selected network interface (top of LONET) as it may have reset itself.

As a troubleshooting step, try sending the data as a broadcast (send to 255.255.255.255) out of LONET.

Also--you can try the new LONET3 beta, as it's completely re-written from scratch and you might find it more reliable.

bsmith

Thank you for the reply, we just got our licensing situation figured out recently and gave that a try today. So far it hasn't worked.

These are some of the troubleshooting steps we have taken:

Have used LONET 2.6.2, 2.7, and 3beta all with the same version of Aximmetry (2024.3.30 and 2025.1.0 BETA)
Confirmed Aximmetry and LONET are listening on the correct port both individually open and running simultaneous
Tested Aximmetry to listen for the lens encoder values from LONET on the ethernet and localhost adapter, no input received from encoder
Confirmed no other services are conflicting with ports used
Confirmed no issues with multicast IP
Again, confirmed firewall isn't blocking any traffic

Under the Aximmetry Broadcast DE license we used the basic calibrator and composer to test lonet device connection. LONET2 was used for everything including toggling the send lonet2 box in the LONET3 beta version.

IP Configs:

Multicast: 236.12.12.12, 255.255.255.255
Adapter: localhost (127.0.0.1), Ethernet (192.168.1.99)
Port: 60608, 60609

AndyJarosz

bsmith
Really interesting. Two things that would be super helpful:

Try the LONET Unreal plugin (or trial of Cinelink) and see if you can see the data in Unreal. That would at least narrow down the problem to Aximmetry then.
You can also download Wireshark and add a "udp.port == 60608" filter to see the LONET traffic. This is less helpful for troubleshooting but will at least tell if you if the data is being emitted.