cannot get 3hc to connect.

A Former User

@bam said in cannot get 3hc to connect.:

12/31/2020, 11:16:15 PM	m98 p"config.g"
12/31/2020, 11:16:03 PM	m98 p "config.g"
Error: M98: non-empty string expected
12/31/2020, 11:15:53 PM	m98 p config.g
Error: M98: non-empty string expected
12/31/2020, 11:15:42 PM	m98 p
Error: M98: non-empty string expected
12/31/2020, 11:15:37 PM	m98
Error: M98: missing parameter 'P'
12/31/2020, 11:14:50 PM	Download of config.g successful after 0s
12/31/2020, 11:14:08 PM	M98 P"config.g"
12/31/2020, 11:13:59 PM	M98 P"config.g
Error: Unterminated string
12/31/2020, 11:13:35 PM	M98 P"config.g
Error: Unterminated string

btw the first one worked (as did the 3rd from the bottom); so no syntax or other errors in the config.g file (edit: at that time)

dc42

When the system has settled down, does the red LED on the 3HC flash in sync with the red LED on the main board, half a second pff and half a second on? If it doesn't then the CAN connection is missing.

I suggest you update DSF and RRF to the 3.2RC2, or alternatively run the main board in standalone mode until you have established communication with the 3HC.

bam

@Veti that happened when I flipped the switch off

bam

@dc42 when I had the main board on 3.2 it wouldn’t talk to the DWC

bam

@dc42 4 flashes only on the 3hc

dc42

@bam said in cannot get 3hc to connect.:

@dc42 4 flashes only on the 3hc

Do you mean it flashes 4 times and then repeats, or something else?

What do you have the address switches set to?

dc42

PS - RRF 3.2 on the main board will need DSF 3.2 on the Pi to connect.

bam

@dc42 4 flashes then it stops then 4 flashes. It’s asking for firmware update. I think.

dc42

The error codes indicated by flashes are lisated at https://duet3d.dozuki.com/Wiki/CAN_connection#Section_LED_behaviour_and_error_codes. Normally you would see alternating 2 or 3 flashes (indicating no valid firmware installed followed by 4 flashes. Anyway, 4 flashes indicates that the main board didn't respond. This normally means that either the main board is not running, or the CAN connection is broken or mis-wired.

bam

@dc42 That’s probably the issue then because I am just using standard issue phone cord

bam

@Veti ; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.0 on Fri Jan 01 2021 12:00:51 GMT-0500 (Eastern Standard Time)

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

; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S0 ; physical drive 0.2 goes backwards
M569 P0.4 S1 ; physical drive 0.4 goes forwards
M569 P0.5 S1 ; physical drive 0.5 goes forwards
M569 P1.0 S1 ; physical drive 1.0 goes forwards
M569 P1.1 S1 ; physical drive 1.1 goes forwards
M584 X0.0 Y0.1 Z0.2 E0.4:0.5:1.0:1.1 ; set drive mapping
M350 X16 Y16 Z16 E16:16:16:16 I1 ; configure microstepping with interpolation
M92 X100.00 Y100.00 Z400.00 E100.00:100.00:100.00:100.00 ; set steps per mm
M566 X600.00 Y600.00 Z18.00 E300.00:300.00:300.00:300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E6000.00:6000.00:6000.00:6000.00 ; set maximum speeds (mm/min)
M201 X1500.00 Y1500.00 Z100.00 E10000.00:10000.00:10000.00:10000.00 ; set accelerations (mm/s^2)
M906 X500 Y500 Z500 E800:800:800:800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-50 Y-10 Z0 S1 ; set axis minima
M208 X300 Y300 Z350 S0 ; set axis maxima

; Endstops
M574 Z1 S3 ; configure sensorless endstop for low end on Z

; Z-Probe
M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
M557 X20:200 Y20:200 S40 ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S100 ; set temperature limit for heater 0 to 100C
M308 S1 P"1.temp0" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin 1.temp0
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S300 ; set temperature limit for heater 1 to 300C
M308 S2 P"1.temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 2 as thermistor on pin 1.temp1
M950 H2 C"out2" T2 ; create nozzle heater output on out2 and map it to sensor 2
M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H2 S300 ; set temperature limit for heater 2 to 300C

; Fans
M950 F0 C"1.out3" Q500 ; create fan 0 on pin 1.out3 and set its frequency
M106 P0 S1 H1:2 T45 ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"1.out4" Q500 ; create fan 1 on pin 1.out4 and set its frequency
M106 P1 S1 H1:2 T45 ; set fan 1 value. Thermostatic control is turned on

; 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
M575 P1 S1 B57600 ; enable support for PanelDue
T0 ; select first tool

bam

@dc42 changed the can address switches on 3hc to 1, same as the config.g file. now we have a slow flash on the mb and a fast flash on the eb

bam

@bam fast flash is no connection to mb

dc42

@bam said in cannot get 3hc to connect.:

@dc42 That’s probably the issue then because I am just using standard issue phone cord

That should be OK if it is short and wired with the middle 2 pins straight through; however it may be wired crossed.

@bam said in cannot get 3hc to connect.:

@dc42 changed the can address switches on 3hc to 1, same as the config.g file. now we have a slow flash on the mb and a fast flash on the eb

Thar suggests a problem with the CAN wiring.

bam

bam

@dc42 i just took a look and the wires are not crossed

bam

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TJ-6JTD2-3SN6K-9BAQU
Used output buffers: 1 of 40 (14 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 162320 of which 100 recycled
Exception stack ram used: 272
Never used ram: 75920
Tasks: NETWORK(ready,1968) HEAT(blocked,476) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1436) TMC(blocked,192) MAIN(running,5056) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 00:06:53 ago, cause: software
Last software reset details not available
Error status: 0
MCU temperature: min 43.7, current 44.6, max 44.8
Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0
Driver 0: standstill, reads 6854, writes 14 timeouts 0, SG min/max 0/0
Driver 1: standstill, reads 6855, writes 14 timeouts 0, SG min/max 0/0
Driver 2: standstill, reads 6855, writes 14 timeouts 0, SG min/max 0/0
Driver 3: standstill, reads 6858, writes 11 timeouts 0, SG min/max 0/0
Driver 4: standstill, reads 6856, writes 14 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 6856, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2021-01-01 23:45:44
Slowest loop: 2102.42ms; fastest: 0.14ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(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, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is ready with "M122" 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
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon* is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.81ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 0 of 8

Ethernet -
State: disabled
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 1636, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 7
Last transfer: 17ms ago
RX/TX seq numbers: 46099/13071
SPI underruns 7, overruns 7
Number of disconnects: 0
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.1.1
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 1.17
1/1/2021, 11:45:04 PM m115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2020-05-19b2

bam

@dc42 what does this mean?

M32 "0:/gcodes/Duet3Firmware_EXP3HC.bin"
Error: Unterminated string in line 3

bam

@dc42 and now this

Warning: Incompatible firmware, please upgrade as soon as possible

Veti