Expansion boards not working on 3.4b7?

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.