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
549 stars 209 forks source link

6 Ch Realy Board DMX address not receiving data #1012

Closed DGHayes closed 6 years ago

DGHayes commented 6 years ago

Have a weird problem I seem to have narrowed down to the layout configuration from xLights. Using this board: https://www.facebook.com/photo.php?fbid=10155666655268046&set=gm.1559512484129240&type=3&theater&ifg=1

I had the start address set to 73 via the dip switches (next address free in my setup) and the board worked fine using the test output from xLights.

Setup two models (it just switches 24V AC out to them via the relay board) and test went fine and added to sequence and it also worked.

Next day after all equipment powered down, these two props didn’t work, nor did they respond to the xLights test function. So, I changed the DMX start address to 128 (have nothing in that range on my setup) reprogramed props for new DMX address (128/129) and all worked again including the sequence output.

Next day same thing happened, not working after shutdown. The board is receiving the data stream and the data light is flashing. Knowing I had data for another model coming out on DMX channel 1 & 2, I simply changed the dip switch address on the relay board to channel 1, and the relays turned on, proving the data steam was OK and the board was getting data.

Next, I changed the models to another DMX channel after resetting the board to address 128, i.e. I set the models to 131 and 132 (any number works here), saved the props, reedited back to the original DMX 128/129 channel, save and run xLight test, and it worked. Also, sequence worked OK after this.

Confirmed this tonight as xSchedule started the show, no relay board working, so did the above procedure, (save models to an unused channel and then back to the correct ones), and xLight test work and just turned on the lights output from xschedule as the show was running and it worked fine.

Not sure why this needs to be reset every day, but hence this post with a strange issue. Logs attached from shortly after the changes to the models and back again tonight.

Thanks in advance, Dave

xLightsProblem.zip

keithsw1111 commented 6 years ago

Looking in your file your networks setup only shows 129 channels configured ... surely this should be more ... in fact I would suggest you just make it 512. I suspect this is your problem but it is impossible to know for sure.

DGHayes commented 6 years ago

Hi Keith, I'll set it to 512 and test, but the reason I only have 129, is that I have two x 36 ch Hanson DMX boards (1-36 and 37-72), one 3 ch relay board (not connected) and one 6 ch (128-133) relay board and one DMX smoke/bubble machine 8 channels (100-107). Very simple setup. Is there a way to capture the data stream (like Ethereal for TCIP packet sniffing) you would recommend? I was looking at using https://freeserialanalyzer.com/ to see if it gave any clues. Using a USB to DMX dongle on Comm port 4.

keithsw1111 commented 6 years ago

You can download virtual comm port software which has the ability to sniff the data. Product names I dont remember. All of them cost money but have free periods which can give you enough time to troubleshoot.

keithsw1111 commented 6 years ago

Right ... so its set to 129 ... but you are using up to 133 ... I see a problem.

DGHayes commented 6 years ago

True, but only using 128 and 129 (first two relay channels), so hence not set to 133. I'll set to 512 tonight so all are covered and let you know if this fixes the data stream issue.

DGHayes commented 6 years ago

Do I need to redo the FSEQ files after the changes to the setup (networks file) Keith?

keithsw1111 commented 6 years ago

Yes

DGHayes commented 6 years ago

Hi Keith,

Have not nutted this one out yet.

Friday I changed the setup to 512 and the show ran (no redo of the FSEQ file).

Saturday, I modifed the two show files and the show refused to run both the relay board (128/129) and the DMX smoke machine (100-107) from the scheduler, but the lights test worked and so did the xLights sequencer output, so ended up looping just one show from the sequencer for the night.

Sunday, deleted and re-added the two show (FSEQ) files to the scheduler, show started but no realy or DMX smoke machine output. Left the scheduler running and turned off the lights output, fired up xLights and used test light function to test the two relay channels 128/129, and they worked (note: did not test the DMX machine output), exited xLights and just turned back on the light output from the scheduler, and both the relay board and DMX smoke machine now worked!

So from the Sunday test, just turning off the scheduler light output, testing two channels and turning on the light output from scheduler, all worked. Will see what it does tonight with no changes at all.

keithsw1111 commented 6 years ago

Whenever you have issues you need to run Check Schedule and verify you get a clean bill of health.

