garageCube

[tobiasebsen]

Hi MadMapper team !

I am currently working on an ArtNet node for controlling LED pixels from MadMapper.

It is working fine in Broadcast mode, but Unicast doesn't work. I am sure that the node sends a reply to the poll from MadMapper (it works in other software), so what can be wrong?
Have anyone else had trouble using the unicast mode?

Thanks!

Tobias

PS: I'm using the free demo version 1.5.3 for testing.

[franz]

We've reworked completely Unicast in 1.6.x
Please try with the latest beta

[tobiasebsen]

Thanks. When will version 1.6 be available as demo?

[franz]

as soon as we finish the final release.
It should have already been released but unfortunately we've had some last time adjustments and final tuning.
We're working hard to release it ASAP. Sorry for the delay.

[Janson]

What is the difference between Artnet code in 1.5.x and 1.6.x?

We are experiencing huge framerate issues when using Artnet Unicast since Madmapper 1.6.x. Our LED stripes always get stuck after one second.

In Madmapper 1.5 everything worked fine.

(We use the Arduino project).

[mad-matt]

Strange. No problem when deactivating unicast ?

[mad-matt]

MM 1.6 is sending at max 44 DMX frames per second, the maximum in ArtNet standard. Maybe your arduino is not fast enough to process all packets... I send you in PM a build with a setting to reduce the ArtNet FPS to test

[Janson]

Ok, cool!

As you mentioned, the Arduino UNO is not capable of high framerates. We built a huge installation with 8 arduino ethernets (which ist actually an arduino uno with ethernet on board) about a year ago, so we do not want to buy new epensive arduino megas and ethernet shields.

I will test the version you send this weekend and let you know the results. Thanks for your help so far


By the way: Artnet BROADCAST never worked for us, even not in MM 1.5.

[mad-matt]

Ok. It certainly doesn't work because your ArtNet library doesn't support read the broadcast address.
Are you using a single ArtNet universe ?

[Janson]

Sorry, I wrote a litte misunderstandable. Broadcast in general worked, but our LEDs hang in MM 1.5 and MM 1.5.

Unicast in MM 1.5 worked, but in MM 1.6 our LEDs hang.

We use 7 Universes, sometimes 8. I will test your version an keep you up to date

[mad-matt]

Ok. So if you use 8 universes, in broadcast, each device will receive 8 time more artnet packets than in unicast mode. That's why to get things working with your arduino you need to use unicast.
With 1.6 we send more artnet frames per second, which in general is good for fluidity, but not good for your arduino setup... Let me know if limiting the FPS with the version I sent you solves.
Matthieu

[Janson]

As far as I could test it, the Beta you send me did not work.

I tested it with 33 and even with 25ms. No Luck

Do I have to enter the terminal commad before starting Madmapper? Do I have to "sudo" it?

I will do another test these days and report back.


Regards,

Jan

[mad-matt]

Ok so that's not because of the ArtNet FPS. More simple: does MM send packets to the device ?? If the device has not been added to the ArtNet unicast routing table, MM will not send packet to it. Normally, ArtNet devices are added automatically because MM broadcasts an ArtNet POLL to which any ArtNet device on the network should reply with some info about theselves. But if your arduino library doesn't, you have to add it manually (IP address, ArtNet subnet/universe) should be added.

[Janson]

Hi,

I will check that with wireshark. However our Artnet Nodes answer to poll requests and appear in the List of Nodes. I already tried to manually add the devices for testing, but it doesn't help. The LED Stripes keep freezing after 1 to 3 seconds and recover when no pixels are changing.

[mad-matt]

> Do I have to enter the terminal commad before starting Madmapper?

Yes you have to enter it once and then start MM. But you don't need to do it before each MM startup.
Did you test after having changed this "hidden setting" (and with the build I sent you) ?