DiyLightAnimation
Hardware => Lynx Zeus => Topic started by: lrhorer on January 12, 2016,
-
As I mentioned before, I am making my first foray into RGB, and I am a little stumped by the behavior of my pixel systems. I can't get them to talk properly to my strings. For testing, I have two systems in play, both fed from a Lynx Etherdongle.
The first is a Zeus 16 feeding a 96 node string. When I power the Zeus on, the string's first pixel usually (not always) lights, and nothing else. I tried flashing the Zeus, and it seemed to work (the entire strings started flashing), but now I can't get anything from the Zeus other than that 1 continuous light, whether I try sending data from Vixen 3 or from the config tool.
The second is a 16 port active hub feeding an SSC. It is a V1 modded to V3. I verified I have 12V power on the SSC. I can see the data steaming from Vixen or the config tool, as the case may be.
First of all, I want to verify my understanding that Vixen 3 does not require a driver for Pixelnet. I read that one can employ the embedded E1.31 ACN streaming protocol. The instructions for the plugin say to put it in the ~/plugin directory, but under Vixen 3 there is no such directory.
Assuming I am good up to the ETD output, how do I proceed in order to troubleshoot / fix this?
-
Here's a good starting point
Checklist...
__ Has the chips on the Zues been programmed?
__ Has the Etherdongle been programmed with the Pixelnet firmware?
__ Is the Etherdongle out port (black, doesn't have lights n the port) have a cable connected from it, to the 16 port Active Hub Pixelnet In port?
__ Is there a cable from the pixelnet output to the Zues?
__ Is the Active Hub being supplied with power from a computer power supply with all the white inputs being plugged in on the hub?
__ Does the Active hub have both pixelnet Universe jumpers set to "1"
__ Is your Zues Programmed for channel 1?
-
Had to edit the checklist to change over to a Zues
I guess you can go straight to the Zues also, and forget about the active hub for now in testing.. forgot the zues also has a built in hub onboard.
-
Is this a zeus v1 or v2 (v2 has 16 universe jumpers). Shouldn't matter.
I would put the Zeus last, some of mine seemed to work best that way. PLus having the active hub upstream allows
you to use it as a pixelnet splitter, which is handy and gives other connectivity options.
go from PC --> network sitch --> Etherdongle -> Active Hub ---(PNout)---> Zeus ch#1--> 96 node string
|
+---------SSC ---> rgb test string?
Makes sure the Zeus is terminated, unless your using that universe downstream, in the example above you would not, so terminate it.
Make sure all PIC chips are flashes with firmware.
Makes sure all zeus channels are programmed that you want to use.
Make sure the smart string utility you use to program them is the right version, this is here is gets confusing. Go to the wiki -> smart strings for the links.
The ss utility for the zeus and ssc are not the same! Even betweem ssc v3 and ssc v4 ... also not the same.
So make sure you program the zues with the ss zeus utility (under zeus in the wiki).
and make sure you program the ssc v3 mod with the ssc v3 utility (Not the zeus version).
You might want to download lights and use its tester ... might at least eliminate any potential vixen problems for now.
If you get it working with the xlights tester, then switch to vixen 3 after that.
-
__ Has the chips on the Zues been programmed?
How do I check for sure? I did not build any of this equipment. I've read through using a PIC programmer, but I don't have it working, yet. Is there a preferred / required compiler I should choose? The MPLAB software won't come up unless I choose one. (Or did I select the wrong target somewhere?)
__ Has the Etherdongle been programmed with the Pixelnet firmware?
I think so. It says so on the label.
'Same question.
__ Is the Etherdongle out port (black, doesn't have lights n the port) have a cable connected from it, to the 16 port Active Hub Pixelnet In port?
When I am testing the hub, yes.
__ Is there a cable from the pixelnet output to the Zues?
When I am testing the Zeus, yes.
__ Is the Active Hub being supplied with power from a computer power supply with all the white inputs being plugged in on the hub?
Yes. The 12V supply option kit is on its way from Mouser.
__ Does the Active hub have both pixelnet Universe jumpers set to "1"
Yes
__ Is your Zues Programmed for channel 1?
Huh? I have tried setting the first address to one on the Zeus using the SSC programming tool V2, if that is what you mean. If not, then I don't know what you mean.
-
Ok, for the pickit3, don't use mplab, but the standalone programmer.
-
Is this a zeus v1 or v2 (v2 has 16 universe jumpers). Shouldn't matter.
V1.1
I would put the Zeus last, some of mine seemed to work best that way. PLus having the active hub upstream allows you to use it as a pixelnet splitter, which is handy and gives other connectivity options.
Standard troubleshooting procedure: remove any unnecessary elements from the system to prevent their causing additional issues within the system. I plug in the Zeus when I am testing the Zeus. I unplug the Zeus and plug in the hub when I am testing the SSC.
go from PC --> network sitch --> Etherdongle -> Active Hub ---(PNout)---> Zeus ch#1--> 96 node string
When testing the Zeus:
PC --> network sitch --> Etherdongle -> Zeus ch#1--> 96 node string
When testing the Hub / SSC:
PC --> network sitch --> Etherdongle -> Active Hub --> SSC --> 12 node string
Makes sure the Zeus is terminated
It is.
Make sure all PIC chips are flashes with firmware.
See above.
Makes sure all zeus channels are programmed that you want to use.
How? I have tried multiple starting addresses using the SSC configuration utility V2.
Make sure the smart string utility you use to program them is the right version, this is here is gets confusing. Go to the wiki -> smart strings for the links.
I've done that, and I am not 100% confidant I have done so. I remember reading about locking up some of the PICs. What can I do if that is what I did?
I know I tried V1.0 off the SSC programmer on the SSC. That selection is grayed out on V2.0. I know I tried V2.0 on the Zeus, but I may have inadvertently run 1.0 on the Zeus. Again, what if I did? I remember reading some of the wrong versions can make the PIC appear to be locked. If so, how do I un-lock it?
The ss utility for the zeus and ssc are not the same!
So I gather. I might have used the SSC utility on the Zeus. See above.
Even betweem ssc v3 and ssc v4 ... also not the same.
I also rather gathered that, but what about a modded V1? What should it use?
So make sure you program the zues with the ss zeus utility (under zeus in the wiki).
Yeah, I've tried that. As I say, I may have accidentally programmed it with the SSC 1.0 utility.
and make sure you program the ssc v3 mod with the ssc v3 utility (Not the zeus version).
The file name of the version I downloaded is "SSC Utility Setup 7-10-2011.zip", and it has two files with mod dates of 7-10-11 in it.
You might want to download lights and use its tester ... might at least eliminate any potential vixen problems for now.
I may try that. Thanks.
-
Ok, for the pickit3, don't use mplab, but the standalone programmer.
Is that something distinct from the SSC programming utilities?
-
I donot see the connectors for the pickit on the zeus. I would place the chips on my ziff adapter and using the standalone programmer, you can flash the latest firmware to the chip.
As for the etherdongle, it does have the connector to flash it. Just make sure all the regular cables are unplugged first.
As far as testing everything, I would set it up using the simplest setup possible. Less items, less things to go wrong.
-
Ok, easier to type on the computer, than the cell phone.
for the programmer...
http://www.diylightanimation.com/wiki/index.php?title=Software#PIC_Programming
choose the
Pickit3 Stand Alone Programmer Appver 1.0
What model SSC do you have?
(it will say on the pcb)
-
I donot see the connectors for the pickit on the zeus.
The Wiki says it does not need an adapter, which doesn't quite make sense, to me.
you can flash the latest firmware to the chip.
All sixteen of them? Ugh.
-
What model SSC do you have?
The person from whom I bought it said it was a V1 modded to V3. It does have the little jumper on it specified in the Wiki for the V1 mod.
(it will say on the pcb)
Not that I can see. All t says is "Robert Jordan 2010".
My ZIFF adapter looks nothing like the ones in the pictures. I'll need to see if I can make it work with these PICs.
-
To program the PIC's on the Zeus, you are either going to need to pick up a socket adapter like the ones from J1SYS or get your hands on a SSC V4 which uses the same PIC as the Zeus. There is no header on the Zeus for the Pickit because there is no practical way to connect it to a particular PIC on the board. It does use different firmware than the SSC but there is no issue in loading the Zeus firmware on the PIC while it is in the SSC. Just don't try and run it like that. As for MPLAB, make sure to use the IPE version. That is the programmer version. The IDE is the developer version which requires a connection to a compiler and is not needed when loading assembled firmware. The independent programmer has not been fully developed and is really a thing of the past.
-
To program the PIC's on the Zeus, you are either going to need to pick up a socket adapter like the ones from J1SYS or get your hands on a SSC V4 which uses the same PIC as the Zeus.
Or use a breadboard. I have one around here, somewhere.
There is no header on the Zeus for the Pickit because there is no practical way to connect it to a particular PIC on the board.
Well, I disagree, there. The brute force method would be to create the board with 16 individual headers. A little more elegantly, at least 2 of the 5 pins in use are not carrying data. A bank of NAND gates tied to a rotary switch could easily route the data to / from one PIC at a time for the 3 (or maybe just 2) pins that don't need to be tied to only a single PIC. If one of the lines is a serial line, then make that a bank of transcievers. Of course, any such facilities would increase the cost of the build a bit, but not much.
As for MPLAB, make sure to use the IPE version. That is the programmer version.
I think I was using the IDE. I'll give the IPE a shot.
The independent programmer has not been fully developed and is really a thing of the past.
Um, the sentence "Only use the Pickit 3 utility and not MPLAB to program the firmware" is splattered all over the Wiki, including the section for the ETD, the 16 port active hub, and the SSCs. This makes me really nervous. Is the Wiki really that far off?
-
(1) not sure how you flashed the pic(s) for the zeus ... but I'm assuming you knew what you were doing (I use a SSC v4 socket, then connect to pickit2 via ispf)
but any failed attempts to flash can ofter require a reflash of the original PIC firmware ... so if its anything but flash, program with correct ss version ... then you may
need to start over.
(2) sounds extremely likely you didn't use the correct version of smart string utility ... as your v1->v3mod and the zeus both need a distinct version to work.
-
(1) not sure how you flashed the pic(s) for the zeus
I didn't. As I said, I purchased these used frm members of the site.
but any failed attempts to flash can ofter require a reflash of the original PIC firmware ... so if its anything but flash, program with correct ss version ... then you may
need to start over.
I intend that, but I need to cobble together an adapter or wait for the one I have purchased to arrive. MEanwhile I can still work on the ETD and the SSC.
(2) sounds extremely likely you didn't use the correct version of smart string utility ... as your v1->v3mod and the zeus both need a distinct version to work.
Yes, it's not unlikely. What about the notes in the Wiki vs. what tbone321 is saying. I know tbone is an experienced member, but when the Wiki repeatedly says something different, it makes me take pause (literally). I might move forward anyway, but I am getting some results from reading the SSC PIC I don't understand.
-
I wasn't getting consistent results when I first attached the PICKit 3 to the SSC. They seem to be stable, now, however. The checksum reads EE30. According to the Wiki, it should be either E363 or ED60. So am I safe to go ahead and use MPLAB to flash the EEPROM with the Smart+String+controller+modded.hex image? The Wiki talks about loading the PK2DeviceFile profile, but MPLAB wants to see a PK3 file, not PK2, and it seems to recognize the PIC24FJ32GA002 PIC. I've exported the data read from the EEPROM to a safety file and imported the modded SSC file. Should I go ahead and write, then verify? Should I erase, first?
-
There is no header on the Zeus for the Pickit because there is no practical way to connect it to a particular PIC on the board.
Well, I disagree, there. The brute force method would be to create the board with 16 individual headers. A little more elegantly, at least 2 of the 5 pins in use are not carrying data. A bank of NAND gates tied to a rotary switch could easily route the data to / from one PIC at a time for the 3 (or maybe just 2) pins that don't need to be tied to only a single PIC. If one of the lines is a serial line, then make that a bank of transcievers. Of course, any such facilities would increase the cost of the build a bit, but not much.
It is probably more expensive than you think and would make the board much larger and more complicated. The idea here was to keep it simple and at as low a cost as possible. Sure, there could have been further improvements and I would have just put a header for each PIC but I didn't take the time and effort to design the board.
The independent programmer has not been fully developed and is really a thing of the past.
Um, the sentence "Only use the Pickit 3 utility and not MPLAB to program the firmware" is splattered all over the Wiki, including the section for the ETD, the 16 port active hub, and the SSCs. This makes me really nervous. Is the Wiki really that far off?
First of all, you don't need the Pickit 3 to program this particular PIC, the Pickit 2 can program that one. The Pickit 3 was required for the 32 bit PIC that the ETD uses. You really need to take a look at the dates of many of those entries in the WIKI. When many of those entries in the WIKI were written, the Pickit 2 was the PIC programmer but could not program 32 bit and larger PIC's. The Pickit 3 had just came out and while it could program PIC's larger than 16 bit, it was not just a PIC programmer like the Pickit 2, it was actually a low cost programmer / debugger. MPLAB at the time was a contained program capable of both firmware development and PIC programming. The problem with using it was that since it was a development product, it was capable of changing registers and memory locations in the PIC that could cause issues that would be difficult to debug, possibly to the point of bricking the PIC or locking in the firmware so no other updates would be possible. The Pickit 2 had a separate piece of software that was designed for programming only which made loading the firmware much easier and safer. That software was not compatible with the Pickit 3 so there yet another program was created to allow the Pickit 3 to do the same thing. This is the software that the WIKI is referring to. The problem with that one was that the Pickit 3 was released in debugger mode and needs to have its firmware reloaded to put it into programmer mode and this software was unable to do that. This required the user to load MPLAB the first time anyway so that it could update the firmware on the Pickit 3 and many of us would just continue to use it to load the firmware as well since it was already loaded and running and was more than capable of doing it. Now it appears that MPLAB has been split into a development / debugging version (MPLAB IDE) and a simple programming version (MPLAB IPE) that can work with both the Pickit 2 and 3, can properly flash the Pickit 3 to put it into programmer mode, and eliminates the need for the other separate programmer programs.
-
It is probably more expensive than you think
Not so much. I've done a considerable amount of circuit design. Of course, every penny counts, here, and the additional cost per board would fairly soon overtake the cost of a PICKit.[/quote], so it is an understandable choice.
First of all, you don't need the Pickit 3 to program this particular PIC, the Pickit 2 can program that one.
OK.
You really need to take a look at the dates of many of those entries in the WIKI.
Well, I have, of course, but just because they are old does not necessarily mean they are wrong, especially when talking about hardware. Hardware tends to evolve more slowly than software. Firmware is somewhere in the middle.
When many of those entries in the WIKI were written, the Pickit 2 was the PIC programmer
...
Now it appears that MPLAB has been split into a development / debugging version (MPLAB IDE) and a simple programming version (MPLAB IPE) that can work with both the Pickit 2 and 3, can properly flash the Pickit 3 to put it into programmer mode, and eliminates the need for the other separate programmer programs.
OK, that makes sense.
So I should use the modded hex file and write to the PIC, then verify?
-
Keep things simple, remove the switch. Pc to etherdongle to zeus. Verify you have the light hooked onto the board from the starting end and not the finish end. Verify the wires arw correct on the board. Jump the lights onto another terminal block on the board. Verify in vixen the output config is correct. Post any and all pics of the board with wires, software config.
-
I found the problem. When the ZIF adapter came in, I re-flashed all the PICs on the Zeus and then ran the Zeus utility, and everything worked just fine. Going back to the Hub and SSC, I re-flashed them, and... nada. I had understood from reading and the comments here the Zeus SSC utility is different from the regular SSC utility. What I hadn't realized is the SSC utility for the modded V1/2 SSCs is also different from the V1 utility. I copied the SSC V3 file ove the SSC V1 file, and all is well. Honestly, the Wiki could be a bit clearer, and better yet, the version numbers on the software should be different. It would be great if the software also listed right up-front which modules it supports. Better still would be a single, unified SSC / Zeus utility.