MADRIX Forum

From ArtNet spec:

The ProtVer field is a 16-bit word transmitted high byte first. It identifies the version of the Art-Net protocol. The protocol version is not related to Art-Net 1, II, 3 or 4. Only one protocol version has ever existed in production equipment which is 1410. Receivers should use the following good packet test:
ProtVer >= 14

Due to some simple tests were found that NEBULA (FW ver 3.03.7390) doesn't work with ArtNet DMX packets with ProtVer = 0.
Is it possible to bypass this limitation in the newest version of NEBULA firmware? Some ArtNet devices generate packets with ProtVer 0 and because of this not possible to use NEBULA in the installation.

Currently, we have installation for 16u and thinking about NEBULA replacement
It would be nice to bypass it somehow, any hints are welcome

Hi!

Thank you for your question.

The latest Art-Net protocol specifications (Art-Net 4, Document Revision 1.4dd2 1/2/2021) are very, very clear in this matter. In them, I also could not find your quote. Here is what is written down:
"Low byte of the Art-Net protocol revision number. Current value 14. Controllers should ignore communication with nodes using a protocol version lower than 14."

To answer your question: No, please do not expect a change in the firmware of MADRIX NEBULA. The device behaves correctly according to the specifications.

That begs the question why some/your devices generate ArtNet DMX packets with ProtVer = 0?
MADRIX NEBULA does support Streaming ACN. Would that be an alternative?

Ok, clear.
ACN is not an option for this project.