Expansion boards not working on 3.4b7?

dc42

@theolodian OK, if you update and test in standalone mode, I hope you will be able to revert to SBC mode without the SBC automatically downgrading the firmware.

theolodian

@dc42 OK, I'll try that tomorrow.

The firmware files on the SBC are listed above.

theolodian

Is there a guide somewhere on how to upload these files to the RPi? I am getting the sense that there are different partitions for standalone vs SBC mode. Plugging the SSD into my PC seems to only giving me access to the partition for standalone mode? That would mean that I'm not trying to install the correct firmware files.

jay_s_uk

@theolodian just upload them to the systems tab in DWC

chrishamm

@theolodian The FAT partition you see when you insert the microSD card in your computer is only used in standalone mode. In SBC mode, the virtual SD card files are located in /opt/dsf/sd. That explains why your M997 B1 update sort of failed (you never updated the files in there). To overwrite them, upload them on Files -> System page as @jay_s_uk said and confirm the update prompt.

theolodian

Thanks all! Update successful. However original problem persists?

M999

M409 K"boards"

1/6/2022, 1:42:33 PM	M409 K"boards"
{
    "key": "boards",
    "flags": "",
    "result": [
        {
            "canAddress": 0,
            "firmwareDate": "2021-12-30",
            "firmwareFileName": "Duet3Firmware_MB6HC.bin",
            "firmwareName": "RepRapFirmware for Duet 3 MB6HC",
            "firmwareVersion": "3.4.0beta7+2",
            "iapFileNameSBC": "Duet3_SBCiap32_MB6HC.bin",
            "iapFileNameSD": "Duet3_SDiap32_MB6HC.bin",
            "mcuTemp": {
                "current": 31.7,
                "max": 31.9,
                "min": 30.8
            },
            "name": "Duet 3 MB6HC",
            "shortName": "MB6HC",
            "uniqueId": "08DJM-956BA-NA3TN-6J9DL-3SJ6M-9T86U",
            "v12": {
                "current": 12.1,
                "max": 12.2,
                "min": 12.1
            },
            "vIn": {
                "current": 24.4,
                "max": 24.4,
                "min": 24.4
            }
        },
        {
            "canAddress": 1,
            "firmwareDate": "",
            "firmwareFileName": "",
            "firmwareVersion": "",
            "maxMotors": 0,
            "mcuTemp": {
                "current": 27.9,
                "max": 27.9,
                "min": 24.2
            },
            "shortName": "",
            "state": "running",
            "v12": {
                "current": 12.2,
                "max": 12.2,
                "min": 12.2
            },
            "vIn": {
                "current": 24.3,
                "max": 24.3,
                "min": 24.3
            }
        },
        {
            "canAddress": 2,
            "firmwareDate": "",
            "firmwareFileName": "",
            "firmwareVersion": "",
            "maxMotors": 0,
            "mcuTemp": {
                "current": 26.2,
                "max": 26.4,
                "min": 22.9
            },
            "shortName": "",
            "state": "running",
            "v12": {
                "current": 12.1,
                "max": 12.1,
                "min": 12.1
            },
            "vIn": {
                "current": 24.3,
                "max": 24.3,
                "min": 24.2
            }
        }
    ],
    "next": 0
}

M122 B1

1/6/2022, 1:43:27 PM	m122 b1
Diagnostics for board 1:
Duet EXP3HC firmware version 3.4.0beta7+2 (2021-12-30 22:07:11)
Bootloader ID: SAME5x bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 158852, free system stack 4394 words
Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.0%,95) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,82) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.4%,99) MAIN(running,91.2%,408) IDLE(ready,0.0%,39) AIN(delaying,1.3%,263), total 100.0%
Last reset 00:04:57 ago, cause: power up
Last software reset at 2021-11-23 12:29, reason: HardFault, available RAM 158816, slot 0
Software reset code 0x0060 HFSR 0x40000000 CFSR 0x00000001 ICSR 0x00489803 BFAR 0xe000ed38 SP 0x20003360 Task MAIN Freestk 519 ok
Stack: 00000000 00000000 20001060 00000000 00000000 000265f3 ffe1d614 61000000 4344ec4f fffc0000 ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
Driver 0: pos 0, 320.0 steps/mm,standstill, SG min n/a, mspos 8, reads 9440, writes 0 timeouts 0, steps req 0 done 0
Driver 1: pos 0, 320.0 steps/mm,standstill, SG min n/a, mspos 8, reads 9440, writes 0 timeouts 0, steps req 0 done 0
Driver 2: pos 0, 320.0 steps/mm,standstill, SG min n/a, mspos 8, reads 9440, writes 0 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -9/2, peak Rx sync delay 179, resyncs 0/1, no step interrupt scheduled
VIN voltage: min 24.3, current 24.3, max 24.3
V12 voltage: min 12.2, current 12.2, max 12.2
MCU temperature: min 24.2C, current 28.3C, max 28.3C
Last sensors broadcast 0x00000000 found 0 211 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 1694, send timeouts 0, received 1046, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

theolodian

This post is deleted!

theolodian

@dc42 Works fine in standalone mode.

M409 K"boards"