In order for your xLights vs xSchedule test to be valid:

  1. You should be running on the same machine
  2. Both xLights and xSchedule must be using the same show directory ... this is because we look at the xlights_networks.xml to decide what to send out.
  3. You must be pointing to the right FSEQ file. FSEQ files are only created when you render all and save a sequence.
  4. Clicking on an effect while ouputting to lights is not necessarily a representation of what will be displayed. Render all then play to see what it actually looks like.

We know this works so there is something you are doing but not communicaying which is likely causing the issue.

If you jump into zoom we may be able to see what and help.

DGHayes commented 6 years ago

Hi Keith,

Check Schedule = Check sequence done, Errors: 0. Warnings: 0 for both files 1 = Yes it is (default) user home documents 2 = Yes they are 3 = Yes and have re-rendered files 4 = Understand, have done that too

On Zoom meeting now

keithsw1111 commented 6 years ago

Check sequence is not the same as check schedule. They do different things.

I cant jump in for at least 30 mins now.

DGHayes commented 6 years ago

OK, will stay on. Check schedule = Errors: 0. Warnings: 1, warning is No password set on website

DGHayes commented 6 years ago

This is the update from the xScheduler tonight. Had set light output to off (as it does not turn off as noted at end of show), show started but relay board (128/129) didn't start. Simply turned off the light output and then back on in xSchedule and the relay board worked. So as you said Keith, resetting the port by turning the output off and on worked.

Will now load the special software revision for data logging you have sent via Dropbox.

DGHayes commented 6 years ago

So after applying your custom build of xSchedule (V40) and the map file to the location specified, started the new scheduler, the show resumed as was programmed to start at 7:30 and the relay board didn't work. Again turned off the output to lights in the scheduler and back on, relay board functioned again.

So if there is a log file you need, please let me know which one? Time is just after 8 in the logs.

keithsw1111 commented 6 years ago

I need the xSchedule log

DGHayes commented 6 years ago

xLightsProblem_1012.zip

xSchedule_l4cpp.log

DGHayes commented 6 years ago

Log position for new debug is: 2017-12-11 19:58:55,155 8512 log_base [INFO] Version: 2017.40

Light output turned off and on (fixes relay board): 2017-12-11 20:02:14,224 8512 log_base [DEBUG] Serial port COM4 closed. 2017-12-11 20:02:19,964 8512 log_base [DEBUG] Opening serial port COM4. Baud rate = 250000. Config = 8N2. 2017-12-11 20:02:19,973 8512 log_base [DEBUG] Serial port COM4 open.

Did not turn light output off (bulb icon still Green) at: 2017-12-11 22:01:05,169 8512 log_base [DEBUG] Turning all the lights off. (Noticed here that COM4 is not closed by program)

Manually turned off light output in scheduler (bulb icon Red):

2017-12-11 22:57:00,223 8512 log_base [DEBUG] Active scheduled playlists: 0 2017-12-11 22:57:08,186 8512 log_base [DEBUG] Viewing log file C:\Users\david\AppData\Roaming/xSchedule_l4cpp.log. 2017-12-11 22:57:18,078 8512 log_base [DEBUG] Serial port COM4 closed. 2017-12-11 22:57:21,643 8512 log_base [DEBUG] Viewing log file C:\Users\david\AppData\Roaming/xSchedule_l4cpp.log.

keithsw1111 commented 6 years ago

Ok. Need to add some more logging which I will do tonight ... but it wont be later.

DGHayes commented 6 years ago

Interesting, not touching the setup came home tonight and the relay board is active. This is after the on/off/on from the prevoiuse day.

keithsw1111 commented 6 years ago

David ... no word on this for some time. Does that mean we resolved it?

DGHayes commented 6 years ago

Hi Keith, Sorry, been away and only got back last night. The problem seems to be related to opening and closing the USB port. If you (either in xLights and xSchedule) turn the lights on/off/on, the board will work. I haven't upgraded from version 40, where I see you fixed the port not closing in the scheduler in V41. That will be my next test, upgrade to the latest and then try a program change, re-render and set in the scheduler. Once the scheduler is running and the on/off/on is done, it will work until any changes are done.

keithsw1111 commented 6 years ago

An upgrade and retest would be in order ... let me know how it goes?

keithsw1111 commented 6 years ago

Can I close this one now?

DGHayes commented 6 years ago

Yes please Keith, I have not had time to test as I'm in Coffs looking after my Uncle with a terminal disease. I'll reopen if needed.

Sent from my iPad

On 15 Mar 2018, at 2:35 PM, Keith Westley notifications@github.com wrote:

Can I close this one now?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.