Duet Wifi - Ethernet, w genuine ethernet module.



  • Hi all,

    Aquired a duet wifi from ebay (genuine from ooznest originally) that has had it's wifi removed because that failed. Got an ethernet module from Ooznest arrived today, is it as simple as solder on the new module, adjust config, and power up?

    Thanks!



  • yeah, asuming there isn't anything wrong with the duet in the first place.

    (shouldn't actually have to adjust config, the ethernet uses the same M552 S1 command to enable networking)


  • Moderator

    @DocTrucker The ethernet module is usually plugged in to some soldered-on headers (where the WiFi chip goes) and has a couple of standoffs. Is Oozenest supplying them, too? Otherwise yes, should be straightforward, and what @bearer said!

    Ian



  • Great! Will try to sort it out this evening then. The kit has the headers and plastic stand-offs with it.

    Would have normally order direct from Duet3D, but I guess that may even inconvenience them more than using resellers!



  • @DocTrucker said in Duet Wifi - Ethernet, w genuine ethernet module.:

    The kit has the headers and plastic stand-offs with it.

    the low profile female header as well?



  • @bearer sure I saw one through the bubble wrap. Would be frustrating is one is missing! I think the ethernet module that Duet3D offer was intended for those looking to convert Duet WiFi to ethernet.


  • administrators

    Yes, it is supplied with the socket strips and standoffs. https://www.duet3d.com/DuetAddons/DuetEthernet_Module



  • All sorted now thanks. I managed to goose the firmware update, but sorted with a little bossac. Talking via ethernet / DWC now. Rewire a little more involved than a simple unplug and plug.

    Getting this setup for RRF 2.05, then will look at guides for converting the config files for RRF 3. Still got the Duet3 to set up but the target machine got diverted to running on a 0.8.5, so waiting on another machine build, which is underway slowly!


  • Moderator

    @DocTrucker said in Duet Wifi - Ethernet, w genuine ethernet module.:

    Getting this setup for RRF 2.05, then will look at guides for converting the config files for RRF 3

    Getting an example config set from the web tool to compare against is a good first step.



  • Tested all axis this morning and all fine, so just down to extendng some wires, PT100 test, fan check, tuning, then finally swap to RRF3.

    All in about £85 with some soldering. I'm happy with that! 🙂

    @Phaedrux yes thanks, that was my planned step one. I haven't used the config generators for some time so I was planning on a default set for RRF2 to compare to what I have now so I can transfer any extras that I have added to the defaults to the autogenerated RRF3 config. Should be fairly normal aside from the reasonably common twin z motors with gantry levelling. Don't anticipate much of an issue, just a bit of learning a new language! 😄



  • Running RRF 3.1 now, less fuss than I expected just an issue with the bed temp sensor and figuring out how to use a NC inductive probe on the zstop input. I suspect easy fixes, just ran out of time.

    I'll repeat the safety checks that I did on RRF1 on this system once I've established it is running well.


  • Moderator

    @DocTrucker does it report as an Duet Ethernet or WiFi in M122? Always wondered where this is set, but I expect it checks peripherals before setting one or the other.

    (I often check my peripherals before deciding one way or the other!)

    Ian



  • @droftarts that'll be the function calls;

    lift_skirt();
    what_am_i_packing();
    

    😉

    I'll check later!


  • Moderator

    @DocTrucker always declare your variables!

    Ian



  • @droftarts Touché! Think it's best I exit this skit before I get myself in trouble.

    Will report what it identifies as later.



  • @droftarts Here you are:

    Spoiler; it identifies as a Duet Ethernet.

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet Ethernet 1.02 or later
    Board ID: 08DGM-917DA-G4MS8-6JKD4-3S86M-19S7A
    Used output buffers: 3 of 24 (10 max)
    === RTOS ===
    Static ram: 27980
    Dynamic ram: 92992 of which 20 recycled
    Exception stack ram used: 192
    Never used ram: 9888
    Tasks: NETWORK(ready,384) HEAT(blocked,1304) MAIN(running,1824) IDLE(ready,80)
    Owned mutexes:
    === Platform ===
    Last reset 00:02:20 ago, cause: power up
    Last software reset time unknown, reason: Watchdog timeout, spinning module PortControl, available RAM 6392 bytes (slot 0)
    Software reset code 0x00ab HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f80f BFAR 0xe000ed38 SP 0x20004aac Task MAIN
    Stack: 0043e171 0043d44c 61000000 00000000 40568000 00000000 00000000 3e178897 3e1cd04f 41880000 3e3a3329 
    Error status: 0
    MCU temperature: min 21.3, current 27.3, max 27.5
    Supply voltage: min 24.3, current 24.4, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2020-08-29 17:22:37
    Cache data hit count 275538932
    Slowest loop: 4.14ms; fastest: 0.12ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Storage ===
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest read time 0.8ms, write time 0.0ms, max retries 0
    === Move ===
    Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
    Bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
    === AuxDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
    === GCodes ===
    Segments left: 0
    Movement lock held by null
    HTTP is idle in state(s) 0
    Telnet is idle in state(s) 0
    File is idle in state(s) 0
    USB is idle in state(s) 0
    Aux is idle in state(s) 0
    Trigger is idle in state(s) 0
    Queue is idle in state(s) 0
    Daemon is idle in state(s) 0
    Autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 4.86ms; fastest: 0.02ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
    HTTP sessions: 1 of 8
    Interface state active, link 100Mbps full duplex
    

  • Moderator

    @DocTrucker great, thanks. So it does look at the available hardware to report this. Nice.

    Ian


Log in to reply