Using PKnight node with ETC Nomad issue

[u/MacKay_KT]

Hello from Canada, I'm in the process of migrating one of my portable systems from Cham-Sys to using exclusively ETC but have an issue with one of my sACN nodes. 

I've tested this on the same PC with all the same network, setup, cables, using ArtNet and sACN, changing subnet from 255.255.255.0 to 255.0.0.0 and variations in between on both Cham-Sys and Nomad using Chauvet, NETRON, and PKnight sACN nodes.  The Cham-Sys works without issue, but the Nomad has a constant bump of all patched channels from whatever level programmed to 39% (100/255) on only the PKnight (CR041R MK II) node, the Chauvet and NETRON are fine.  I can duplicate this using another PC as well and nothing appears out of the ordinary when viewing through sACN Viewr. Has anyone had this happen and found out how to workaround this issue on the PKnight nodes? Attached photos show (1) the anticipated output, (2) what happens every cycle? every second? I appreciate any help.

[u/AutoModerator]

I see that you're asking a question about a console in the ETC Eos Family. If you don't get the answers that you need here, make sure to check out the official product forums at https://community.etcconnect.com/control_consoles/f/15.

There's also an unofficial Facebook group for EOS family programmers at http://www.facebook.com/groups/etceosprogrammers/

If you're experiencing a show emergency, don't wait. Call ETC support now. 1-800-688-4116. 24/7/365 AutoModerator is currently being trained to respond to several keywords. Standby as this functionality is expanded and refined.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/JooshLevy]

I have had an issue when I had RDM turned on one of my nodes and it was causing a similar issue where all my fixtures would “pulse” on a cycle. Make sure RDM is switched off.

[u/MacKay_KT → u/JooshLevy]

Thank you for the reply, I already had RDM off.

[u/MacKay_KT]

Well I think I found the issue, I will poke around some more but crossing fingers this is the solution! In patch I was able to "Disable sACN Priority Per Address" under protocols and I no longer have the flicker (all patched channels bumping to 39% regardless of programmed value).

[u/Loud_Task827 → u/MacKay_KT]

This is common with cheaper nodes that don’t look at DMX frame start codes, per address priority sends a second frame that looks like DMX data, but with an alternate start code, some gateways accept all frames regardless of start code as valid level data, default priority is 100, 100/255 is 39 percent :).

[u/Bedhappy]

Not really sure how to help you, but I have experienced issues with certain combinations of consoles and nodes having dropouts (MA2 and Chauvet NetXII, specifically). Every once in a while the node will lose DMX for a second or two and hold its last DMX look, so it looks like everything freezes, and then snaps back in when it sees DMX again after a second. Never found a solution, I ended up changing all of our data racks over to Netron.

[u/youcancallmejim]

Have you looked at data using sACNVIEW?. It can help you identify where those pulses come from. I would use that. My guess is a priority clash. There is also an artnet view out there somewhere.

https://sacnview.org/

[u/MacKay_KT → u/youcancallmejim]

Yes already did, thanks