dpitts / f16v3_issues

Track issues for F16V3 software
12 stars 0 forks source link

Serial port issues #76

Open PeteyHall opened 5 years ago

PeteyHall commented 5 years ago

Upgraded most of my controllers to 2.51 this weekend without issue and at the same time, I tried adding a new DMX moving head light to the show but it looks like something may be wrong with 2.51 and the serial ports.

As a basis for my issue: My 2.51 f16v3 controller was set to e131 mode and I added the correct universes and channels where appropriate on the controller. The DMX head was plugged into DMX2 using an RJ45 -> XLR connector.

When I did test mode on the controller itself, the head worked as expected but when I tried to control the head through Xlights, the controller was seeing the traffic (as the counter on the main status screen was going up) but there was no output to the moving head. I made sure all of the ports/configs were set properly in Xlights but no matter what I did, I couldn't get it to work. I then went onto the controller test mode and even though the head was plugged into DMX2, Serial 4 was the only one that would provide output.

As a test, I did this on multiple controllers running 2.51 and had the same problem every time.

I took one of my original firmware f16v3, made the same configuration changes as on the other controllers, plugged the head into DMX2 and this time it worked perfectly through Xlights!

It appears that others are seeing the same issue on the Facebook pages.

dpitts commented 5 years ago

Hi

I would update to 2.52 because of an output issue with 2.51 for SmartReceivers. I ran several DMX tests with 2.52 last night and saw no issues. The DMX code was not changed in 2.52. You can call me and we can try to resolve your issue.

David

From: PeteyHall notifications@github.com Sent: Tuesday, August 27, 2019 2:48 PM To: dpitts/f16v3_issues f16v3_issues@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [dpitts/f16v3_issues] Serial port issues (#76)

Upgraded most of my controllers to 2.51 this weekend without issue and at the same time, I tried adding a new DMX moving head light to the show but it looks like something may be wrong with 2.51 and the serial ports.

As a basis for my issue: My 2.51 f16v3 controller was set to e131 mode and I added the correct universes and channels where appropriate on the controller. The DMX head was plugged into DMX2 using an RJ45 -> XLR connector.

When I did test mode on the controller itself, the head worked as expected but when I tried to control the head through Xlights, the controller was seeing the traffic (as the counter on the main status screen was going up) but there was no output to the moving head. I made sure all of the ports/configs were set properly in Xlights but no matter what I did, I couldn't get it to work. I then went onto the controller test mode and even though the head was plugged into DMX2, Serial 4 was the only one that would provide output.

As a test, I did this on multiple controllers running 2.51 and had the same problem every time.

I took one of my original firmware f16v3, made the same configuration changes as on the other controllers, plugged the head into DMX2 and this time it worked perfectly through Xlights!

It appears that others are seeing the same issue on the Facebook pages.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/dpitts/f16v3_issues/issues/76?email_source=notifications&email_token=AARHOBBR4PRPQB3M7MNUKSLQGWHIHA5CNFSM4IQMYBE2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HHYFSWA, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AARHOBCMXLLSFN2FIRNQWELQGWHIHANCNFSM4IQMYBEQ.

PeteyHall commented 5 years ago

I can confirm that upgrading to 2.52 fixed the Dmx moving head issue.

Thanks!

On Aug 27, 2019, at 5:58 PM, dpitts notifications@github.com wrote:

Hi

I would update to 2.52 because of an output issue with 2.51 for SmartReceivers. I ran several DMX tests with 2.52 last night and saw no issues. The DMX code was not changed in 2.52. You can call me and we can try to resolve your issue.

David

From: PeteyHall notifications@github.com Sent: Tuesday, August 27, 2019 2:48 PM To: dpitts/f16v3_issues f16v3_issues@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [dpitts/f16v3_issues] Serial port issues (#76)

Upgraded most of my controllers to 2.51 this weekend without issue and at the same time, I tried adding a new DMX moving head light to the show but it looks like something may be wrong with 2.51 and the serial ports.

As a basis for my issue: My 2.51 f16v3 controller was set to e131 mode and I added the correct universes and channels where appropriate on the controller. The DMX head was plugged into DMX2 using an RJ45 -> XLR connector.

When I did test mode on the controller itself, the head worked as expected but when I tried to control the head through Xlights, the controller was seeing the traffic (as the counter on the main status screen was going up) but there was no output to the moving head. I made sure all of the ports/configs were set properly in Xlights but no matter what I did, I couldn't get it to work. I then went onto the controller test mode and even though the head was plugged into DMX2, Serial 4 was the only one that would provide output.

As a test, I did this on multiple controllers running 2.51 and had the same problem every time.

I took one of my original firmware f16v3, made the same configuration changes as on the other controllers, plugged the head into DMX2 and this time it worked perfectly through Xlights!

It appears that others are seeing the same issue on the Facebook pages.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/dpitts/f16v3_issues/issues/76?email_source=notifications&email_token=AARHOBBR4PRPQB3M7MNUKSLQGWHIHA5CNFSM4IQMYBE2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HHYFSWA, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AARHOBCMXLLSFN2FIRNQWELQGWHIHANCNFSM4IQMYBEQ. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.