DiyLightAnimation
Hardware => Lynx Zeus => Topic started by: rrowan on November 21, 2013,
-
Hi Folks,
My apologizes for the delay. Life got in the way and I was unable to release the software earlier.
It is now in the wiki equipment page under Zeus 16
Just unzip the file and run the program.
Changes since the previous version:
Device to Setup, Select Zeus (not SSC)
String #, All does all of the controllers on the Zeus at one time, You can select each one to customize as needed. Note ALL: increments the start channel base on the other options selected.
Color order is now in RGB (Red Green Blue) format selection and not type of nodes. This was done to support different orders and since our friends in China like to keep changing them.
The rest of the options are the same.
Let us know how it goes.
Yes I know the version number is not updated. I have no control over that part.
Note: There is not an installer with this version.
You must have a previous version installed and then you can use the exe file in the wiki. So don't uninstall the previous version. This also allows you to use the previous version for your SSC's (until the firmware is updated to support the color orders) or you can select the Zeus version. You don't want the exe files in the same folder.
Rick R.
-
thanks for all your hard work Rick
-
zues is built got the utility running. first few attempts I programmed in "all" only one string would light up. when I went in and did individual. they would light accordingly. well I noticed that I didn't change the rgb order when the utility opens it defaults to rgb but the order on the pcb is rbg? well now I am getting nothing when trying to transmit? did not having the correct order selected screw something up? I added a 5th test string because I had 4 before onto a different string number in case I did do something to the pics and it is not working either. they were working in the default setting of rgb but not now
UPDATE
after rebooting everything, waiting a few minutes to try anything. leaving the rgb order as is from default rgb being my string type selection, I was able to get it to transmit again programming ALL strings, start channel 4097, 50 nodes per string, ed as my dongle, it will transmit to one channel. shouldn't it transmit to all channels at the same time?
-
First of all, 4097 is an INVALID starting address. A pixelnet universe only has 4096 addresses so proframming the Zeus to start at 4097 is simply not possible. If you are trying to start the Zeus at the beginning of universe 2, then set the starting address to 1. Yea, that's right, set it to 1. Remember that the sequencing software channels will not always be the same as the hardware channels. The sequencing software will make the translation of sequence channel 4097 to hardware channel 1 of PixelNet universe 2. The utility should have caught this but either way, make sure that none of the channels exceed 4096 or the Zeus will NOT be able to display them.
-
changed it and nothing now
ED
ZUES
strings ALL
start channel 1
individual pixels
50 nodes per string
rgb
that is how I have it set up and now it's not transmitting anything. I rebooted everything and no response on any of the 5 strings I have connected (string 1, string 5, string 8, string 12, string 16)
-
What channel numbers are you using on your sequence? I would suspect that when using the utility that you have the Zeus universe set to universe 1 for configuration. If you are using your sequence software to test at channels exceeding 4096, make sure that you move the universe jumpers back to universe 2. If you set your configuration with the Universe jumpers set to universe 2, then the device may never see it and if you are testing at channels above 4096, the software will be sending that data on the proper universe which will NOT be on universe 1 with channel counts exceeding the first universe capabilities.
-
I did have it on universe 2 on the zues, switched to universe 1, rebooted, and nothing. tested ED with the lights I already have up and it is working fine. program pins are terminated
-
For some reason I was thinking you had to program on universe one and then move to other universes to use.
So if you wanted 4097 you would program on universe 1 channel 1 and the switch the jumper to universe 2 to use.
-
For some reason I was thinking you had to program on universe one and then move to other universes to use.
So if you wanted 4097 you would program on universe 1 channel 1 and the switch the jumper to universe 2 to use.
you are right. I was doing it wrong. i'm still not getting anything out of it though. I have another one to build so when I am done with that I will test it and trouble shoot from there
-
Nothing if you just try one string channel one type of setup? Power cycle it and give all the defaults a try on one string. Can you try taking the first pic out and put one in from the other build.
-
swapped pics, power cycled ED and zues, launched utility.
ED
ZUES
channels 2
individual nodes
# of nodes 35 for test
rgb
and nothing.
-
swapped st485 chip and still the same results
-
just to be clear. set up just like ssc on node wiring correct? red + green - blue data tried another set of nodes and still no dice
-
That could be an issue with your sequencing software setup. Set the Zeus to universe 1 and set the starting address to 1, set the jumper in program mode, power it up and give ita few seconds and then press the send button on the config utility. I was not involved in the design of the Zeus but it appears that in order for you to configure it, you need to give it a few seconds to configure itself so each processor knows which one it is. Hopefully you will see the strings start flashing in a few seconds. After that, power the Zeus down and move the jumper into the run (single pin) mode and power it back up. Then, without changing anything (leave it on universe 1) run a test using channel 1 to whatever and see if the Zeus responds. If not, then you have some issus that need further exploration. If it does, then move the jumpers to universe 2 and run you test again using the higher channels. If it doesn't work there, then your issue is more likely in the sequncing sofware configuration. You could also try another cat5 cable between the zeus and the dongle.
Of course, make sure that you are NOT connecting the zeus to one of the hub outputs other than the PixelNet output and that you are using an ETD and not the USB dongle which is only capable of 1 Pixelnet universe. For this testing, the zeus should be directly connected to the dongle output and make sure that you are NOT using a crossover cable here. It will not hurt the unit but it won't work either.
-
no sequence software being used just yet. I am just trying to get the board programmed. I have seen it flash the light today. when I did program all, it would flash one string. I could go in and do one string at a time and it would flash each one. now it won't do anything. test on ed works the lights just fine. switch cat5 cables
-
You do have the terminate set correct? The jumper does need to be on if you are not using the pixelnet out on the board
-
Check the fuses and make sure that none have failed. How do you have the Zeus hooked up?
-
12v at all screw terminals, fuses good. terminate is terminated. ED definitely works. having issues receiving data at the zues. 3rd cat5 cable I have tried so I seriously doubt that is it. here are some pics. I had to take them inside the garage, it's dark outside.
-
Are you saying you can program one string at a time but not all?
RJ
-
Are you saying you can program one string at a time but not all?
RJ
when I first set it up on the utility it would flash one string when I tried to program as all. then I tried each individual channel and it worked fine with the corresponding channel, but now it won't let me do anything. I checked some solder joints that were questionable and went threw the whole board. I have swapped st485 chips. I have swapped a pic chip with one from my other zues kit and tried just that string. and still nothing.
-
Built and tested without a hitch. Tested Only with 3 strings so far, as cabling (my least favorite activity) is taking me forever.
Programmed it using - ALL - 50 nodes/string - starting address @ 1
Jumpers on board were:
Terminate:closed
Program:closed
Universe: 1-1
Using etherdongle. When sent the data, the 3 attached strings (#1/#2/#3) all flashed white.
Turned power off. Opened the program jumper. Move the universe jumpers to #2 and #2 (my setup in LSP has my mega tree starting at address #4097). Repowered everything and launched a sequence with LSP -> lights working.
Duane, I looked at the pics and couldn't spot anything wrong on the board. The only thing I can think off is to make sure that the cable going from the board to the string, lead to the first node with the chip inside the LED closest to the board.
-
Built and tested without a hitch. Tested Only with 3 strings so far, as cabling (my least favorite activity) is taking me forever.
Programmed it using - ALL - 50 nodes/string - starting address @ 1
Jumpers on board were:
Terminate:closed
Program:closed
Universe: 1-1
Using etherdongle. When sent the data, the 3 attached strings (#1/#2/#3) all flashed white.
Turned power off. Opened the program jumper. Move the universe jumpers to #2 and #2 (my setup in LSP has my mega tree starting at address #4097). Repowered everything and launched a sequence with LSP -> lights working.
Duane, I looked at the pics and couldn't spot anything wrong on the board. The only thing I can think off is to make sure that the cable going from the board to the string, lead to the first node with the chip inside the LED closest to the board.
what configuration did you use for the rgb? rgb? rbg? mine worked briefly and then nothing.
-
rgb. I didn't change any other settings than the one mentioned in my previous post.
-
built zues #2, programmed threw the utility and the 3 strings I had connected all flashed. powered down, opened up program jumper. opened vixen, test sequence and no response. powered down the zues, went back into utility to program again. nothing! i'm going to bed!
-
I will test my Zeus this morning and see if I can simulate the same issues you are having now.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Strang that you guys are having these issues, the beta guys threw everything but the kitchen sink at them and the final product worked like a charm for them.
In program mode, jumper set, the units ignore any programming you do so no matter what you program you should not be able to make it where you can not be able to program it.
RJ
-
Strang that you guys are having these issues, the beta guys threw everything but the kitchen sink at them and the final product worked like a charm for them.
In program mode, jumper set, the units ignore any programming you do so no matter what you program you should not be able to make it where you can not be able to program it.
RJ
not sure what I've done RJ. I have built 20 LE's, 3 active hubs, dongles, ssc's, dsc's ....etc and no problems.(short of networking issues with my conductor that I put on the back burner). i will get at it again after work today and see what i can come up with.
-
I can't help but wonder if the conductor and zeus issues are somehow related...
-
How do the processors know which one is which? Is this something that happens every time the Zeus boots up or is this a one time thing? Could a bad config load prevent this from happening? He also said that that he swapped a few processors while attempting to debug the programming issue. Would this have a negative effect?
-
How do the processors know which one is which? Is this something that happens every time the Zeus boots up or is this a one time thing? Could a bad config load prevent this from happening? He also said that that he swapped a few processors while attempting to debug the programming issue. Would this have a negative effect?
No I made it simple and bullet proof. the pcb is coded to tell each pic which one they are. if you look at some of the pins on the pcb you will see four pins on each pic are binary encoded to 0 - 15 so the pic always knows which one it is. The firmware reads this on boot and goes from there. You can not change this in software.
RJ
-
No I made it simple and bullet proof. the pcb is coded to tell each pic which one they are. if you look at some of the pins on the pcb you will see four pins on each pic are binary encoded to 0 - 15 so the pic always knows which one it is. The firmware reads this on boot and goes from there. You can not change this in software.
RJ
I don't have one yet so I was unable to look at the board but that is very cool. It appears that the configuration utility allowed him to set the start address to one above the limits of a PixelNet universe. Even though I doubt it, could doing that corrupt the firmware or configuration area in memory in some way? I am just reaching here because these issues just don't seem to make sense.
-
I was able to simulate his problem, which is now my problem also.
Here is my set up:
Window 8 > Ethernet Dongle>Zeus Pixelnet In>Zeus Pixelnet Out>Active Hub>DMX out>LE and SSCs for Smartstring Matrix. I also have a Flex strip on Zeus String 1.
Here is what I found.
During the whole process I never had xLights and the Zeus SS Utility open at the same time. I also had the jumper on for terminate.
1. I was able to program the Zeus to channel 1, using String 1 connections.
2. I was able to program every version of color selection using the Zeus SmartString Utility. Note: Though I have 120 nodes I was choosing 84 nodes to eliminate the warning of max nodes.
3. I could run the all channel test in xLights and was able to test every setting in xLights including individual channels. No problem.
4. Then it happened. That moment you think you are good to go. I decided to try changing the color back to my operating color for the flex strip. I closed xLights and opened the Zeus SS utility and started to change back to RGB. I forgot one little mark and that was to change the selector on the utility to Zeus and not SSC. Since that point I can not get the Zeus to work at all.
5. I moved back to xLights to see if I lost my previous settings (they were gone or not reacting to xLights)
6. What is interesting is my Active Hub, Matrix and LE are still responding to my test signals from xLights.
7. My Zeus is not responding and the Terminate jumper does not effect my Pixelnet Out at all.
8. I tried a single string program and it does not work now also. I also removed and installed the Zeus Utility again and can not get the Zeus to take a channel configuration.
I hope this helps us figure out what is going on. I did notice the Warning in the Wiki stating to not use the Zeus SS Utility to program SSC. Could it be that when I forgot to select the Zeus button in the utility it stayed in the default selection of SSC and that sent the wrong information to the Zeus and now it is acting like it will never work? Let me know what you all think and I can try anything and respond back.
One other tidbit of information though on the higher end of trouble shooting. The voltage from the Signal to the Gnd (-) on some of the String connector are 3.32vdc and others are .5vdc. not sure if this is an issue or not. All string points from + to - have 12vdc
-
Based on what you have written I would want to reflash the zeus.
-
I thought about pushing the firmware to the PICs. I have a 24 pin socket for my P3, but I am not sure the Firmware is available.
-
If you have a processor that has not been corrupted, you can read the firmware from it and save it to disk. then you can reload it onto one of the corrupt processors and see what happens.
-
I will try that next. I will let you know next.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
I am guessing but I only have one Zeus and I sent start channels to all. Not sure if they are all corrupted.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
I would bet that they are if you also changed the color order on all of them. I would look into it but I don't have mine yet.
-
We can get the firmware posted, it just has not been since the chips came pre programmed and we hoped no one would have a need to do it. Thats why we took so long on the beta making sure the system worked well as the firmware was. I need to look at the firmware as I do not think it should be possible to mess it up programming to where it will not reprogram. when the setup jumper is on it uses a default setup and ignores the config information that is programmed in. Might be something I am not thinking of but for the moment I would say everyone be careful about using the correct setting to program the Zeus until we figure this issue out.
Maybe the guys in the beta never made this issue. But I do remember someone having an issue that was never worked out and we were never able to duplicate. He also could not get it to repeat and I think it required him to flash his pic. So maybe there is an issue with this.
RJ
-
No worries RJ. As always this is great stuff and fun. We are DIY and we have been through many of these similar situations. I think everyone will be fine as long as they remember to click Zeus in the (Device to Setup) area. It is still about having a hobby that not only makes me happy, but puts smiles on other peoples faces. I am having a blast!
Kevin
-
ok, so I come home from work, made myself 2 knew cat5 jumpers so that I know my cables were good. the others were factory made but that don't mean they were bad. I have a 1000' cat5 so I just made 2 knew ones to eliminate the cables. waited for about a minute, launched utility and nothing. as far as my computer communicating with the ED, the orange light on the ED flickers in correspondence with the transmit letters on the utility, the green light stays solid threw this process. I followed the assembly manual to a T. the 2nd build I did last night flashed all 3 strings that I had connected when I programmed, but when I went into vixen, no response. profile is set to 12,288 channels with ED as dongle. the existing pixels in my sequence work just fine.
so I had friend show up during writing this post and forgot that I had the utility set on program. out of the blue, one of the strings started flashing.
-
I think everyone will be fine as long as they remember to click Zeus in the (Device to Setup) area.
Kevin
on my second build, after going threw all the issues with the first build. I double triple quadruple checked everything to make sure it was right, before I hit the transmit button. AND IT WORKED! I was very happy, until I tried it in vixen and it wouldn't work. so I tried to program just one string at a time and nothing. just that fast. no cables were changed, the only thing I did was power down so I could switch the program pin. repower to run vixen, nothing. power down, put program cap back to terminate, and nothing.
-
I only have one Zeus and never got the chance to try Vixen. They worked perfect in XLights and in all RGB configurations. Once we get the firmware I will test more and confirm if it will fix it. We will understand soon, no worries.
Sent from my iPad using Tapatalk (http://tapatalk.com/m?id=1)
-
The firmware is now in the wiki.
Since the Zeus family doesn't include a ICSP connector you must use an adaptor board.
Two options are the j1.sys board and I put in the wiki the wire jumper settings that the beta team use. Second option is to use the Red Neck board in the wiki. http://www.diylightanimation.com/wiki/index.php?title=Red_Neck_Pic24_programmer
Hope it helps.
Thanks to RJ and the beta guys for the info. I am just the messenger.
Rick R.
-
Thank you everyone for the help. I have the J1 and will make the adjustments.
I will let you know in the morning.
Kevin
-
Rick is this the same configuration on the J1 as is for the V4 PIC config using the J1 with jumpers and the single wire? Like in the Wiki link for V4? I sure hope I did not cause confusion on the page? If so please delete and remove. Darn that was not the best writing, but it has been a 22 hour day. Again, thank you for the help.
Sent from my iPad using Tapatalk HD
-
Since it is the same PIC, I would say yes. For those of us that don't have that particular adapter, if mine doesn't work I will just use my SSC V4 board to act as my adapter.
-
Rick is this the same configuration on the J1 as is for the V4 PIC config using the J1 with jumpers and the single wire? Like in the Wiki link for V4? I sure hope I did not cause confusion on the page? If so please delete and remove. Darn that was not the best writing, but it has been a 22 hour day. Again, thank you for the help.
Sent from my iPad using Tapatalk HD
The annotated picture was a big help... it took a couple minutes to digest it because I've not run wire jumpers in the past. The table in the Zeus-8 and Zeus-16 boxes was much more confusing -- I didn't get that, and still wouldn't know what to do with it -- the picture will be my guide.
I hoped that I'd be able to use a completed SSCv4 as a programming platform (swap PICs, program, swap back). Would that work? Is there enough consistency between SSCv4 and Zeus?
If people don't mind, I will add the picture to the Zeus box(es) near the pinout table, and I'll also add Zeus to the "J1SYS boards jumper chart".
-
Thanks Tbone and Steve. Ido not own a V4 board, but did see it is the same PIC. I would do that if I didn't have the J1 sockets from 4 years ago.
Sent from my iPad using Tapatalk (http://tapatalk.com/m?id=1)
-
this stinks. I don't have an ssc v4 or an adaptor. guess I will need one or the other to flash the pics?
-
Rick is this the same configuration on the J1 as is for the V4 PIC config using the J1 with jumpers and the single wire? Like in the Wiki link for V4? I sure hope I did not cause confusion on the page? If so please delete and remove. Darn that was not the best writing, but it has been a 22 hour day. Again, thank you for the help.
Sent from my iPad using Tapatalk HD
The annotated picture was a big help... it took a couple minutes to digest it because I've not run wire jumpers in the past. The table in the Zeus-8 and Zeus-16 boxes was much more confusing -- I didn't get that, and still wouldn't know what to do with it -- the picture will be my guide.
I hoped that I'd be able to use a completed SSCv4 as a programming platform (swap PICs, program, swap back). Would that work? Is there enough consistency between SSCv4 and Zeus?
If people don't mind, I will add the picture to the Zeus box(es) near the pinout table, and I'll also add Zeus to the "J1SYS boards jumper chart".
Sorry the chart was confusing to you. I don't own any J1.sys products and really have no intentions to own any. The chart was supplied by a beta team member and I was just passing it along. Not sure why pin jumpers are confusing but to each his own. I think if I didn't add the info people would just try to connect the pic to the adapter and if nothing worked right then everyone would be up in arms about that.
Rick R.
-
Rick, thank you for the help. The chart works also. I am sure people will find one type, that they are comfortable using. It is nice to have so many options.
Again, a big thanks to RJ, the Beta testers and you for getting this to us in such a short time.
Kevin
-
I was able to simulate his problem, which is now my problem also.
Here is my set up:
Window 8 > Ethernet Dongle>Zeus Pixelnet In>Zeus Pixelnet Out>Active Hub>DMX out>LE and SSCs for Smartstring Matrix. I also have a Flex strip on Zeus String 1.
Here is what I found.
During the whole process I never had xLights and the Zeus SS Utility open at the same time. I also had the jumper on for terminate.
1. I was able to program the Zeus to channel 1, using String 1 connections.
2. I was able to program every version of color selection using the Zeus SmartString Utility. Note: Though I have 120 nodes I was choosing 84 nodes to eliminate the warning of max nodes.
3. I could run the all channel test in xLights and was able to test every setting in xLights including individual channels. No problem.
4. Then it happened. That moment you think you are good to go. I decided to try changing the color back to my operating color for the flex strip. I closed xLights and opened the Zeus SS utility and started to change back to RGB. I forgot one little mark and that was to change the selector on the utility to Zeus and not SSC. Since that point I can not get the Zeus to work at all.
5. I moved back to xLights to see if I lost my previous settings (they were gone or not reacting to xLights)
6. What is interesting is my Active Hub, Matrix and LE are still responding to my test signals from xLights.
7. My Zeus is not responding and the Terminate jumper does not effect my Pixelnet Out at all.
8. I tried a single string program and it does not work now also. I also removed and installed the Zeus Utility again and can not get the Zeus to take a channel configuration.
I hope this helps us figure out what is going on. I did notice the Warning in the Wiki stating to not use the Zeus SS Utility to program SSC. Could it be that when I forgot to select the Zeus button in the utility it stayed in the default selection of SSC and that sent the wrong information to the Zeus and now it is acting like it will never work? Let me know what you all think and I can try anything and respond back.
One other tidbit of information though on the higher end of trouble shooting. The voltage from the Signal to the Gnd (-) on some of the String connector are 3.32vdc and others are .5vdc. not sure if this is an issue or not. All string points from + to - have 12vdc
Well I did not program all but rather just the channel I intended to use and forgot to set it to the Zeus in the utility so I did send the SSC part to the Zeus. I did not play with any of the RGB settings and just have 1 flex attached to see how it did.
So after reading this thread I just replaced the PIC of the channel I was using and it took the program ( Flashed all white) However when I play my sequence I get nothing. So my thoughts now are I need to re-flash all the PIC chips but I wanted to verify that with you all first.
My setup is currently Window XP > Ethernet Dongle>Zeus Pixelnet In>Zeus Pixelnet Out>Active Hub. And the active hub has a SSC on it with the same channels I was trying to get the Zeus to play.
SO please let me know if a re-flash of all the PIC's on the Zeus is the way to go now. That will teach me from burning the midnight oil. ;)
thanks.
Tallan
-
Rick is this the same configuration on the J1 as is for the V4 PIC config using the J1 with jumpers and the single wire? Like in the Wiki link for V4? I sure hope I did not cause confusion on the page? If so please delete and remove. Darn that was not the best writing, but it has been a 22 hour day. Again, thank you for the help.
Sent from my iPad using Tapatalk HD
The annotated picture was a big help... it took a couple minutes to digest it because I've not run wire jumpers in the past. The table in the Zeus-8 and Zeus-16 boxes was much more confusing -- I didn't get that, and still wouldn't know what to do with it -- the picture will be my guide.
I hoped that I'd be able to use a completed SSCv4 as a programming platform (swap PICs, program, swap back). Would that work? Is there enough consistency between SSCv4 and Zeus?
If people don't mind, I will add the picture to the Zeus box(es) near the pinout table, and I'll also add Zeus to the "J1SYS boards jumper chart".
Steve,
It sounds like using the SSCv4 to program the Zeus PIC should work. The difference between selecting SSC and Zeus in the SS Utility program is in the information sent to each unit. The Zeus has one additional byte, String #, at the beginning of the data stream. By not selecting Zeus as the controller, the information for each string was NOT transmitted, which means only one PIC could have been affected provided that you didn't change the starting channel #. Since the configuration information for both the SSC and Zeus are stored in the same location in the PIC, it picked up byte one of the starting channel # as the string #. Thus all the Zeus configuration information is corrupt, i.e. offset by one byte since string # was missing in the data stream.
As to why you can't redo the programming for Zeus the only thing I can't guess is that the firmware is rereading the corrupt configuration information and getting a fatal error prior to checking to see if it's in program or operational mode.
I don't have access to the source code to verify that though.
Unfortunately the only fix is to flash the PIC again.
I just thought of one thing. You should be able to program a single string in Zeus since all the PIC's shouldn't have been corrupted. Try configuring a single string, i.e. don't use the "ALL" option for string and see if that works.
Denny
-
this stinks. I don't have an ssc v4 or an adaptor. guess I will need one or the other to flash the pics?
To avoid confusion, you shouldn't normally need to program the PICs... from the coop:
PICs will be programmed
Having the PICkit3 and a harness of some kind is needed for future updates, or if troubleshooting and the firmware is one step to rule out that as a problem.
-
I used all the first and second time and it did corrupt everything. I just finished flashing my PICs. I am tempted to test the single channel and see if it fails the whole board. Curious I guess.
As of right now everything is working fine. I even moved it to a different universe and all is good.
Kevin
-
I used all the first and second time and it did corrupt everything. I just finished flashing my PICs. I am tempted to test the single channel and see if it fails the whole board. Curious I guess.
As of right now everything is working fine. I even moved it to a different universe and all is good.
Kevin
so by flashing all of your pics, it fixed your issue?
-
Yes. Then make sure to always select the Zeus button when setting start channels.
Sent from my iPad using Tapatalk (http://tapatalk.com/m?id=1)
-
I used all the first and second time and it did corrupt everything. I just finished flashing my PICs. I am tempted to test the single channel and see if it fails the whole board. Curious I guess.
As of right now everything is working fine. I even moved it to a different universe and all is good.
Kevin
Just so people are clear on this, it's NOT the "ALL" option that caused the issue but having a mismatch between the controller being programmed, Zeus in this case, and then not selecting Zeus for the "Device to be Setup" in the SS Utility program.
Programming the Zeus PCB and then selecting SSC or leaving it as the default when the SS Utility program is opened, will cause the problem.
This can be prevented from happening in the future with a new firmware release but for now be sure they match.
Denny
-
So I flashed all mine and that seemed to correct the issue as well.
Thanks,
tallan
-
so if I get this right, I either need an sscv4 or the 24pin adapter from j1sys to reprogram my pics? I have the icsp28, is there a way to make that work?
-
Soon as I can I am sending out a Zeus only version of the utility to fix this. That way no one can make this mistake.
RJ
-
Rick remove the current utility for me to stop any more people doing this.
RJ
-
Rick remove the current utility for me to stop any more people doing this.
RJ
file is deleted
Rick R.
-
so if I get this right, I either need an sscv4 or the 24pin adapter from j1sys to reprogram my pics? I have the icsp28, is there a way to make that work?
please let me know so I can order what I need or try and get an sscv4 from someone. I only have sscv2
-
Duane, I used the same device to program my PICs. Make sure you set the jumpers in the correct position and build the jumper wire. I Tested by reading my PIC first.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Soon as I can I am sending out a Zeus only version of the utility to fix this. That way no one can make this mistake.
RJ
I made sure everything was right on my second build (ED-zues-node count- node type) , it worked to flash the 3 strings I had connected in program mode but would not respond in vixen. then I tried to check each individual string and nothing.
-
so if I get this right, I either need an sscv4 or the 24pin adapter from j1sys to reprogram my pics? I have the icsp28, is there a way to make that work?
please let me know so I can order what I need or try and get an sscv4 from someone. I only have sscv2
Do you have a electronics store near you? (Radio Shack, Fry's, etc)
If so just make the Red Neck programmer. Cheap fast and it works just fine.
http://www.diylightanimation.com/wiki/index.php?title=Red_Neck_Pic24_programmer
just a solderless breadboard and wires.
Rick R.
-
Duane, I used the same device to program my PICs. Make sure you set the jumpers in the correct position and build the jumper wire. I Tested by reading my PIC first.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
j
where do I find the diagram? or is this it?
http://www.diylightanimation.com/wiki/index.php?title=File:J1SYS_PIC24F04KA200_SSCV4_FIX.png
-
That may be a set up issue. I was able to use Vixen, xLights. Check to make sure your profile is checked in Vixen. I forgot to do that today.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Do you have a electronics store near you? (Radio Shack, Fry's, etc)
.
[/quote]
5 minutes away. thanks Rick. I saw that diagram but wasn't sure if it would work with the 24 pin.
-
Do you have a electronics store near you? (Radio Shack, Fry's, etc)
.
5 minutes away. thanks Rick. I saw that diagram but wasn't sure if it would work with the 24 pin.
[/quote]
Administrator
Sr. Member
*****
Re: Welcome to the Beta
« Reply #19 on: June 20, 2013, 07:39:42 AM »
I am afriad this is one thing I can't help on as I do not have anyones adapter. I use the old Redneck adapter I built and posted in the wiki and it does not have jumpers. I just do it on a proto breadboard.
It should be the same setup as a pic 24fj16GA002 chip from the previous ssc or express. so you could look for the jumpers for them as try that.
Anyone else have one of these and can help?
RJ
Just saying....... ::)
Rick R.
-
I built the redneck bread board version before and it works just fine. My J1 stuff was a gift years ago and must say I ended up using both today just for fun. Thanks again Rick and RJ.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
Duane,
Have a bunch of extra SSCv4s as well as programmed pics from my zeus coop order. Gimme a PM if you want something.
-
Do you have a electronics store near you? (Radio Shack, Fry's, etc)
.
5 minutes away. thanks Rick. I saw that diagram but wasn't sure if it would work with the 24 pin.
Administrator
Sr. Member
*****
Re: Welcome to the Beta
« Reply #19 on: June 20, 2013, 07:39:42 AM »
I am afriad this is one thing I can't help on as I do not have anyones adapter. I use the old Redneck adapter I built and posted in the wiki and it does not have jumpers. I just do it on a proto breadboard.
It should be the same setup as a pic 24fj16GA002 chip from the previous ssc or express. so you could look for the jumpers for them as try that.
Anyone else have one of these and can help?
RJ
Just saying....... ::)
Rick R.
[/quote]
well there is no jumper chart for the pic referenced in your quote. I built the redneck bread board version and I am not detecting the pic for the zues but if I put a 24fj32ga002 it will read it. does the .1uf capacitor need to be on a different pin with the 14 pin pic? it obviously isn't doing any good for the 14 pin pic being on space 20. here is a pic
-
as I interpret the chart and your picture, pic pin 1,14,13 are good...
but pic 3 is not going icsp 4 as it should -- instead you have 4 going to 4.
ALSO, instead of pic 2 going to icsp 5, you have 5 going to 5.
Refer to the chart:
http://www.diylightanimation.com/wiki/index.php?title=Equipment#Zeus_.26_Pixelnet_Hubs
-
as I interpret the chart and your picture, pic pin 1,14,13 are good...
but pic 3 is not going icsp 4 as it should -- instead you have 4 going to 4.
ALSO, instead of pic 2 going to icsp 5, you have 5 going to 5.
Refer to the chart:
http://www.diylightanimation.com/wiki/index.php?title=Equipment#Zeus_.26_Pixelnet_Hubs
thanks steve, i haven't checked in the wiki this evening. i was just going by the diagram in the post rick sent me but i will switch the wires around and see where i go! lol
-
I've updated the wiki -- both the J1Sys table with (4) options!! :)
...and also the page for the redneck.
I see your issue (duane)... you built the redneck as described, but the instructions were for the 24FJ32GA002 PIC, not the one used with Zeus, PIC24F04KA200. I've updated the redneck page with the additional table.
Please review.
http://www.diylightanimation.com/wiki/index.php?title=J1SYS_boards_jumper_chart (http://www.diylightanimation.com/wiki/index.php?title=J1SYS_boards_jumper_chart)
http://www.diylightanimation.com/wiki/index.php?title=Red_Neck_Pic24_programmer (http://www.diylightanimation.com/wiki/index.php?title=Red_Neck_Pic24_programmer)
-
i must say. THANK YOU! THANK YOU! THANK YOU! and if i left anyone out. THANK YOU TOO! all good now. everything responding in vixen as it should. . i only flashed one zues and tested the one. i am assuming my second one is the same issue so i will find out in the morning before i go out in forecasted 25 degree weather with wind chills in the teens to hook it all up. such is life. zues conquered, i'll be back in the conductor section before long. lol
CANT' SAY THANKS ENOUGH TO ALL THE HARD WORK WE ALL PUT INTO THIS HOBBY TO MAKE IT EASIER AND SMOOTHER FOR THE NEXT GUY.
-
great news!!
-
great news!!
yes sir. now time to get some sleep and get back at it tomorrow.
-
Great to hear!
Sent from my iPad using Tapatalk (http://tapatalk.com/m?id=1)
-
Great news. Thanks to everyone working this as. I haven't tried programming my Zeus boards yet but this thread has given me a lot of information that should be invaluable. Can someone explain when the terminate should be set?
-
Great news. Thanks to everyone working this as. I haven't tried programming my Zeus boards yet but this thread has given me a lot of information that should be invaluable. Can someone explain when the terminate should be set?
[/quo
the terminate should be set when your not using the pixelnet out put. so if your zues is solo, then terminate, just like on the express. so with your mega tree, one zues would be open while you terminate the other.
-
second zues works as it should. thanks to everyone whom made it possible. the wife says thanks too! lol
-
Congrats Duane. Glad you got it figured it out, just sorry you had to be the guinea pig.
-
So am I correct in my understanding that you always program channels with a starting value between 1 and 4096 regardless of the pixelnet universe? I can't believe I didn't know this already but probably because I had under 4096 (1 pixelnet universe) in prior years it didn't really matter.
So for example, if I want to start a display item at pn ch#4097 ... This would be set as starting channel 1 and I just jumper the Zeus (or ssh) to pn univ#2 ... Which in the software can be referred to s pixelnet channel 4097.
Also, do you need to have the jumper set to pn univ#1 when running the ss utility?
-
So am I correct in my understanding that you always program channels with a starting value between 1 and 4096 regardless of the pixelnet universe? I can't believe I didn't know this already but probably because I had under 4096 (1 pixelnet universe) in prior years it didn't really matter.
You said program channels, but you are referring to hardward addressing. To keep them separate in my mind I try to always talk about hardware as addressing and software as channels. Hardware addressing does not equal software channels once you get into more than one universe. a similar terminology issue comes up all the time when folks talk about programming the pic. I alway say flash the pic for loading firmware and programming when I am talking about configuring the firmware. It is hard to keep it all straight when we use the same terminology for different things.
So for example, if I want to start a display item at pn ch#4097 ... This would be set as starting channel 1 and I just jumper the Zeus (or ssh) to pn univ#2 ... Which in the software can be referred to s pixelnet channel 4097.
Also, do you need to have the jumper set to pn univ#1 when running the ss utility?
I always have, but do not know if that is required. It helps that I have a backup active hub that stays on my workbench and I always leave that one at univ 1. I use a passive hub for universe 2 (and I have a backup for that as well and set to univ 2)
-
Thanks, I agree we need to use the terms you suggested to keep everything clear.
-
So am I correct in my understanding that you always program channels with a starting value between 1 and 4096 regardless of the pixelnet universe? I can't believe I didn't know this already but probably because I had under 4096 (1 pixelnet universe) in prior years it didn't really matter.
So for example, if I want to start a display item at pn ch#4097 ... This would be set as starting channel 1 and I just jumper the Zeus (or ssh) to pn univ#2 ... Which in the software can be referred to s pixelnet channel 4097.
Also, do you need to have the jumper set to pn univ#1 when running the ss utility?
In the DMX world, devices have channel assignments from 1-512, multiple DMX universes can coexist, often called "networks".
Similarly in the Pixelnet world, the devices have channel assignment from 1-4096, and again multiple universes can coexist.
The devices know nothing about the other universes, only their place within their current universe.
If your dongle is sending packets over universe 2, the hub is assigned to #2 using the jumpers, then the SSCs will pick up the packets -- they won't know they are on universe 2... the hub knows that by the selection of the 2nd pair.
-
Congrats Duane. Glad you got it figured it out, just sorry you had to be the guinea pig.
Thanks, just earning my keep. I don't mind learning the hard way. Guarantee I won't do it again! Lol
-
Please replace your EXE file with this Version 2 file to prevent the issue. Rick if you would please put this one in the wiki for everyone.
Thanks
RJ
-
Please replace your EXE file with this Version 2 file to prevent the issue. Rick if you would please put this one in the wiki for everyone.
Thanks
RJ
Added to the wiki
Rick R.