Duet 3 expansion 3HC v1.0 No Can Connection

[DanielPetrea]

I'm trying to connect duet3 expansion 3hc 1.0 with Duet 3 Mainboard 6hc v1.0.
I have connected the power and the straight rj11 to the expansion board.I setted also the board address to 1.
I have compiled the following package:

• CANlib
• CoreNG
• Duet3Expansion
• DuetWifiSocketServer
• FreeRTOS
• RepRapFirmware 3 v1.0
• RRFLibraries

And i have the binaries for the mainboard and the expansion. I have put it on the sd card and i tried to update the expansion board using M997 B1 command but give me this error:
"Error: M997 Response timeout: Can addr 1 , req type 6024, RID=15"
I noticed also that the expansion diag led is not blinking.
I don't understand how to get working this board.
Thanks.

[dc42]

@DanielPetrea said in Duet 3 expansion 3HC v1.0 No Can Connection:

I noticed also that the expansion diag led is not blinking.

Are the blue, red and green power LEDs on the expansion board lit?

If you disconnect the board from CAN and set the address to zero (all switches off), does the DIAG LED flash at all?

[DanielPetrea]

I have 4 leds that are working(blue,orange,red and green).
I tried to set the address to zero and now the diag led is blinking. I reconnected the can bus and set the address to 1 but give me the same error "Error: M997 Response timeout: Can addr 1 , req type 6024, RID=15". The diag led blinks for 5 times than stops for 5 seconds and than blinks again

[dc42]

You may need to update the firmware on the expansion board. Make sure you are running firmware 3.1.1 on the main board first. Then download expansion firmware 3.1.0 which is included in the 3.1.1 firmware release. Set the address switches to 0 and the expansion board will download new firmware. if that succeeds and the diag LED blinks steadily, you should be able to communicate with the board at address 126.

[DanielPetrea]

I upload the firmware 3.1.1 to mainboard.
I have download the expansion firmware 3.1.0 and complied it , than i copied the binary to mainboard sd card. I setted the address switches to 0 and reset the mainboard. But the expansion diag led blinks for 5 times than stops for 5 seconds and than blinks again.

I have tried also che M122 gcode.

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode)
Board ID: 08DJM-956L2-G43S4-6J9DG-3SJ6L-KB6GG
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 162664 of which 60 recycled
Exception stack ram used: 280
Never used ram: 75608
Tasks: NETWORK(ready,348) ETHERNET(blocked,444) HEAT(blocked,1200) CanReceiv(suspended,2756) CanSender(suspended,1488) CanClock(blocked,1432) TMC(blocked,212) MAIN(running,4536) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 00:03:38 ago, cause: power up
Last software reset at 2020-07-31 12:22, reason: Stack overflow, spinning module none, available RAM 75124 bytes (slot 2)
Software reset code 0x4111 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f80e BFAR 0x00000000 SP 0x2045ffb4 Task NETW
Stack: 204120c0 204120f4 00463615 20417e30 20412228 0000000a 00000000 00000000 00462499 20412104 20417e30
Error status: 0
MCU temperature: min 36.8, current 40.9, max 41.2
Supply voltage: min 23.4, current 23.5, max 23.6, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Driver 0: standstill, reads 34522, writes 14 timeouts 0, SG min/max 0/0
Driver 1: standstill, reads 34523, writes 14 timeouts 0, SG min/max 0/0
Driver 2: standstill, reads 34523, writes 14 timeouts 0, SG min/max 0/0
Driver 3: standstill, reads 34527, writes 11 timeouts 0, SG min/max 0/0
Driver 4: standstill, reads 34524, writes 14 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 34525, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2020-07-31 14:57:55
Slowest loop: 1050.93ms; fastest: 0.21ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 1.6ms, 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 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
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: 14.37ms; fastest: 0.03ms
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: 1 of 8

• Ethernet -
  State: active
  Error counts: 1 0 0 0 0
  Socket states: 5 2 2 2 2 0 0 0
  === CAN ===
  Messages sent 4904, longest wait 0ms for type 0
  === Linux interface ===
  State: 0, failed transfers: 0
  Last transfer: 218908ms ago
  RX/TX seq numbers: 0/1
  SPI underruns 0, overruns 0
  Number of disconnects: 0
  Buffer RX/TX: 0/0-0

[dc42]

These are the error codes reported by the bootloader:

// Error codes, presented as a number of flashes of the DIAG LED
enum class ErrorCode : unsigned int
{
	invalidFirmware = 2,
	badCRC = 3,
	blockReceiveTimeout = 4,
	noFile = 5,
	badOffset = 6,
	hostOther = 7,
	noBuffer = 8,
	flashInitFailed = 9,
	unlockFailed = 10,
	eraseFailed = 11,
	writeFailed = 12,
	lockFailed = 13
};

So 5 flashes means that the main board firmware reported that the requested file was not present in /sys on the SD card. The filename should be Duet3Firmware_TOOL1LC.bin. There may also be a message in DWC from RRF on the main board warning you that it received a request for a missing file.

You can find the file here https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.0/Duet3Firmware_TOOL1LC.bin. It's also included in the .zip file of the 3.1.1 release.

[DanielPetrea]

@dc42 Thanks. I renamed the binary file and now it work. Thanks you for the support.