Duet 2 Ethernet and SBC
-
@wilriker is it a different DuetIAP as the normal build which is released on GitHub?
-
-
@wilriker did you see anything like https://forum.duet3d.com/post/162547 in your testing?
(that is with 330R inline on the MOSI, MISO and SCK signals, but the ESP is in place with its pins as hi-z and sleeping).
i'll see if I can't put some 2.0mm headers on there so I can switch between WiFi and SBC but will take a while
-
@bearer I remember that I have seen the
6/26/2020, 11:51:59 AM Connection to Duet established 6/26/2020, 11:52:01 AM Warning: Lost connection to Duet (Board is not available (no data response))
cycle at least once but I don't remember what the reason/solution was (as there were a lot of errors at that time ). And I have only ever tested with a Duet 2 Ethernet.
Unlikely but: did you use the
GPIO0
on the ESP as the TransferReady pin? I remember that while testing I got confused that the header for Ethernet does not have all the pins that the ESP needs and thus some contact points where not what I expected in the first place. Usually if you get that wrong DSF will complain about Duet not being available, though.EDIT: I only now saw that you get a connection every once in a while (in your example to issue
M115
). That means basic connection is working. And if SPI speed would be too high that would result in checksum errors rather thanno data
errors.EDIT2: There have been a lot of refactorings lately. Let me quickly check if it still works on my test hardware.
EDIT3: That still works (although I get an error with DCS not being able to deserialize a status update but that's something different).
-
@wilriker haha! Don't worry about it too much, it was just a stab in the dark as I had someone to help me with the wiring. I'll get back to it in a couple of weeks.
Anyways yes, i did use gpio0 or EDR_CONN as the net is called, which looked to be the same pin the w5500 uses, and as M115 did manage to sneak through I presumed that was ok. And despite not seeing checksum errors I tried dropping the SPI speed but made no difference.
I just wanted to see if it was possible to not remove the ESP, so far either i messed up hi-z firmware, or it has to GTFO. Thanks for taking a look!
-
I finished my prototype
It has a 5V 3A regulator on it for the raspberry
-
@smoki3 said in Duet 2 Ethernet and SBC:
It has a 5V 3A regulator on it for the raspberry
have you considered the load on the 1A fuse for the fans when you're taking a good chunk out for the 5v buck?
-
@bearer said in Duet 2 Ethernet and SBC:
I just wanted to see if it was possible to not remove the ESP, so far either i messed up hi-z firmware, or it has to GTFO. Thanks for taking a look!
If the firmware sets up the ESP reset pin and EN pins as outputs in the low state, then I think it should work without disconnecting the ESP. The additional capacitance of the ESP pins might reduce the maximum available SPI speed a little, but that speed isn't critical.
-
@dc42 said in Duet 2 Ethernet and SBC:
If the firmware sets up the ESP reset pin and EN pins as outputs in the low state
I feel like I'm missing something obvious here; will have a think or two and make a new topic when I've figured it out, or figured out that I'm not gonna figure it out
edit: nope, doesn't compute.as suspected, were missing something obvious .. -
@bearer said in Duet 2 Ethernet and SBC:
@smoki3 said in Duet 2 Ethernet and SBC:
It has a 5V 3A regulator on it for the raspberry
have you considered the load on the 1A fuse for the fans when you're taking a good chunk out for the 5v buck?
Yes you are right. I thought the always on Fan are directly connected to VIN
-
@smoki3 said in Duet 2 Ethernet and SBC:
@bearer said in Duet 2 Ethernet and SBC:
@smoki3 said in Duet 2 Ethernet and SBC:
It has a 5V 3A regulator on it for the raspberry
have you considered the load on the 1A fuse for the fans when you're taking a good chunk out for the 5v buck?
Now you are right. I thought the always on Fan are directly connected to VIN
might not be a problem, you should have 3-400mA left for fans driven by Vin, I was just trying to make sure you'd take it into account.
edit: I've used some of these type of things to tap the fuse for putting on a step down for fans (mini - not low profile, ATM or ATP fuse)
https://www.ebay.com/sch/i.html?_nkw=atp+fuse+tap -
../src/Libraries/Fatfs/diskio.c:51:10: fatal error: ctrl_access.h: No such file or directory 51 | #include "ctrl_access.h" | ^~~~~~~~~~~~~~~ compilation terminated. make: *** [src/Libraries/Fatfs/diskio.o] Error 1 make: *** Waiting for unfinished jobs....
I get this when I try to build DuetIAP. Building in mac.
-
@smoki3 said in Duet 2 Ethernet and SBC:
ctrl_access.h: No such file or directory
i got the same, but as long as you can use Bossa to do any programming after the inital flashing you don't need the IAP binary
-
So tested my PCB today. Its working fine. So I just miss the IAP that I can flash the duet trough DWC.
-
With SBC there is no SD card needed in the duet right?
-
@smoki3 said in Duet 2 Ethernet and SBC:
With SBC there is no SD card needed in the duet right?
it explicitly needs to not have a SD card with a config.g on it. (at least for now (RRF3.2), been some discussion on changing that)
-
@bearer said in Duet 2 Ethernet and SBC:
@smoki3 said in Duet 2 Ethernet and SBC:
With SBC there is no SD card needed in the duet right?
it explicitly needs to not have a SD card with a config.g on it.
I got it I removed the SD Card now my config is working
-
@wilriker said in Duet 2 Ethernet and SBC:
@Dougal1957 DSF is absolutely the same. It does neither know nor care if it's a D3 or a D2 on the other end.
not 100% accurate .. if one were to suffer from pendanticitis(?) .. upon first connection it says "Welcome to your new Duet 3" .
...good thing i don't
-
@bearer Have you found a solution building DuetIAP?
maybe @wilriker can help us?
-
@smoki3 said in Duet 2 Ethernet and SBC:
@bearer Have you found a solution building DuetIAP?
sort of; wait for 3.2 release candidates as I don't really need it.
I just send
M997 P"ERASE"
M999 P"ERASE"
and upload firmware with bossac from the pi.