Completed an SS24 and it just wouldn't go. Removed all the chips and followed the Beginners Setup Guide. Everything checked out down to running the diagnostic firmware. Connected test lights to channels 1-8, ran the diagnostic firmware and lights flashed as described in the guide. Setup a Vixen sequence with the settings listed in the guide. Let the diagnostics run through it's cycle then started the Vixen sequence while channel 1 was still flashing. While the sequence was running:
-Channel 1 was still flashing
-LED SD was on
-LED FE was ON
-test light on channel 6 came on and stayed on while the sequence ran
-test light on channel 7 did the same
-Channels 2,3,4,5 and 8 stayed off
Any thoughts?
If the FE light is on, that's a problem. You likely do not have the COMM settings correct and/or consistent in all places. The settings need to be in three places:
Windows COM Port Settings
Vixen Plugin Settings
PIC Code
Make sure these are consistent and go from there.
baud rate has to be at 57600
I'll double check the COM settings. If it makes a difference or not, before going to the Troubleshooting Guide I had a working SS24 laying next to the problem SS24. Ran a successful sequence on the good one, took the J2 cable to the bad one and 'nothing' when I ran the sequence. Tried swapping the PICs, tried daisy chaining it from the good one, still nothing on the bad one. When I installed the diagnostic firmware I changed the baud rate to 19200 in the profile plugin, do I need to change it elsewhere also?
gilles1 wrote:baud rate has to be at 57600
While that is typical, it's not always the case and definitely does not "have to be set at 57,600". I just helped someone who's PICs were set at 38,400.
gassy wrote:I'll double check the COM settings. If it makes a difference or not, before going to the Troubleshooting Guide I had a working SS24 laying next to the problem SS24. Ran a successful sequence on the good one, took the J2 cable to the bad one and 'nothing' when I ran the sequence. Tried swapping the PICs, tried daisy chaining it from the good one, still nothing on the bad one. When I installed the diagnostic firmware I changed the baud rate to 19200 in the profile plugin, do I need to change it elsewhere also?
Yes, that bit of information is important and good to know 🙂 Since Cabling and COM settings are the most common issue, you have eliminated those.
As I mentioned above, COM settings also need to be changed in the Windows COM Port settings.
kychristmas wrote:While that is typical, it's not always the case and definitely does not "have to be set at 57,600". I just helped someone who's PICs were set at 38,400.
Being that this is a SS controller, the firmware (both Diagnostic and Operational) from the SS wiki is set for 57600 by default. PICs from the SS Group Buys and from the full SS Kits also come @ 57600. Now if one decides to change it, then that's a different story.
When running a Vixen test sequence with the diagnostic firmware is normal for any of the test lights connected to channels 1-8 to come on?
Wayne J wrote:Being that this is a SS controller, the firmware (both Diagnostic and Operational) from the SS wiki is set for 57600 by default. PICs from the SS Group Buys and from the full SS Kits also come @ 57600. Now if one decides to change it, then that's a different story.
Yes, my point is that the statement "Baud rate HAS to be set a 57,600" is incorrect.
Wayne J wrote:Being that this is a SS controller, the firmware (both Diagnostic and Operational) from the SS wiki is set for 57600 by default. PICs from the SS Group Buys and from the full SS Kits also come @ 57600. Now if one decides to change it, then that's a different story.
I guess I wasn't suppose to change the baud rate for the diagnostic firmware, must of read the directions wrong in the setup guide. Try it again tomorrow.
