Etherdongle problem - No blinky (SOLVED)

[diceman3807]

I built my first etherdongle and have a problem. In checking previous posts, I have checked everything I think but still can't find the issue. I have setup my conductor either directly connected to my laptop, or through a hub. In testing with both Vixen3 and XLights. When I hook up the etherdongle, I get connectivity lights on the MagicJack, and the yellow activity light blinks rapidly when I push a sequence. I get a DMX connectivity light on my LE, but not activity occurs. If I go back to Vixen 2.1 with a USB Dongle, the LE works. I configured Xlights to use E131, universe 1, multicast, last channel 512, and my LE is showing 001 on the display.

I have included pictures here of my board...

[txag2008]

Just for technicality sake, that's an Etherdongle not a Conductor.  Hopefully you've just confused the names.

[diceman3807]

Whooops...I was thinking about the next step when I put this together...I corrected the original. Thanks!

[jnealand]

Hopefully, you flashed using the etherdongle firmware and not the conductor firmware.  Many problems have been due to cables or how you connect the ETD to the network / PC so that is probably the place to concentrate.

[rdebolt]

To add to Jim's post. Also make sure that it was the DMX firmware not Pixelnet as an LE will not work with pixelnet.

[diceman3807]

Well, I'm going back through my processes, and going to reprogram the chip. I have PICkit 3 program 3.10.00, and downloaded the PK2DeviceFile, and put in in my directory, so the when I hook up the programmer it detects the PIC32MX795F512L, but when I import the DMX hex file, the checksum comes back as 69DE, not the 0000 that the wiki has stated. (when i read the existing file it also say 69DE)

Any ideas?

[tbone321]

You should never get a checksum of 0000.  There was a point in time where the Pickit3 was not producing a checksum.  This was probably a programmer software issue and appears to have been corrected.

[diceman3807]

Do you know what the new checksum should be then? The wiki still shows the 0000

[tbone321]

Until smene updates it, that is what it will continue to say.  Have you loaded the firmware into the PIC yet?  What software are you using with the Pickit-3 t load the firmware?

[diceman3807]

I am using the PICkit 3 Programmer (not the MPLAB) app version 3.10.00. I have loaded the DMX software a couple of times.

Are you saying that the Checksum that shows up in the programmer should still read 0000 then?

[tbone321]

No, what I'm saying is that what you are seeing is prbably what it should be.  Version 1 just returns 0000 probably because the code that actually performs the function probably didn't exist yet in that version. 

[twooly]

Use the pickit software version 1, known problems trying to flash with the version 3

[tbone321]

It appears that some f these issues have been resolved.  As Ver 3 continues to be upgraded these issues will continue to disappear.  Ver 1 works but is incomplete and I will start using ver 3 with ver 1 as a fallback until ver 3 is completed.  The primart issue with 3 was that it couldn't see the PIC and was unable to flash it.  It appears that this versin has resolved this, at least as far as the PIC used by the ETD is concerned.  I will have to give it a shot with the SSc and see if it works there as well.

[diceman3807]

Thanks guys for all the help. I was searching other threads and one of them mentioned a solder bridge on the Ethernet chip. I did a hard look and I think I might have one between pins  35 and 36. I'm going to attempt to see if I can clean it up. Any tips on how to do this?

Sent from my Nexus 10 using Tapatalk 4

[tbone321]

Some pins actually are supposed to be connected.  Is there an actual problem with the EDT or is all of this based on the checksum value that you are seeing.  Cleaning up bridges on pins this tight requires some skill and the right equipment.  If the EDT is not working then I would PM RJ and give him the pin number that appear to be bridged.  He will let you know if this is a problem and some suggestions on how to resolve it if it is.