@jay_s_uk @Phaedrux - Thanks for taking time to reply. I followed the process using BOSSA and it seems to have worked.

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

Cheers,

Christian

@Phaedrux thanks for the suggestion. Here is what I get:

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JTD2-3S46M-9BAYS
Used output buffers: 1 of 40 (10 max)

M122 B121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.2 (2021-01-05)
Bootloader ID: SAMC21 bootloader version 2.2 (2021-01-16b1)

Here are two consecutive messages:

ISR - MB 16  OVERRUN: 0  LEN: 16  EDL: 1 EXT: 1 TS: 53390 ID: 1E007F Buffer: 2B D1 92 DB 3A 87 90 DB 0 0 0 0 0 0 0 0 
ISR - MB 16  OVERRUN: 0  LEN: 16  EDL: 1 EXT: 1 TS: 56781 ID: 1E007F Buffer: 1A 1B 95 DB 2B D1 92 DB 0 0 0 0 0 0 0 0 

I am receiving 16 bytes but as you can see, the last 8 are always zeros. Looking at the first 8 bytes, I can see the current 'timeSent' become the 'lastTimeSent' in the next message.

I am currently using the 3.2 release.

@dc42 Thanks again for your help, I have made good progress based on the information that you shared.

May I ask a follow up question?

When I receive timeSync messages (type 30) I am only seeing 64 bits, enough to unpack 'timeSent' and 'lastTimeSent'. I was expecting another 64 bits containing 'lastTimeAcknowledgeDelay' and 'realTime' but never see them. Is this expected or do I need to start investigating where the other 64 bits have gone?

Many Thanks,

Christian

Edit: oops - Corrected 64 bytes to 64 bits

Thank you, this is exactly what I needed.

Best Regards,

Christian

I have a Duet 3 connected to a Toolboard via a Tool Distribution board.

For no particular reason, I would like to understand more about the data which is exchanged between the Mainboard and the Toolboard. To this end, I have connected a Teensy 4 and am receiving CAN-FD frames.

My next task is to understand how to unpack the data based on message ID. Could anyone offer any pointers regarding the messages I should expect to see and how the data is packed?

Thanks,

Christian

@jay_s_uk @Phaedrux - Thanks for taking time to reply. I followed the process using BOSSA and it seems to have worked.

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

Cheers,

Christian

Hi All,

First time Duet user. Just powered up my Duet 3 which is connected to a RPI3B+. As instructed here I have run an update using:

sudo apt-get update
sudo apt-get upgrade

However, when I do M115 I still see old firmware:

FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.01-RC9 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2020-04-21b1

Am I missing something?

Christian