search

xLightsSequencer / xLights

xLights is a sequencer for Lights. xLights has usb and E1.31 drivers. You can create sequences in this object oriented program. You can create playlists, schedule them, test your hardware, convert between different sequencers.
GNU General Public License v3.0
554 stars 209 forks source link

xlights crashes with servo effect. #1956

Closed shanerehm1234 closed 9 months ago

shanerehm1234 commented 4 years ago

I had xlights crash on me repeatedly when adding the servo effect to the DMXSkull model in the sequencer. it only seems to happen with the skull model is configured with only the "Jaw servo" box checked. When all the options are checked (except 16-bit and Skulltronics) it works great!

XLights version 2020.6 64-bit

image

jjewell66 commented 4 years ago

I'm having xlights crash every time I import a VSA file. Newest version. Standard skull model. xLights_dbgrpt-16564-20200317T115554.zip

AzGilrock commented 4 years ago

Shane - When you use the Servo effect is the 16-bit box checked in the effect settings? It sounds like you are telling it to write 16bits of data to the model but you only have an 8bit Jaw servo defined. The effect is dumb it's not trying to see how many bits are on the servo.

jjewell66 commented 4 years ago

I’m not Shane.. but I have it defined as 16 bit. With the latest xl update I’m getting no movement at the servo when in sequence mode. Xl is sending data. FPP is receiving data but no servo movement. Servos move under xl test mode and FPP test mode. So communication is there. I had Ed look also and he was baffled.

Jerry Jewell Skulltronix.com 916 600 2295

On Mar 17, 2020, at 1:59 PM, Gil Jones notifications@github.com wrote:

 Shane - When you use the Servo effect is the 16-bit box checked in the effect settings? It sounds like you are telling it to write 16bits of data to the model but you only have an 8bit Jaw servo defined. The effect is dumb it's not trying to see how many bits are on the servo.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

AzGilrock commented 9 months ago

Almost 4 years old so I'll assume this is sorted. Otherwise open a new issue and reference this one.