marktwoengage
New member
Hello.
I'm currently struggling with Renard output. Occasionally, output frame contains zeroes in value bytes (protocol service bytes like sync and command are ok), which makes LEDs to flicker for a moment.
I have encountered this trouble in v3.7u1, and in v3.7u4 it's still present.
In my setup i use NRF52840 MCU with USB CDC in it, it parses output data internally and sends it via radio to device which outputs received data to LEDs. MCU enumerates as serial port in my system. Then this port is set in Renard display in Vixen. Display uses 381 channels.
Seems like problem reproduction rate does not depend on baud rate or execution engine refresh rate (but with slower rate i get less frames overall, so i encounter less zero frames), nor it depends on display size, effects used or any other condition i thought of so far, and it happens as often during show playback as with effect preview.
I've done some debugging in my device's firmware, it does not seem like it's USB stack or internal (in device firmware) Renard protocol parser are at fault here. I've also tried to redirect output to terminal viewer program via com0com driver and issue is reproducing there - i can see sometimes i get zero frames there as well.
I can reply with data capture i've managed to get with realterm if someone needs it, but from what i can tell about it - zero frames just happen, without any kind of change in previous or next frames.
I have also tried to set up display as Generic Serial with data header and footer but for some reason Vixen struggles with device's serial port. It does not open it properly, freezes on start/stop in display menu and no data flow happens, so i eventually went back to Renard since it is the only working option i have for now. Directing Generic Serial to software defined port (via com0com) and capture output in realterm seems to work okay and sending data to device from terminal program also works, so it seems like device USB CDC drivers are working properly and i'm not sure what causes Vixen to behave like it does, but i would like to focus on Renard for now.
I have not tried to use other USB devices like USB-TTL converters, since i see that even COM port emulation encounters this same issue.
I'm currently struggling with Renard output. Occasionally, output frame contains zeroes in value bytes (protocol service bytes like sync and command are ok), which makes LEDs to flicker for a moment.
I have encountered this trouble in v3.7u1, and in v3.7u4 it's still present.
In my setup i use NRF52840 MCU with USB CDC in it, it parses output data internally and sends it via radio to device which outputs received data to LEDs. MCU enumerates as serial port in my system. Then this port is set in Renard display in Vixen. Display uses 381 channels.
Seems like problem reproduction rate does not depend on baud rate or execution engine refresh rate (but with slower rate i get less frames overall, so i encounter less zero frames), nor it depends on display size, effects used or any other condition i thought of so far, and it happens as often during show playback as with effect preview.
I've done some debugging in my device's firmware, it does not seem like it's USB stack or internal (in device firmware) Renard protocol parser are at fault here. I've also tried to redirect output to terminal viewer program via com0com driver and issue is reproducing there - i can see sometimes i get zero frames there as well.
I can reply with data capture i've managed to get with realterm if someone needs it, but from what i can tell about it - zero frames just happen, without any kind of change in previous or next frames.
I have also tried to set up display as Generic Serial with data header and footer but for some reason Vixen struggles with device's serial port. It does not open it properly, freezes on start/stop in display menu and no data flow happens, so i eventually went back to Renard since it is the only working option i have for now. Directing Generic Serial to software defined port (via com0com) and capture output in realterm seems to work okay and sending data to device from terminal program also works, so it seems like device USB CDC drivers are working properly and i'm not sure what causes Vixen to behave like it does, but i would like to focus on Renard for now.
I have not tried to use other USB devices like USB-TTL converters, since i see that even COM port emulation encounters this same issue.