DiyLightAnimation
Hardware => Lynx EtherDongle => Topic started by: mmorlan62 on April 06, 2012,
-
Hi all,
I finally hooked up my newly-built ED and LE boards but experienced zero feedback from the LE channel LED's while running a Vixen sequence. Setup:
Vixen -> 4096 channel sequence -> Lynx_EtherDongle plugin -> cat5 cable -> wired GigiBit switch -> ED -> cat5 cable -> LE
ED:
o power LED is on
o eNet jack link LED is on
o eNet data LED blinks when sequence running
o still set to default DMX channel 001
LE:
o data link LED lit
o 5v OK LED lit
o 3.3v OK LED lit
o when on-board test is run, LED3/DMX is lit
o no lights connected to 120v outputs yet.
o terminator and power jumpers are bridged
When running sequence, ED eNet jack data LED blinks but no other activity.
Other "stupid questions" answered: ;D
o yes, everything is plugged in
o the ED chips are properly oriented
o the LE on-board test runs okay
o LE PIC chip successfully flashed for DMX
Next steps:
o A/B test ED chips by swapping them around - no change
o WHAT ELSE?
Thanks,
Michael
-
Is the Ed flashed for DMX http://diylightanimation.com/index.php?action=dlattach;topic=5765.0;attach=7397 with the DMX firmware? And you have the Vixen 2.1 plugin for the etherdongle? If yes to both, download Xlights and try the hardware testing utility and see if you get any blinky.
-
Also try turning off Virus protection S/W. I had blinking on the Etherdongle, but it wasn't getting to my Hub (not the same set up as yours). Turned off my virus protection and everything fired up.
-
caretaker: yes on both counts. I'll try the xlights util next.
M
-
STILL NO JOY.
I discovered the ED is assigned an IP address by my DHCP server. (Not sure where that info is on the DLA site.) I set up xlights with the following:
Network Type - E131
Port - 10.10.11.255
Universe - 1
Last Channel - 512
I get the same flurry of traffic at the ED ethernet jack but no response from the LE. The LE's DATA LINK LED is on showing, I presume, a physical connection. Should it blink when there is data present?
On a related subject, how does the ED DLL find the ED on the network? There doesn't appear to be a distinctive name when I scan with an IP scanner.
M
-
No the ETD does not use DHCP and will not be set by your DHCP server the address is fixed.
RJ
-
Hi RJ.
Okay, that's odd then. My switch is apparently recognizing the ED as address 10.10.11.255. When I set the xlights network to 10.10.11.254, I get no IP blinky. When I set it to 10.10.11.255, I get IP blinky along with the xTester routines.
EDIT: Oh, nevermind. That 10.10.11.255 address is the VPM gateway on my router. Doh!
What is that ED address? I can try entering it into the xlights network setup.
-
You set the address to the multicast addresses for the E1.31 universe. It is not sending stuff to the ETD it is broadcasting data to the world and the ETD knows what to listen to.
The guys using Xlights posted a image of the correct setup info somewhere can someone point him at it?
RJ
-
Aha! Okay, I get that. I'm still trying to find an E1.31 spec somewhere that would explain everything.
I note some directions in xlights for setting up a multicast network. I'll play with that now.
Thanks for pointing me in the right direction.
While I may get xlights talking to the ETD properly, I presume vixen is already doing so via the ETD DLL.
M
-
http://diylightanimation.com/index.php?topic=7277.msg105282#msg105282
IP Address Universe Last Channel
239.255.0.1 1 512
239.255.0.2 2 512
239.255.0.3 3 512
239.255.0.4 4 512
.
.
.
.
239.255.0.16 16 512
-
Aha! Okay, I get that. I'm still trying to find an E1.31 spec somewhere that would explain everything.
I note some directions in xlights for setting up a multicast network. I'll play with that now.
Thanks for pointing me in the right direction.
While I may get xlights talking to the ETD properly, I presume vixen is already doing so via the ETD DLL.
M
In the wiki I posted a pdf that talks about the e1.31 standard - http://www.diylightanimation.com/wiki/index.php?title=Equipment#Library
Rick R.
-
I found the "Setting up LSP 2 and xLights.pdf" file explaining how to set up xlights with an ETD to run an LOR sequence. I have four universes set up with IP address 239.255.0.1 through 239.255.0.4 now.
No response from the attached LE when I run the xlights tester.
M
-
does the LE show any signs of receving data? there should be a dmx led?
-
Ok best way to test is to eliminate everything you can from the setup.
So for ease of setup this is the basic. Do not skip steps because you know it is ok do it to be sure.
1 - load DMX firmware loaded into ETD from wiki making sure you are getting the ETD DMX firmware.
2 - Load vixen 2.1 not 2.5 / not 3.0 but 2.1 on your computer. if it is not there already.
3 - download the vixen 2.1 etherdongle plugin
4 - start vixen and make a simple seqence with random lights blinking in it with the Etherdongle plugin setup. Almost nothing you have to do to it but set the start channel in the plugin setup.
5 - make sure you use a stright through network patch cable that is good not a crossover like comes with most of the equipment you buy. This needs to be a standard patch cable. hook this from the etherdongle jack that is on the right when looking at the end of the ETD has no lights on it.
6 - hook another cable from you computer to the ETD ethernet jack (has lights). if you computer is not a newer device you may need a cross over cable here. Newer computers will swap it for you if they support this so either type works on them. Other will not. Make sure the Connection light on the ETD ethernet jack lights up. when it is plugged into your computer.
7 - Power the ETD up and the LE up with the start channel of the LE set to 001.
8 - run the Vixen seqence and set it to repeat.
at this point you should see the ETD ethernet lights change when the seq is running and calm down when you stop it.
this setup has little to configure so it is easier to troubleshoot with then what you are doing . When you have to configure a lot it gives you more places to make mistakes. Once it is working then you go back to the more complicated and if it does not work you know you configuration is the problem.
RJ
-
RJ, I'll get back to basics, as you suggest, and report back.
Thanks,
M
-
Okay, here is my test setup with negative test results. Where do we go from here?
Michael
----------------------------
ETHERDONGLE PROGRAMMING:
o Connections:PICkit 3 Programmer -> USB cable -> PICKit 3 -> ETD ICSP header
o Device: PIC32MX795F512L
o Imported: EtherDongle_DMX.hex
o Clicked [Write]
o Received: "Erasing device... done"
"Programming device... Program... Boot... Config... done"
o Clicked [Verify]
Received: "Verifying device... Program... Boot... Config... done"
VIXEN:
o Already using Vixen 2.1.4.0 with Lynx+EtherDongle.dll plugin.
o New Vixen Standard Sequence
- 100ms step timing
- 16 channels
- Lynx_Etherdongle plugin with ch1-16 assigned to it
- 10second sequence
o Created a random sequence across all 16 channels
PHYSICAL:
o Laptop -> Cat5 cable -> ETD -> cat5 cable -> LE DMX In
o LE booted with default settings and "001" displayed on 7-seg LED.
o Laptop and ETD jacks have green connection LED lit with regular patch cable.
o LE DMX terminator jumper bridged
o LE DATA LINK LED lit.
RAN VIXEN SEQUENCE:
o Laptop and ETD Ethernet jack yellow activity LEDs blink.
o Tried different ETD->LE Cat5 cable.
NOTHING FROM LYNX EXPRESS
-
Here are pics of my builds:
(http://talltalepictures.com/projects/DLA_EtherDongle_1_Build_0002.JPG)
(http://talltalepictures.com/projects/DLA_EtherDongle_1_Build_0004.JPG)
(http://talltalepictures.com/projects/DLA_Lynx_Express_1_Build_0001.JPG)
(http://talltalepictures.com/projects/DLA_Lynx_Express_1_Build_0008.JPG)
Michael
-
Last question, we know the LE works already am I correct?
RJ
-
I believe you optocoupler chips (white chips) are in backwards. It looks like the pin one marker, the little circle in the top of the chip is on the top rht and should be to the bottom left like the other four chips above them. This would make the unit work but not send out data and could cause power issues.
If this is true swap them around.
Was there a substitiion on these parts in the coop I was unaware of? none of mine are white they are black chips?
RJ
-
I have been in both EtD coops and all of my optos are white. My optos are oriented as shown in the top picture and my EtD is working.
-
The white ones from Fairchild have a decorative "F" in the corner opposite PIN 1.
My eD from the first coop shipped with the white ones.
:) joe
I believe you optocoupler chips (white chips) are in backwards. It looks like the pin one marker, the little circle in the top of the chip is on the top rht and should be to the bottom left like the other four chips above them. This would make the unit work but not send out data and could cause power issues.
If this is true swap them around.
Was there a substitiion on these parts in the coop I was unaware of? none of mine are white they are black chips?
RJ
-
Ok good I see I used what I had on the last couple but the proto did have them <fp. !!
I have too much going on and am losing my mind!!!! nothing new (Nothing to see here folks just keep moving along!)
Although there are currently two post about dongle issues and I believe these are opposite on the two peoples units so someone has them backwards.
Let me go look again.
No these chips are in backwards guys, the pin 1 on the 8 chips are all in the same place on the pcb and these dongle does not have them correct.
RJ
-
Never mind what I am seeing as the pin 1 dot is the little F it just looked like the dot.
(keep moving along folks, nothing to see!)
RJ
-
I don't know If I'm getting output from the ETD.I suppose I could build an RJ45-XLR adapter and rent a DMX instument to test it.
Anything else?
M
-
When the DMX cable to the Lynx Express is disconnected, the DATA LINK LED should be off. If it comes ON when the EtD is connected then you know something is coming out of the EtD.
Is the LE known to work or is it new too?
-
Both the LE and ETD are new and being tested together. Not an optimal testing environment, I know.
The LE DMX LED is lit when connected to the ETD then off when disconnected.
Does the ETD output a constant stream of DMX?
M
-
Everyone have a great holiday weekend, and thanks for the advice and insight thus far. I look forward to picking up this thread next week.
Best,
Michael
-
I noticed in your first post you have a cable going from the laptop to the ED, others have reported a problem with communication when connecting this way and had to use a cross-over cable, if you have Ethernet Switch try plugging into the the laptop into the switch and the ED into the switch OR try a cross over cable. You can download this program http://www.wireshark.org/download.html which will allow you to capture packets and see what is (or isn't) going on as far as communications between the computer and the ED. I know when I got my ED working and tried plugging it into my current router (Netgear WNDR 3700-2) it would not recognize the ED (I found out it doesn't do multicast) so I broke out my old Netgear RT311 along with a Netgear FS105 (Fast Ethernet Switch) and connected to my show computer and it was instantly recognized and works great.
-
Hi Jeff,
Actually, my first setup included a gigabit switch between laptop and ETD. I took I out to simplify. The direct cat5 patch between laptop and ETD shows the exact same results - cat5 link and activity LEDs at each end.
M
-
For some reason I am wondering if Vixen is configured correctly and I don't mean just the etherdongle setup, but all the other options. no one seems to be asking about this. I am not a vixen expert, but others on this board are.
-
I'm just getting started and built my first EtherDongle and Express. Had it connected to the computer and couldn't get Vixen to even run the test sequence until I increased my channel count in my Vixen routine to 2048. Did that and it's running fine now.
-
RAN VIXEN SEQUENCE:
o Laptop and ETD Ethernet jack yellow activity LEDs blink.
o Tried different ETD->LE Cat5 cable
Does the green LED activity light on the ETD also come on and flash as the sequence runs?
Be sure the “Remove for wireless†jumper on the LE is jumped as you are not wireless and need it on.
You do not need to configuar anything else in vixen for the ETD. I would try to create a test sequence of 4096 channels in vixen. Then use vixens channel tester function and click the select all channels button. Than as you move the slider up and down you should see all the activity lights flash (well shimmer it is very quick but is noticeable)
In doing it this way it does not matter what channel your LE is set to as all channels are getting the command.
Just some things I would check for.
Jeffry
-
Jeffry,
Yep, done all that. All connections and lights are playing between laptop and ETD. We're now suspecting the LE but I don't have another DMX device with which to check the ETD so I can be sure.
Meh.
M
-
Does the Lynx Express power up with the "Lynx express... 60Hz" scrolling on the LED display? After power up it should show "001" as the starting channel number.
-
PK,
Yep, LE boots just find and passes the test sequence as described in the build webpage.
M
-
Try this sequence and see if it works for you.
-
Jeff,
I will. Thanks.
M
-
No joy with Jeff's sequence. <md..
So, to bring everyone up to date:
Vixen 2.1.4 -> Lynx_EtherDongle 2.1 plugin -> cat5 cable -> ETD -> cat5 cable -> LE
VIXEN:
o 2048 channel sequence
o EtherDongle plugin
o random sparkle set up in channels 1-16
ETD:
o all chips installed correctly
o power LED is on
o eNet jack link LED is on
o eNet data LED blinks when sequence running
LE:
o PIC chip successfully flashed for DMX
o all chips installed correctly
o when on-board test is run, LED3/DMX is lit
o data link LED lit (when Cat5 connected)
o 5v OK LED lit
o 3.3v OK LED lit
o 7-segment LED reads "001"
o terminator and power jumpers are bridged
o no lights connected to 120v outputs yet
When running sequence, Laptop and ETD eNet jack data LEDs blink but no other activity.
A BIG NOTE: I have yet to attach a load to the LE. I've just been relying on the channel LED's to light up as they do during the on-board diagnostic.
-
Have you tried the "all lights on" feature of the LE, to verify the LED's are all working?
-
This probably sounds silly, but put the ETD board against a bright light – I used a 100W incandescent - component side towards you and solder side towards the light so you can see (sorta) through the PCB.
One of my ETD’s had a solder bridge between pin 1 and pin 2 on the PIC (and a pair of other PIC pins) and with the light shining through, I could see the ever-so-tiny bridges! (Believe it or not, I inspected every pin over and over with a fairly powerful magnifying glass and a microscope and I still missed the bridge!)
A little flux, a little solder wick and whoosh, the bridges were gone! ETD works perfectly now!
:) joe
-
bisquit - All the LED's light during the on-board test. Is that what you mean?
joe - I took a high-rez photo of the solder side and zoomed in to review everything. Maybe, I'll take another look. (That image is linked in a previous post.)
M
-
In an interesting turn of events, the LE on-board test now results in a "Led 3 / DMX" light NOT illuminated at the end of the test (although the "DATA LINK" LED still lights up when I connect the DMX input to the ETD.}
Might I have a marginal RS485 chip? I have some extras in my personal inventory.
M
-
Try a different Cable also.
RJ
-
Of course. More A/B testing.
Also, I need to eliminate a variable and rent a DMX instrument to test the ETD by itself.
M
-
I'm going to build an RJ45-XLR adapter cable. I noted the single-universe diagram but couldn't find the 4-universe RJ45 pin-outs. (I thought I saw that somewhere but have lost track.)
M
-
Try the wiki library
http://www.diylightanimation.com/wiki/index.php?title=Equipment#Library
first pdf = pixelnet Specs (draft)
page 6
Rick R.
-
SUCCESS!!
Well, sort of. I have the LE responding perfectly to a DIY DMX tester I built with a;
- Boarduino;
- the Tinkerit DmxSimple library;
- an RS485 chip, and;
- a bare-wire to RS485 patch cable.
The Arduino runs a simple 1-512 ramp cycle on channels 1-16.
So, the LE is working.
This, at least, isolates our problem to the ETD. (Good thing since this entire thread has been in the ETD sub-forum. :)
So;
FAIL...
Now that I've isolated the problem to the ETD, what board-level diagnostics may I perform? I don't have a scope or logic probe yet. (That's next on my list.)
Thanks to everyone who has helped thus far. Despite my frustration with the hardware, I've really enjoyed the support and graciousness of everyone here.
Michael
-
Have you done a packet trace yet to see what packets are going from Vixen to your ED? I would check that first to see if Vixen is talking to the ED and if that is good then trouble shoot the DMX output of the ED.
-
caretaker - not sure how to do that. I installed Wireshark but the interface is so dense I don't know where to begin.
Here's a new problem: I believe I've burned out two RS485 chips on my DIY tester. They both got damned hot and the LE stopped responding. After a cool-down, the formerly hot chips still don't work. Is it possible I have the data lines reversed? What might be causing this? The chips are the Maxim MAX485 wired per this page:
http://www.arduino.cc/playground/DMX/DMXShield (http://www.arduino.cc/playground/DMX/DMXShield)
Meh.
-
What vo;tage were you powering the 485's with. An over voltage will cause them to get hot. I don't believe that they have a thermal shutdown so if they stopped working, they probably were toasted. Also, you did just use pins 6 and 7, right. The refrence signal is not used.
-
caretaker - not sure how to do that. I installed Wireshark but the interface is so dense I don't know where to begin.
Meh.
Start Vixen and load your sequence and then start Wire Shark. On the left side of Wire Sharks screen is a box marked "Capture" below which is "Interface List" select that and it will show you what interfaces you have connected to your computer (most likely just your network interface) select that and hit start then start your routine in Vixen and Wire Shark will show if any packets are being sent to the ED. Once you can confirm whether packets are being sent or not you can stop the capture and if they are you can save the results RJ or someone else here will be able to tell you if the right info is being sent to the ED.
-
The 485 chip should not get hot.
I would not put the 100 ohm resistor in the circuit. Maybe a 1k... That resistor is just loading an unused output, which is going to draw a fair amount of current depending on the output voltage... If its 5v TTL it could pull 50 mA, which would make the chip warm.
RM
-
re: DIY DMX Tester:
The voltage drop across the rails supplying the RS485 is around 4.3v and I doubled-checked the wiring so I'm not sure why the chip is overheating. I'll try the 1k resistor to reduce current across those pins. Odd that no one has challenged the 100ohm value since that circuit has been on-line.
(Let's drop this DMX Tester thread since it's outside the bounds of this forum. We've determined the LE is working now.)
--------------------------------
re: ETD Packet Trace
I captured the packet stream going to the ETD. At first glance, it appears to be correct. See attached Wireshark output file.
-
Are you sure you are running DMX? When I looked at you Wireshark packet, it shows Pixelnet. I just tried wireshark with my ED, using xLights, and it shows xLights as the output.
-
bisquit476: All I know is I'm sending packets from Vixen to the Lynx_EtherDongle plugin. I have no control over the content of those packets. I presume it is the job of the EtherDongle to interpret the packets based on its firmware load.
This particular stream was generated from a Vixen file with 16 channels and a random blink pattern.
Michael
-
Hi Michael,
I've attached a couple of pictures of how the xLights setup is on my computer, maybe try that and see if it works. Good Luck,
Bill
-
The reason I say try xLights is because that is what I used and got it to work. If your computer is putting out pixelnet, and your ED is flashed with DMX, (which according to how I'm reading your Wireshark file is being output from the computer) it will not work. The computer is outputting one protocol and the ED is set to receive another. I hope I'm explaining this correctly,
Bill
-
I understand your explanation and will try xlights again, following your setups screenshots.
Michael
-
Hmmm,
My assumption is that the e1.31 packet would be the same, regardless of the etherdongle firmware.
A DMX etherdongle would just receive and output 4 e1.31 universes as 4 universes of DMX and the pixelnet version would receive 32 e1.31 universes and output the data as 4 pixelnet universes.
The e1.31 specification doesn't address other protocols like pixelnet...
RM
-
When I looked at your wire shark listing, I didn't see any channels turned on. All of the channel data was zero...
-
Yeah. I was wondering about all the blank data. The header info is obviously in each packet so there doesn't appear to be a firewall filter or other such hindrance. What's up with the rest?
I attached a screenshot of the sequence window with the 16ch sequence.
I also attached a Wireshark capture of a 512ch sequence with 25ms frame rate. Still looks empty.
Back to xlights next.
(I'm running on a laptop with Win7 64bit Home Premium.)
M
-
I do believe RJ has stated that 50ms is what the EtherDongle was designed to support. Now I am not saying that is the reason but I can't hurt to try a new sequence at 50ms instead of the 25ms.
Rick R.
-
Here is a;
vixen 50ms network capture and;
xlights network capture with the "twinkle 50%" test running.
The data packets still are empty beyond the header info.
Incidentally, the output from my desktop Win7 system is the same as the laptop.
In a separate question, how does the Lynx+EtherDongle plugin know which Ethernet port to use when there are multiple ports on the system?
-
OKAY, to catch everyone up on this thread:
PHYSICAL:
Both the ETD and LE seem to be good physical builds. The ETD Ethernet chip has a solder bridge between pins 35 and 36 which no one seems to believe is a cause for alarm.
All Ethernet jack Link LED's light when connected and Activity LED's blink with activity. The LE DMX LED lights when connected to the powered ETD and to my DMX tester.
The LE tested positive when I fed DMX from a DIY Arduino/RS485 tester. All channel LED's ramped up with the programmed test. We'll presume the LE is working as it should.
NETWORK:
Wireshark network snooping reveals what appears to be packets with headers but little else. Without knowing the E1.31 protocol better, I can't say more. Packets are getting through with headers so one might assume there aren't any firewall issues. I did receive a firewall challenge with xlights at one point and I allowed xlights to continue.
PROGRAMS:
Vixen 2.1.4 with Lynx+Etherdongle 2.1 plugin.
xlights with E131/239.255.0.1 network type.
-
Let back up one poster. There is no difference in what goes to the Etd no matter what you haveit flashed. The computer no matter what software you are using send E1.31 packets. There should be some data not all zeros if you are turning lights on. If you send a all zero channel data packet you will not turn any lights on.
If the ETD network light is Blinking when the data is being sent and stops when you stop Vixen then. it is likely the ETD is getting data. Are we sure we are sending something to the correct channels to make the express react?
This really sounds like a setup problem but maybe this is just me.
Are we sure the cable between the ETD and Express is a straight through and good?
We are sure we are programmed with DMX on the ETD and not pixelnet?
Amy one of these would do just what you are seeing.
RJ
-
RJ,
Everything you write makes perfect sense. I have A/B tested every software and physical component of this setup (besides the LE and it turned up functional when I drove it from my DIY DMX tester.)
So, I wasn't getting any ENet packet data after the E1.31 header before but now I am. (I have no idea why.) Below, is a frame for Universe 1 of a random pattern in Vixen. I can also see each of the four universes being sequentially output in separate packets in the Wireshark capture file.
I have flashed the ETD with DMX firmware multiple times.
I can see the ETD ENet jack LED getting banged by the laptop.
I can see the LE DMX LED lit the moment the ETD is connected and powered.
I have successfully driven the LE with a DIY DMX tester.
We seem to be isolating the problem down to the EtherDongle at the component level.
----------------------------------------------------------
No. Time Source Destination Protocol Length Info
1 0.000000 169.254.176.207 239.255.0.1 UDP 680 Source port: 57119 Destination port: sdt
Frame 1: 680 bytes on wire (5440 bits), 680 bytes captured (5440 bits)
Ethernet II, Src: CompalIn_57:46:63 (88:ae:1d:57:46:63), Dst: IPv4mcast_7f:00:01 (01:00:5e:7f:00:01)
Internet Protocol Version 4, Src: 169.254.176.207 (169.254.176.207), Dst: 239.255.0.1 (239.255.0.1)
User Datagram Protocol, Src Port: 57119 (57119), Dst Port: sdt (5568)
Data (638 bytes)
0000 00 10 00 00 41 53 43 2d 45 31 2e 31 37 00 00 00 ....ASC-E1.17...
0010 72 6e 00 00 00 04 31 20 4f 5c 2b a9 0f 48 9c 02 rn....1 O\+..H..
0020 fe dd f2 dd b1 e7 72 58 00 00 00 02 50 49 58 45 ......rX....PIXE
0030 4c 4e 45 54 00 45 54 48 45 52 44 4f 4e 47 4c 45 LNET.ETHERDONGLE
0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060 00 00 00 00 00 00 00 00 00 00 00 00 64 00 00 00 ............d...
0070 00 00 01 72 0b 02 a1 00 00 00 01 02 01 00 ff 00 ...r............
0080 ff ff ff ff 00 ff ff ff ff 00 ff ff ff ff ff 00 ................
0090 ff ff 00 ff 00 ff ff 00 ff ff ff ff ff ff 00 ff ................
00a0 ff ff ff ff 00 ff ff ff 00 ff ff ff ff ff ff ff ................
00b0 ff ff 00 ff ff ff ff ff 00 ff 00 ff ff 00 ff ff ................
00c0 ff ff ff ff 00 ff ff ff ff ff 00 00 ff 00 ff 00 ................
00d0 ff ff ff 00 ff ff 00 ff ff ff ff ff 00 ff ff ff ................
00e0 ff 00 ff ff ff ff ff ff 00 ff ff 00 00 ff ff ff ................
00f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff 00 ff ................
0100 ff ff ff ff 00 ff ff ff ff ff ff 00 ff ff ff ff ................
0110 ff 00 ff ff ff 00 00 ff 00 ff ff ff ff ff ff ff ................
0120 ff ff 00 00 ff ff ff ff ff ff ff ff ff 00 ff ff ................
0130 ff ff ff 00 ff ff ff ff ff ff ff ff ff ff ff ff ................
0140 ff ff 00 ff 00 ff ff ff ff ff ff ff ff ff ff ff ................
0150 ff ff ff ff 00 ff ff ff ff ff ff ff 00 ff ff ff ................
0160 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
0170 ff ff 00 ff ff ff ff ff ff ff 00 ff ff ff ff ff ................
0180 ff 00 ff ff ff ff 00 ff ff ff ff ff ff ff ff ff ................
0190 ff ff ff 00 ff 00 ff 00 ff 00 00 ff ff ff ff ff ................
01a0 ff ff ff ff ff ff ff ff ff ff ff ff 00 ff ff ff ................
01b0 ff ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff ................
01c0 ff ff ff ff ff ff ff ff ff ff 00 ff ff ff ff 00 ................
01d0 ff ff 00 ff ff ff ff ff ff ff ff 00 ff ff ff ff ................
01e0 ff ff ff ff ff ff ff ff ff ff ff ff 00 00 ff 00 ................
01f0 ff ff 00 ff ff ff 00 ff ff ff 00 ff ff ff 00 00 ................
0200 ff ff ff ff ff ff ff ff 00 ff ff ff ff ff 00 ff ................
0210 ff ff ff 00 ff ff ff ff ff ff ff ff 00 ff ff ff ................
0220 ff ff 00 ff 00 00 ff ff ff ff 00 00 ff ff ff 00 ................
0230 ff 00 ff ff ff ff ff 00 ff ff ff ff ff ff ff ff ................
0240 ff 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
0250 ff ff ff ff ff ff 00 ff 00 ff ff 00 ff ff ff ff ................
0260 ff ff ff ff 00 00 00 ff ff ff ff ff ff ff ff ff ................
0270 ff ff ff ff ff ff ff ff 00 00 00 ff ff ff ..............
-
Ok lets assume it is on the output side not the input then.
On the four sets of 8 pin chips swap the set closest to the cat 5 jack with another set of them to make sure we do not have a bad opto or 485 chip. Look over the solder connections on those two chips and the cat5 jack ect.
Does sound like you are getting ethernet info.
RJ
-
RJ,
Yep. That was one of my first A/B tests. Did it again, per your instruction.
I retouched some of the solder points, especially those where the solder hadn't fully flowed around both sides of the vias. All soldering looks good per my photo uploaded earlier in this thread. All DIP's properly inserted.
Output random sparkle via xlights,
Wireshark sees good packets
All comm lights are lit and blink.
No reaction from LE.
M
-
Here's a question: Is my DMX Cat5 cable simply too short? Would there be some ringing/oscillation issues or A/C loading issues caused by a 1-foot cable connection?
-
I feel like we're moving beyond my ability to debug this problem (and everyone's most gracious patience) without a "Theory of Operation" or "Service Manual" type document and a scope/logic probe.
Before I go investing in a logic probe, is there anyone to whom I can send my boards so they can give them a quick once-over?
Michael
-
Try downloading the plugin from here http://diylightanimation.com/index.php?action=dlattach;topic=3554.0;attach=6342 it is the older version of the plugin from the software page and it works for another user but he couldn't get the new plugin to work.
-
Jeff, I'll try the older plugin however, my WireShark packet sniffer reveals I'm sending packets to the E1.31 world. (Perhaps, there's a formatting error in the packet? No one has commented. A brief comparison of the packet to the E1.31 spec seemed to check out.)
Rick AKA rmp2917 has graciously offered to take a look. He's away until the 26th when I'll be shipping my boards and notes to him for review. He has a scope, access to a logic probe, and a general knowledge of the operation of the ETD, so yay!
Best,
Michael
-
Hi Michael,
There was activity showing on the ED (green and blinking yellow on the Magjack) with the new file, but the LE didn't work until I went with the older software.
-
Ah. Interesting.
I'll have some time to test it next week. Away from the house through the weekend.
Best,
M
-
After all this I am still suspicious of a Vixen problem, esp since you are a new vixen user (at least it sounds like that) and problems like this crop up all the time when people first start with vixen. Everyone is concentrating on hardware, but no one is asking about the overall vixen setup. Not just the ED plugin, but also other preference issues.
-
Can anyone comment on the E1.31 packets I've posted to this thread? If Vixen is outputting E1.31, I'm not sure how I could be failing with my setup. It's not that complex.
Michael
-
Michael, when I get a chance this weekend I will capture and post the data packets of Vixen communicating with my ED controlling a Lynx Express
-
caretaker,
Excellent. Then we can compare yours against the ones I've posted here and against the E1.31 spec.
Best,
Michael
-
Ok below is a packet capture from Vixen 2.1.10 to the Etherdongle: I was running the attached sequence which is 2048 channels of which I have 16 set up randomly flashing. My Lynx Express picked up the data and flashed it 16 led's in the random pattern. I am running this on my show computer (Windows XP - Athalon XP 1800+ 768GB Ram) to a NetGear FS105 fast switch (which the ED is connected to) which is connected to a Net Gear RT311 router which is multicast capable. If you PM me I will give you the complete wireshark capture and the vixen file if you want them.
Some notes in setting up Vixen with the ED, make sure the ED is plugged in and connected before opening Vixen and setting up the the output plugin in your profile. It should look like this:
(http://)
0000 01 00 5e 7f 00 01 00 a0 cc 3b 36 a7 08 00 45 00 ..^..... .;6...E.
0010 02 9a c3 30 00 00 01 11 41 b0 c0 a8 01 ca ef ff ...0.... A.......
0020 00 01 08 1c 15 c0 02 86 1d 2a 00 10 00 00 41 53 ........ .*....AS
0030 43 2d 45 31 2e 31 37 00 00 00 72 6e 00 00 00 04 C-E1.17. ..rn....
0040 31 20 4f 5c 2b a9 0f 48 9c 02 fe dd f2 dd b1 e7 1 O\+..H ........
0050 72 58 00 00 00 02 50 49 58 45 4c 4e 45 54 00 45 rX....PI XELNET.E
0060 54 48 45 52 44 4f 4e 47 4c 45 00 00 00 00 00 00 THERDONG LE......
0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0090 00 00 00 00 00 00 64 00 00 00 00 00 01 72 0b 02 ......d. .....r..
00a0 a1 00 00 00 01 02 01 00 00 a6 00 00 d0 00 d4 00 ........ ........
00b0 67 00 49 c9 00 bf e2 00 00 00 00 00 00 00 00 00 g.I..... ........
00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
01a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
01c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0200 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0210 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0220 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0230 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0240 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0250 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0260 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0270 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0280 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0290 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
02a0 00 00 00 00 00 00 00 00
-
Jeff,
I'm not sure what the pixelnet.dll plugin you linked to in a previous post is about. It was seeking a COM port and was definitely not talking to Ethernet.
Here are the E1.31 headers from your EtherDongle packet and mine. Why, I wonder, do they bear absolutely no relation to each other?
Jeff's Vixen 2.1.1.0:
0000 01 00 5e 7f 00 01 00 a0 cc 3b 36 a7 08 00 45 00 ..^......;6...E.
0010 02 9a c3 30 00 00 01 11 41 b0 c0 a8 01 ca ef ff ...0....A.......
0020 00 01 08 1c 15 c0 02 86 1d 2a 00 10 00 00 41 53 .........*....AS
0030 43 2d 45 31 2e 31 37 00 00 00 72 6e 00 00 00 04 C-E1.17...rn....
0040 31 20 4f 5c 2b a9 0f 48 9c 02 fe dd f2 dd b1 e7 1 O\+..H........
0050 72 58 00 00 00 02 50 49 58 45 4c 4e 45 54 00 45 rX....PIXELNET.E
0060 54 48 45 52 44 4f 4e 47 4c 45 00 00 00 00 00 00 THERDONGLE......
0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Michael's Vixen 2.1.4.0 w/Lynx+EtherDongle:
0000 00 10 00 00 41 53 43 2d 45 31 2e 31 37 00 00 00 ....ASC-E1.17...
0010 72 6e 00 00 00 04 31 20 4f 5c 2b a9 0f 48 9c 02 rn....1 O\+..H..
0020 fe dd f2 dd b1 e7 72 58 00 00 00 02 50 49 58 45 ......rX....PIXE
0030 4c 4e 45 54 00 45 54 48 45 52 44 4f 4e 47 4c 45 LNET.ETHERDONGLE
0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060 00 00 00 00 00 00 00 00 00 00 00 00 64 00 00 00 ............d...
0070 00 00 01 72 0b 02 a1 00 00 00 01 02 01 00 ff 00 ...r............
Michael's xlights:
0000 00 10 00 00 41 53 43 2d 45 31 2e 31 37 00 00 00 ....ASC-E1.17...
0010 72 6e 00 00 00 04 c0 de 00 80 c6 9b 11 e0 95 72 rn.............r
0020 08 00 20 0c 9a 66 72 58 00 00 00 02 78 4c 69 67 .. ..frX....xLig
0030 68 74 73 00 00 00 00 00 00 00 00 00 00 00 00 00 hts.............
0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060 00 00 00 00 00 00 00 00 00 00 00 00 64 00 00 90 ............d...
0070 00 00 01 72 0b 00 a1 00 00 00 01 02 01 00 ff ff ...r............
According to the draft E.131 standard (E1-31r3.pdf) your header isn't formatted correctly. How is your EtherDongle even working? (For instance, the ACN Packet Identifier "ASC-E1.17" should run from bytes 4 through 15, and the Source Name should run from byte 44 through 107.
Even weirder: Why does the About dialogue of my Vixen read as version 2.1.4.0 but the latest version available on the website is 2.1.1.0?
Michael
-
Hi Michael,
Have you tried the old version of the output plugin yet?
-
I've tried ver 1 and ver 2.
M
-
Even weirder: Why does the About dialogue of my Vixen read as version 2.1.4.0 but the latest version available on the website is 2.1.1.0?
Michael
You probably updated, that's the latest update, why it isn't shown on the website, I don't know,
Bill
-
Okay, I've shipped my ETD and LE off to Rick Perry aka. rmp2917, who is being kind enough to scope and probe my boards.
I'll report back his findings (if he doesn't himself.)
Regards,
Michael
-
SOLVED!!
Rick aka rmp2917 discovered a solder bridge between pins 40 & 41 of the Ethernet chip. A little flux and solder braid and the bridge was removed and the board functional.
Here's Rick's troubleshooting procedure in his own words:
"To start with, I setup my equipment to provide a known working test bed. Since I have 2 ED’s, I have one setup for PixelNet connected to a smart string and one for DMX connected to a Lynx Express. I used xLights to test the units. It was easier to setup and use the test panel instead of using Vixen.
"I connected your LE in place of mine and everything was working fine. Each of the channel LEDs responded according to values I was sending from xLights. I connected a string of lights to all 16 outputs to verify that they actually lit.
"Now that I knew the LE was OK, I moved on to the EtherDongle. I placed your ED in place of mine. Everything appeared to be working. However, there was no response from the LE. At first I thought there may be an issue on the output side, so, I made an adapter that allowed me to connect the LE on universe 4. I got the same result.
"The Ethernet chip seemed to be receiving data from the PC since the LEDs on the jack were responding appropriately. Also, the PIC seemed to be sending data to the LE since the data LED on the LE was lit. Also, after removing my ED, the channels were still on and as soon as I plugged yours in all channels turned off. This led me to believe that there was an issue with communication between the PIC and the Ethernet chip. So, I started checking those connections.
"I found that pins 40 and 41 of the Ethernet chip seemed to be shorted. The resistance on yours was 0.9 Ω while the resistance on both of mine was 6 point something MΩ. I looked for possible shorts on the board, but could not find any. So, I started looking at the chip itself. It looked like there might have been a little solder between the pins, but it was really hard to tell. I used a flux pen to add some flux to the pins. Then, I used solder braid with a fine tip on the soldering iron to remove the solder. The resistance between the two pins was now 6 point something MΩ.
"I reconnected the ED and ran through the test again. Everything was now working and the LE was responding as expected."
So, there ya go.
A big huge shout out to Rick aka rmp2917 for his most excellent service, not only to me, but to the DLA community. If it would serve the site, I'll write an ETD troubleshooting guide based on the experiences of this thread and Rick's work.
Best to all,
Michael
-
Glad to see you got it working! I was following the thread and hoping you would get the problem resolved!
-
Congratulations! I'm glad you got it fixed.
Was your etherdongle from the first coop (last year) or the recent one?
There was some trouble with the SMDs from the first coop, but I was thinking those problems were eliminated in the second coop.
Also I feel compelled to give the general warning - messing with the surface mount components should be the last resort when all other possibilities have been eliminated. Most of us do not have the proper tools and it is really easy to damage the chip such that it cannot be repaired.
While it seems like the SMD is the major issue, it really is not - It just gets the most discussion. For every SMD related problem, I would be willing to bet that there are 50 other issues that are resolved by the individual without ever posting. Things like solder bridges, chips in backwards, cold solder joints, wrong component, etc.
RM
-
Thanks RM.
This ETD was from the most recent coop.
That's a good point regarding frequency of SMD soldering issues. There are so many tests we tried as part of this thread before resorting to suspecting the SMD. Anyone troubleshooting a board should start with a thorough review of their build, assuring they have everything soldered in the right place and orientation and that all soldering is clean. (For example, I had soldered sixteen resistors on the LE board before realizing they were in the wrong place. So, check and check again during your build. Then check again afterwards.
I think this thread is a great encapsulation of the ETD troubleshooting process and should serve as a fine source for a troubleshooting manual page in the Wiki. Would it be of value for me to format a troubleshooting doc from this thread?
Michael
-
AWESOME! <res.
-
Glad it is working for you