duet Wifi to Ethernet disastrous swap



  • i totally ruined my Duet Wifi trying to switch to ethernet. My fault as I accidentally overheated the wifi module area by getting distracted and ruined most of the connection points...i tried tracing some of them back but it was a mess, totally ruined. The board runs ok via the DuetDisplay and USB thou.

    DC42...the ESP8266 connector, I noticed is there, is it usable at all? regardless I ordered a new Ethernet Duet just now anyways, but the old one while in rough shape, it works perfect network aside...

    total embarrassment on my part, I solder and desolder stuff like daily and have even replaced microchips and more complex components....ugh



  • If you wanted to get some network connectivity back you could connect a raspberry pi running Octopi via USB. Then you could upload files and initiate prints with a web interface at least. You wouldn't even have to stream the prints over USB from the pi if you didn't want to. You could upload the files and then issue a print command to print from SD.



  • @phaedrux thanks I actually have it hooked up like that now to an OctoPi via USB, but it doesnt seem to take the G commands properly...some work and some dont, like M117 wont start a print or raise temps....and I do have the paramater to set look like Marlin on config.g....not sure why is this happening



  • I don't think "Look like Marlin" does what you think it does. You'll still have to use the same gcodes that work with RRF. M117 is display message. https://duet3d.dozuki.com/Wiki/GCode#Section_M117_Display_Message

    You'd need M23 and M24 to start a print. https://duet3d.dozuki.com/Wiki/GCode#Section_M23_Select_SD_file


  • administrators

    @imrj said in duet Wifi to Ethernet disastrous swap:

    DC42...the ESP8266 connector, I noticed is there, is it usable at all? regardless I ordered a new Ethernet Duet just now anyways, but the old one while in rough shape, it works perfect network aside...

    The ESP_COMMS connector that is present on older Duet revisions only connects a few of the ESP module pins: supply, ground, the UART transmit and receive pins that are used only for programming, and a few other pins that are otherwise unused by the Duet. It does not include the high speed SPI pins that are used for data transfer between the ESP module and the Duet main processor.

    I actually have it hooked up like that now to an OctoPi via USB, but it doesnt seem to take the G commands properly...some work and some dont...

    There are others using Duets with Octoprint, you can search the forum for the relevant posts. I recall making a change (in firmware version 2.01 I think) because Octoprint is very fussy about the format of the replies it receives, and I had to add an extra space in one of them so that it could parse the response.



  • @dc42 cool DC...will look around. I think @Phaedrux was correct it seems the commands between Marlin and Rep arent the same. I use S3D to write out the .gcode files and it is this software which seems to be embedding the wrong commands in the GCODE, not really Octoprint, Octoprint seems to just be issuing whatever commands are in the generated .gcode file. But yet in S3D it has the firmware selection choice one in the same for Marlin and Rep0_1547511134893_2019-01-14_19-10-47.jpg


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.