1/7/2022, 9:34:52 AM	m409 K"boards"
{
    "key": "boards",
    "flags": "",
    "result": [
        {
            "canAddress": 0,
            "firmwareDate": "2021-12-30",
            "firmwareFileName": "Duet3Firmware_MB6HC.bin",
            "firmwareName": "RepRapFirmware for Duet 3 MB6HC",
            "firmwareVersion": "3.4.0beta7+2",
            "iapFileNameSBC": "Duet3_SBCiap32_MB6HC.bin",
            "iapFileNameSD": "Duet3_SDiap32_MB6HC.bin",
            "mcuTemp": {
                "current": 34.6,
                "max": 34.8,
                "min": 32.6
            },
            "name": "Duet 3 MB6HC",
            "shortName": "MB6HC",
            "uniqueId": "08DJM-956BA-NA3TN-6J9DL-3SJ6M-9T86U",
            "v12": {
                "current": 12.1,
                "max": 12.2,
                "min": 12.1
            },
            "vIn": {
                "current": 24.3,
                "max": 24.4,
                "min": 23.9
            }
        },
        {
            "canAddress": 1,
            "firmwareDate": "2021-12-30 22:07",
            "firmwareFileName": "Duet3Firmware_EXP3HC.bin",
            "firmwareVersion": "3.4.0beta7+2",
            "maxMotors": 3,
            "mcuTemp": {
                "current": 28.3,
                "max": 28.3,
                "min": 25.6
            },
            "shortName": "EXP3HC",
            "state": "running",
            "uniqueId": "6Q9PQ-0D6P9-F65J0-401FJ-NWN0Z-ZH8FG",
            "v12": {
                "current": 12.2,
                "max": 12.2,
                "min": 12.2
            },
            "vIn": {
                "current": 24.1,
                "max": 24.3,
                "min": 23.8
            }
        },
        {
            "canAddress": 2,
            "firmwareDate": "2021-12-30 22:07",
            "firmwareFileName": "Duet3Firmware_EXP3HC.bin",
            "firmwareVersion": "3.4.0beta7+2",
            "maxMotors": 3,
            "mcuTemp": {
                "current": 27.1,
                "max": 27.2,
                "min": 24.9
            },
            "shortName": "EXP3HC",
            "state": "running",
            "uniqueId": "HGGW1-R5BFL-D65J0-40KKY-K6S1Z-ZHLPK",
            "v12": {
                "current": 12.1,
                "max": 12.1,
                "min": 12.1
            },
            "vIn": {
                "current": 24.1,
                "max": 24.2,
                "min": 23.7
            }
        }
    ],
    "next": 0
}

dc42

@theolodian that's interesting! Does it consistently work OK in standalone mode but not in SBC mode?

theolodian

@dc42 Yep

For one reason or another 12 axes has never worked in SBC mode. You said 3.4b6 worked for you in standalone mode.

dc42

@theolodian axes whose names are lowercase letters didn't work in SBC mode until recently, so you would have been limited to 10 axes i.e. XYZUVWABCD.

theolodian

@dc42 Yes, the lower case letters now work in SBC mode however the expansion boards do not... so we still can't do 12 axes. Latency issue, too many things in the chain?

Our main interest in the RPi is using an SSD instead of unreliable SD cards. Will the 6XD take an M2 SSD? WiFi is 2nd issue but can use an extender, will there be a WiFi 6XD?

theolodian

@dc42 12 motors moved at the same time! Standalone only still, 3.4b7+2 - haven’t tried any of the newer betas in SBC mode.

Is it easy to turn off the axes mixing? We would like the motors to run the full feed rate (or at least the axis with the most travel). The more motors move at once the slower it goes, probably trying to calculate a tool tip speed in 12 dimensional space.

dc42

@theolodian said in Expansion boards not working on 3.4b7?:

Is it easy to turn off the axes mixing? We would like the motors to run the full feed rate (or at least the axis with the most travel).

The way the F parameter is interpreted is as defined by NIST, extended to cater for more than 3 linear and 3 rotary axes, like this:

If any linear axes are moving then the F parameter gives the speed of motion along the linear axes in N-dimensional hyperspace, where N is the number of linear axes.
Else if any rotary axes are moving then the F parameter gives the composite speed of all the rotary axes in N-dimensional hyperspace, where N is the number of rotary axes.
Else the F parameter gives the total extrusion rate (the sum of all the extrusion speeds).

However, you can modify this using the M574 S parameter when you create the additional axes. See https://duet3d.dozuki.com/Wiki/M584.

theolodian

@dc42 OK, thanks. That’s a no then. Can you call for a feedrate of a million, and then let the max feedrate in config.g sort it out?

We have stacked carriages so the hyperspace dimensions aren’t relevant. However, this is not a new feature request - at least not at this time. Cheers.

dc42

@theolodian said in Expansion boards not working on 3.4b7?:

@dc42 OK, thanks. That’s a no then. Can you call for a feedrate of a million, and then let the max feedrate in config.g sort it out?

Yes.

If you have no real rotary axes then you could use the M584 S parameter to have the extra linear axes treated as rotary axes for the purposes of feed rate calculation.