First time SS24 bui...
 
Notifications
Clear all

First time SS24 builder.. Need help

25 Posts
10 Users
0 Reactions
6,073 Views
Posts: 30
Topic starter
(@rukiddin)
Eminent Member
Joined: 14 years ago
[#21986]

Just finished building my first SS24, it powers on, green LED, I started through the Basic Setup guide, and tested channels 1-8 manually by removing the PIC and hard wire testing them, and they all worked. I started the next phase of testing with the Diagnostic PIC, turn it on, and Channel 1 comes on and stays on, none of the other channels do anything.

Before I start tearing things apart, am I missing something obvious? Seems like the PIC isn't switching like it should, which could be a bad PIC or a bad oscillator? My solder points look good. When I put a non-diagnostic PIC in U6, I get the same result (channel 1 on, others off).

I programmed the PICs myself, so that could be the problem, but they seemed to take the programming fine. (I downloaded the diagnostic and regular firmware from the guide)

I still have a long way to with regards to testing before I'm fully functional, but I want the basic stuff at least passing the built in diagnostics.

Thanks

Mike


24 Replies
kychristmas
Posts: 3955
(@kychristmas)
Famed Member
Joined: 18 years ago

It actually sounds like you may not have gotten the PIC programmed. Try to program it again and do a verify to make sure.


Reply
THurrle
Posts: 1211
(@thurrle)
Noble Member
Joined: 17 years ago

Not sure if you erased the pics before yo tried to flash them If you did you need to load your hex file again. They will appear to flash. You don't have to erase them each time to program them. Make sure your hex file is loaded. From my own experience.


Reply
Posts: 154
(@scubaspookf)
Estimable Member
Joined: 16 years ago

I have built numerous SS24's and never used the diagnostic firmware. If the testing worked manually by connecting a jumper from pin 14 to whatever the wiki says and it worked for all channels the boards seem to work flawlessly at least for me. So once the initial testing of the mocs is done I load up the firmware, install the cabling to the computer and give it a go.


Reply
Posts: 30
Topic starter
(@rukiddin)
Eminent Member
Joined: 14 years ago

I'll reflash the firmware for sure..

If I power the board up not attached to a PC and have the PIC programmed for normal operation, what should happen on Channel 1? Like I said, right now the light comes on and stays on. Is that normal? (I get no LED action with JP3 shunted or unshunted). (other than the power LED).

I'll report back after flashing the PIC again.

Thanks

Mike


Reply
OregonLights
Posts: 736
(@oregonlights)
Prominent Member
Joined: 16 years ago
scubaspookf wrote:I have built numerous SS24's and never used the diagnostic firmware. If the testing worked manually by connecting a jumper from pin 14 to whatever the wiki says and it worked for all channels the boards seem to work flawlessly at least for me. So once the initial testing of the mocs is done I load up the firmware, install the cabling to the computer and give it a go.

+1
I tried the diagnostics with my Ren48LSD and couldn't get it to work. So I just fired it up with standard firmware and it worked fine. I've done the same with my RenSS boards ever since and didn't have any issues. If you're confident with your soldering skills and followed the Wiki carefully to assemble, diagnostics may be more trouble than it's worth unless you have a known issue (just my humble opinion).

I just plug in a light string and test with normal firmware to ensure it's working right.


Reply
Posts: 30
Topic starter
(@rukiddin)
Eminent Member
Joined: 14 years ago

This was my first Soldering job, so am I confident? eh? although I did practice on a "practice" board I bought at Fry's first and I watched a lot of Youtube videos.

If I put a blank PIC in what should happen on channel 1? If there is a difference, at least I know something is programmed on the PIC.

Mike


Reply
Posts: 30
Topic starter
(@rukiddin)
Eminent Member
Joined: 14 years ago

Ok,

Did some re-flashing.. got some interesting results. Even though last night I verified EVERYTHING, I clicked "Blank Check" this morning, and all 3 PICS I have verified as BLANK.

So this time, I did it a little differently. First I flashed the operational firmware, then I verified it, then I loaded the diagnostic firmware, and did a verify against that (which failed like it should), I also did a blank check and it failed the blank check.. so something burned on that PIC. I restarted, reloaded the operational firmware, and verified it again against the PIC I had burned, and it verified successfully, loaded the diagnostic firmware, verified, and it failed... Perfect.

I did the same thing with my second PIC, except I burned the diagnostic firmware, and verified it against the operational (which failed like it should), so the diagnostic firmware seems to have taken on PIC #2.

The last one I left as blank (I wanted to see what happens on a verified blank chip on the board).

First plugged in the blank PIC into the board, and as expected (since this is what happened last night), the light on CHANNEL 1 lit up.

Second plugged in the Diagnostic PIC into the board, with JP3 shunted - NOTHING (no LEDs, no light)
Third still with the diagnostic PIC, JP3 unshunted - NOTHING

Fourth plugged in the operational PIC into the board, with JP3 shunted - NOTHING (no LEDs, no light)
Fifth still with the operational PIC, JP3 unshunted - NOTHING

I was really hoping to get some results from the diagnostics, since it seems so many people have initial problems with their cables and baud rates. Guess I'll make a cable later today and give it a go connected to a PC. Unless someone else has more things for me to try.

Thanks

Mike

p.s. Just for additional information, I am using a completely unmodified version of the firmware which I downloaded from the SS24 wiki. I know there are some things you modify for PWA vs. non-PWA, and also the unit #, but since I only have one unit, I assumed I really didn't need to do anything. Plus I plan on using some LED strings, and it sounds like PWA is more reliable for that. (and PWA is the default right?)

Should I try and download some of the pre-Hexed firmware's that I see on the forums? (they seemed a little old though)


Reply
kychristmas
Posts: 3955
(@kychristmas)
Famed Member
Joined: 18 years ago

I would suggest making a cable ASAP. You have to do it anyway and even the diagnostic FW isn't much without it. There is a Beta Diagnostic FW in the wiki as well. It will turn on channels in a pattern for more direct testing of the ouputs.

btw, It's PWM not "PWA" 🙂


Reply
CaptKirk
Posts: 2200
(@captkirk)
Noble Member
Joined: 16 years ago

Double check the orientation of the clock chip- that baby is easy to get soldered in wrong. One corner will be different from the others and that needs to face toward the indicator on the board.

+1 on getting a cable hooked up, but you can also hook LIGHTS to the channels used by the diag firmware and those tend to be a bit more reliable than the LEDs for indicating especially with the PWM option enabled.


Reply
Page 1 / 3
Share: