Possible to add unique ID to 1LC or modify Name

[dc42]

@marcossf if you run M409 K"boards" does it show the board unique IDs? I'm away from the office right now so I can't check.

[T3P3Tony]

@quentinle thanks for confirming this. I have moved this to the firmware wishlist.

[dc42]

@marcossf currently the only way you can find the unique ID of expansion boards is to send M122 B# P1 where # is the CAN address of the board.

The bootloader version will show as "not available" in the M122 report if the bootloader is an old version.

[Marcossf]

@dc42 Ok, found it out.

M409 K"board" in this case M409 K40 on a 1XD boards gives this output:

M409 K40
{
    "key": "",
    "flags": "",
    "result": {
        "boards": [
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {}
        ],
        "directories": {},
        "fans": [],
        "global": {},
        "heat": {},
        "inputs": [
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {}
        ],
        "job": {},
        "limits": {},
        "move": {},
        "network": {},
        "sensors": {},
        "seqs": {},
        "spindles": [
            {},
            {}
        ],
        "state": {},
        "tools": [
            {},
            {},
            {}
        ],
        "volumes": [
            {}
        ]
    }
}

Same with a 1LC:

M409 K20
{
    "key": "",
    "flags": "",
    "result": {
        "boards": [
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {}
        ],
        "directories": {},
        "fans": [],
        "global": {},
        "heat": {},
        "inputs": [
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {},
            {}
        ],
        "job": {},
        "limits": {},
        "move": {},
        "network": {},
        "sensors": {},
        "seqs": {},
        "spindles": [
            {},
            {}
        ],
        "state": {},
        "tools": [
            {},
            {},
            {}
        ],
        "volumes": [
            {}
        ]
    }
}

If query with a M122 B40 P1 it shows the GUID right:

1XD:

m122 b40 p1
MCU temperature reading OK (25.8C)
VIN voltage reading OK (24.4V)
All checks passed
Board ID: SF2PJ-GDA7A-N25J0-40KM4-LNS2Z-76T99

1LC:

	m122 b20 p1
MCU temperature reading OK (34.6C)
VIN voltage reading OK (23.8V)
Driver status OK
All checks passed
Board ID: 4DXBX-8KANL-M25J0-401GQ-1V40Z-RKLP5

Updating a toolboard to new version, also updates their bootloader, isn't it?

Thanks David

[jay_s_uk]

@marcossf the bootloader update is a separate command.
e.g. M997 B40 S3

[Marcossf]

@jay_s_uk Ok, thank you!

[QuentinLe]

@dc42 said in Possible to add unique ID to 1LC or modify Name:

M122 B# P1

Thanks for your reply => M122 B# P1 working like a charm in my case

[dc42]

@marcossf it's M409 K"boards" (plural) to get the complete board info. However I have checked and the unique ID is not included. I have added a work item to add the unique ID to the object model.

[Marcossf]

@dc42 Ok, undestood. Thanks David.

[dc42]

@marcossf this is now implemented and will be in the next 3.4 beta release.