v2 development
sstaub opened this issue · 4 comments
features for the next release
- Receiver merge DD support following ESTA BSR E1.31-1
- Universe discovery
Hi Stefan, sorry to bother you. I saw that you are working on the implementation of channel priority. I would need some information. I'm developing my own software to drive DMX systems via sacn and I was just wondering, within protocol 1.31 where the byte indicating channel priority was. In the protocol, byte 108 indicates universe priority, but I couldn't find any byte which tells me channel priority. Can you suggest to me which byte should be used to transmit channel priority? thanks and good continuation.
Mario
I made an example for using the library with priority per channel in the example folder.
The priorities are send like a normal DMX packet but send with the start code 0xDD. There is no need extra config.
The source channel priorities will initialized with the default priority 100 (This will changed in future). So can change the simply the channels you want a different priorities.
Here is the document from ETC:
sACN_per_channel_priority.pdf
Stefan,
I used your library for a small button project with a teensy 4.1 that receives sACN and controls a series of LEDs inside the button. I used the QNEthernet library because the NativeEthernet library was not transmitting the group subscribe packets n a large networked system with IGMP implemented. The QNEthernet library does properly transmit the subscribe packet but does not respond to the master queries about subscriptions so looses sACN after a period of time. I made a workaround but thought you would like to know that your library does work with QNEthernet library on the teensy 4.1.
@Druuka Thanks for this advice. I started development for merging. I'm using the W5500-EVB-PICO from WIZnet, but I will also test with Teensy and QNEthernet, because merging with DD start code needs much resources. In larger networks IGMP Snooping and Querier Option must set on the switches.