Struggling to connect to new board

Asdasd1234

I cant run M558 until I can connect to the board though? or do you mean just put it in the config?
Will try YAT now though

TKWARD

Once you get YAT connected you can run the M588 S"*" first.

Then follow the getting connected guide.

A Former User

@Asdasd1234 said in Struggling to connect to new board:

Will try YAT now though

which operating system are you using? and you are using the duet3 6hc as stand-alone with the SD card in the duet3 and not with a raspberry pi?

A Former User

@TKWARD said in Struggling to connect to new board:

Also, before following that guide run M588 S"*" to delete any saved networks ....... it will save confusion later on.

only relevant to duet2wifi so no need with the duet3

TKWARD

Another thought .... your WiFI network ... Does it allocate DHCP addresses ? or expect static IP addresses ?

If DHCP... then use the M550 machine name command, and let it auto allocate the IP address ( don't try to specify one ).

You can then ping it in command prompt with : ping machine name.

TKWARD

@bearer Missed that bit ..... DOH!!

Asdasd1234

Using windows 10,
Running standalone,
the router allocates DHCP that this is plugged into (ethernet, not wifi)

I've got YAT setup now, but it seems that something else immediately connects to the board and takes up the com slot since I get this as soon as its plugged in (in use by another application)
https://i.imgur.com/f2cTmCP.png

I'm going to restart the pc and see if that changes

EDIT: Restarting pc freed up the com port. M115 returns the firmware, so some progress at last!

EDIT2: M552 returns ethernet is disabled... I'm guessing I have something missing in my config then ?

A Former User

Maybe confirm the Duet can read the SD card?

What do you get if you run M20 P"/" in the terminal?

droftarts

@Asdasd1234 Here's your config.g

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Mar 01 2020 11:41:32 GMT+0000 (Greenwich Mean Time)

; General preferences
G90                              ; send absolute coordinates...
M83                              ; ...but relative extruder moves
M550 P"DuetCNC"                  ; set printer name

; Network
M552 P0.0.0.0 S1            ; enable network and set IP address
M553 P255.255.255.0              ; set netmask
M554 P192.168.1.11               ; set gateway
M586 P0 S1                       ; enable HTTP
M586 P1 S0                       ; disable FTP
M586 P2 S0                       ; disable Telnet

; Drives
M569 P0.0 S1                     ; physical drive 0.0 goes forwards
M569 P0.1 S1                     ; physical drive 0.1 goes forwards
M569 P0.2 S1                     ; physical drive 0.2 goes forwards
M584 X0.0 Y0.1 Z0.2              ; set drive mapping
M350 X8 Y8 Z8 I1                 ; configure microstepping with interpolation
M92 X800.00 Y800.00 Z1600.00     ; set steps per mm
M566 X900.00 Y900.00 Z12.00      ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00   ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00      ; set accelerations (mm/s^2)
M906 X2500 Y2500 Z2500           ; set motor currents (mA)
M84 S0                           ; Disable motor idle current reduction

; Axis Limits
M208 X0 Y0 Z0 S1                 ; set axis minima
M208 X430 Y360 Z100 S0           ; set axis maxima

; Endstops
M574 X1 S0 P"!io1.in"            ; configure active-low endstop for low end on X via pin !io1.in
M574 Y1 S0 P"!io2.in"            ; configure active-low endstop for low end on Y via pin !io2.in
M574 Z2 S0 P"!io3.in"            ; configure active-low endstop for high end on Z via pin !io3.in

; Z-Probe
M558 P0 H5 F120 T1200            ; disable Z probe but set dive height, probe speed and travel speed
M557 X15:215 Y15:195 S20         ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"pt1000" R2200 ; configure sensor 0 as PT1000 on pin temp0
M950 H0 C"out0" T0               ; create bed heater output on out0 and map it to sensor 0
M143 H0 S120                     ; set temperature limit for heater 0 to 120C
M307 H0 B1 S1.00                 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0                          ; map heated bed to heater 0

; Fans

; Tools
M563 P0 D0 H1 F0                 ; define tool 0
G10 P0 X0 Y0 Z0                  ; set tool 0 axis offsets
G10 P0 R0 S0                     ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

; Miscellaneous
M501                             ; load saved parameters from non-volatile memory

I can 't see anything obviously amiss.

Ian

droftarts

@Asdasd1234 Send M122 and post the response.

Ian

Asdasd1234

I think @bearer might have hit the nail on the head.
runing m20 P"/" returns :

Begin file list
NONE
End file list
ok

m122 returns the following

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 version 3.0beta12 running on Duet 3 MB6HC
Board ID: 08DJM-956L2-G43S4-6J1F2-3SJ6N-1A62G
Used output buffers: 1 of 32 (2 max)
=== RTOS ===
Static ram: 122240
Dynamic ram: 171368 of which 0 recycled
Exception stack ram used: 344
Never used ram: 99264
Tasks: orm ===
Last reset 00:28:45 ago, cause: power up
Last software reset details not available
Error status: 0
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 32.6, current 37.7, max 38.2
Supply voltage: min 0.2, curre
Driver 5: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Date/time: 1970-01-01 00:00:00
Slowest loop: 0.43ms; fastest: 0.18ms
=== Move ===
Hiccups: 0, FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, 1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 1 in use
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
serial is ready with "m122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0 0, running macro
queue is idle in state(s) 0
lcd is idle in state(s) 0
spi is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.42ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
Hansfer: 1725042ms ago
RX/TX seq numbers: 0/1
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 0/0-0
ok

droftarts

@Asdasd1234 said in Struggling to connect to new board:

SD card 0 not detected, interface speed: 37.5MBytes/sec

Can you try a different SD card? See here for specification and how to format it (a Windows 'Quick Format' doesn't work): https://duet3d.dozuki.com/Wiki/SD_Card

Also, now it's on YAT, you can send M552 P0.0.0.0 S1 and get it on your network.

Ian

Asdasd1234

I don't have another sd card at hand, but I'll try reformatting that one (its the one that came with the board)
thanks

EDIT: sorry I was an idiot, I took the sd card out as per one of the troubleshooting links earlier and didn't replace it.

New output from m122 below:

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 version 3.0beta12 running on Duet 3 MB6HC
Board ID: 08DJM-956L2-G43S4-6J1F2-3SJ6N-1A62G
Used output buffers: 1 of 32 (1 max)
=== RTOS ===
Static ram: 122240
Dynamic ram: 171368 of which 0 recycled
Exception stack ram used: 280
Never used ram: 99328
Tasks: orm ===
Last reset 00:00:22 ago, cause: reset button
Last software reset details not available
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 36.1, current 37.1, max 37.1
Supply voltage: min 0.2, currets 0, SG min/max 0/0
Driver 1: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 2: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 3: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 4: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 5: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Dateis idle in state(s) 0 0, running macro
queue is idle in state(s) 0
lcd is idle in state(s) 0
spi is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.29ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8
- Ethernet -
State: 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 0, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 22301ms ago
RX/TX seq numbers: 0/1
SPI underruns 0, over

Although m20 P"/" still returns the same (nothing found) so I'll still try reformatting

A Former User

@Asdasd1234 said in Struggling to connect to new board:

so I'll still try reformatting

please ensure the card does not have multiple partitions and formatted with FAT32.
https://www.sdcard.org/downloads/formatter/

or

windows key + x -> disk management to look at the card

droftarts

@Asdasd1234 If it's the SD card that came with the Duet 3, and you didn't reformat it, it's formatted for the Raspberry Pi. This should be FAT32 too, so should work in the Duet 3. However, if you reformatted it with Windows 'Quick Format', that might explain why it's not read. Best thing to do is to format it with the official SD formatting tool: https://www.sdcard.org/downloads/formatter/index.html

Ian

Asdasd1234

That was it! When i reformatted the rpi image , I must have selected NTFS.
Re-done to fat32 and its all working as expected.
Thank you so much everyone for the help!

A Former User

Maybe dc42 could consider adding the partition type to the M122 output and/or a helpfull error message when people use these Raspberry Pi cards for stand alone use?

Asdasd1234

To be fair, I'd already realised it was an rpi image and I'd need to reformat it, I just had no idea which type it needed to be. Even a sticker on the bag it comes in would be a bonus for newbies like me lol