Weird issue PanelDue. I think it has a bad SB diode. Ideas?
-
A framing error suggests to me that the ATSAM is no longer transmitting correctly. Assuming you have set your logic analyser to the correct parameters (57600 baud, 1 stop bit, no parity bit) that suggests to me a firmware error or a faulty microcontroller.
-
Probe settings confirmed. 57600, 1 stop bit, no parity. Also- you had asked what screen size I had. That would be 4.3".
I am thinking it's a bad chip and not firmware. But- It may be a "it depends". Some SAM chips have one HW SPI port whereas others may need to be setup as SW. idk.. just thinking aloud.
-
If you are brave, you can try the binary here: https://www.dropbox.com/s/ya3s46660yxvl1t/PanelDue-v3-4.3.bin?dl=0. I haven't tested it, but the 5" build from the same source code seems to work properly so far.
-
AH- that's not brave! Brave is what may come next.. SMD rework
I did try that binary and still a no-go 
. Going to try that SB Diode next and if that doesn't fix it.. then I'll order a few ATSAM4S4BA chips and.. see how it goes.Keep you posted.
-dt -
What happened when you tried the new binary: did it not work at all, or work but had the same issue?
The PanelDue board will work without that diode present. Its main purpose is to provide compatibility with 5V systems by limiting the voltage that can appear on the pins of the ATSAM.
-
I figured it was for that. Hmm.. I could setup some of those probes of Logic Analyzer to Analog mode an analyze voltage. Ah - I just checked the DuetWiFi. It doesn't have any protection. The DuetWiFi's URXD0 and UTXD0 pins plugs directly to pin 75 and 66 of the ATSAM4E8E. So in theory.. I could remote the diode and the 2.2K resistors on the PanelDue board. I just have to bridge over where the resistors were.
-
David - truly puzzling. I left the display disconnected for several days as I worked on other parts of the build. Today I reconnected it for cable length sizing, etc.. and it just works. Typically it would stop working after coming up on a minute of start-up, however it has been on for at least 10 mins and counting. For the record - running v1.21RC1 on DuetWiFi and 1.20b2 on DuePanel.
I'm trading in my CmpEn/Sci degree and going back for a degree voodoo/witch doctor.
-dt
-
I'm trading in my CmpEn/Sci degree and going back for a degree voodoo/witch doctor.
Many would say they are already one and the same.
-
LOL disregard. Stopped working a second ago.
It apparently just does not like me and is messing with me.
Will keep you updated. Should be received new PanelDue board in a week.
-dt
-
If the framing errors are on the PanelDue data out pin, then likely causes are:
1. Intermittent short between that data out pin and something else, in the cable or at the Duet;
2. The pin on the MCU that generates data out is not properly soldered down to the pad, or has a minute solder bridge to an adjacent pin.
I guess there is also the possibility of the crystal oscillator on the PanelDue not running smoothly.
-
interesting - I discovered panel can receive data from Duet. Using WiFi/Web interface I did a print and noticed on the panel that it is getting print status. Ie Temperature readings. But yet on the Panel, it shows I have 4x extruders, but on DuetWiFi.. it is programmed for 1. I'm going to hit the pins with soldering iron.. We'll see if that makes a difference.
-dt
-
Another way to test data reception by the Duet is to use M117 or M300 commands.
-
Status Update: fixed
So hit the R4 and R5 2k2 resistors, D3 sb diode, and output pins with soldering iron. Worked for awhile and then stopped transmitting again, like before. I then removed these resistors and diode and then bridged over where the 2k2 resistors were and voila, PanelDue is working.
So I tested the 2k2 resistors and they are ok, however SB diode seems to be the culprit in this case.
I'll keep you posted if this arises again.
Many thanks for your help
-Drew
