• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login

Possible to add unique ID to 1LC or modify Name

Scheduled Pinned Locked Moved
Firmware wishlist
6
16
658
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • undefined
    QuentinLe
    last edited by 29 Sept 2021, 09:50

    Hello,

    I needs to attribute a unique id to my 1LC board but i don't find anything about this. I have searched on gcode list and on reprap firmware and i saw nothing about this.
    But i can see that field exist on ObjectModel => Board.
    I would like to know if you have any solutions to set this variable and if is not it's possible did you have a solution to change an other variable like Name or ShortName.

    Thanks by advanced.

    undefined 1 Reply Last reply 29 Sept 2021, 15:47 Reply Quote 0
    • undefined
      droftarts administrators @QuentinLe
      last edited by 29 Sept 2021, 15:47

      @quentinle do you mean change the CAN address? That’s how each expansion board is addressed, not by name. See https://duet3d.dozuki.com/Wiki/Duet_3_Tool_Board#Section_Set_the_CAN_address

      Ian

      Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

      1 Reply Last reply Reply Quote 0
      • undefined
        QuentinLe
        last edited by 30 Sept 2021, 07:58

        @droftarts

        Hello droftarts thanks for you reply.
        I already know for the can adresse but it not working on my case. I have multiple machines with different main board and I would like to recognise tool between machine so I need unique variable and store in the 1LC like the unique id on the 6HC.
        I don't Know if it's possible but I can see the field uniqueID on board so I think so.

        Quentin

        undefined 1 Reply Last reply 30 Sept 2021, 08:07 Reply Quote 0
        • undefined
          T3P3Tony administrators @QuentinLe
          last edited by 30 Sept 2021, 08:07

          @quentinle there is a unique GUID on the toolboard 1LC (similar to the ID on the mainboards Board ID: 08DJM-956BA-09876-XYZUV-ABCDE-12345 ) so it could be reported by M122/the Object model. I take it you have looked for it and its not there? I am not by a printer right now to check. If not then this should be a feature request to report it.

          www.duet3d.com

          undefined 1 Reply Last reply 30 Sept 2021, 10:21 Reply Quote 0
          • undefined
            QuentinLe @T3P3Tony
            last edited by 30 Sept 2021, 10:21

            @t3p3tony
            It is good to know that there is an unique ID in the board. You can find below the M122 B20 console answer:

            Diagnostics for board 20:
            Duet TOOL1LC firmware version 3.3 (2021-06-15 16:12:58)
            Bootloader ID: not available
            Never used RAM 3604, free system stack 2762 words
            Tasks: Move(notifyWait,1.3%,147) HEAT(delaying,124.7%,107) CanAsync(notifyWait,0.0%,61) CanRecv(notifyWait,16.0%,76) CanClock(notifyWait,12.8%,65) TMC(delaying,1943.7%,57) MAIN(running,3696.1%,352) IDLE(ready,0.0%,41) AIN(delaying,3334.0%,142), total 9128.6%
            Last reset 23:53:46 ago, cause: power up
            Last software reset data not available
            Driver 0: position 0, 335.4 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 21464, writes 11, timeouts 0, DMA errors 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 -2/4, peak Rx sync delay 219, resyncs 0/0, no step interrupt scheduled
            VIN: 24.2V
            MCU temperature: min 37.2C, current 54.4C, max 55.9C
            Ticks since heat task active 213, ADC conversions started 85682667, completed 85682666, timed out 0, errs 0
            Last sensors broadcast 0x00000001 found 1 218 ticks ago, loop time 0
            CAN messages queued 1032430, send timeouts 0, received 1118443, lost 0, free buffers 37, min 37, error reg 100000
            dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
            Accelerometer detected: no
            I2C bus errors 4619, naks 4619, other errors 4619

            So, on the 3.3 version, the unique ID is not reported.

            The field "uniqueId" in the object model (under boards) returns "null", so nothing there either apparently.

            In case it is an important information, I am running on SBC mode.

            undefined undefined 2 Replies Last reply 30 Sept 2021, 10:40 Reply Quote 2
            • undefined
              Marcossf @QuentinLe
              last edited by 30 Sept 2021, 10:40

              Same here, our several 1XD and 1LC didn't show the Bootloader ID. We identify the board by their Can ID adjusting the settings according that CAN number, but having a GUID could be advantageous to have same tool Can ID but some different settings or attibutes.

              undefined 2 Replies Last reply 30 Sept 2021, 11:03 Reply Quote 0
              • undefined
                dc42 administrators @Marcossf
                last edited by dc42 30 Sept 2021, 11:03

                @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.

                Duet WiFi hardware designer and firmware engineer
                Please do not ask me for Duet support via PM or email, use the forum
                http://www.escher3d.com, https://miscsolutions.wordpress.com

                1 Reply Last reply Reply Quote 0
                • undefined
                  T3P3Tony administrators @QuentinLe
                  last edited by 30 Sept 2021, 11:11

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

                  www.duet3d.com

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    dc42 administrators @Marcossf
                    last edited by dc42 30 Sept 2021, 16:28

                    @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.

                    Duet WiFi hardware designer and firmware engineer
                    Please do not ask me for Duet support via PM or email, use the forum
                    http://www.escher3d.com, https://miscsolutions.wordpress.com

                    undefined undefined 2 Replies Last reply 1 Oct 2021, 10:49 Reply Quote 1
                    • undefined
                      Marcossf @dc42
                      last edited by 1 Oct 2021, 10:49

                      @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_ukundefined 1 Reply Last reply 1 Oct 2021, 10:50 Reply Quote 0
                      • jay_s_ukundefined
                        jay_s_uk @Marcossf
                        last edited by 1 Oct 2021, 10:50

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

                        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                        undefined 1 Reply Last reply 1 Oct 2021, 10:51 Reply Quote 1
                        • undefined
                          Marcossf @jay_s_uk
                          last edited by 1 Oct 2021, 10:51

                          @jay_s_uk Ok, thank you!

                          1 Reply Last reply Reply Quote 1
                          • undefined
                            QuentinLe @dc42
                            last edited by QuentinLe 10 Jan 2021, 12:13 1 Oct 2021, 12:13

                            @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

                            1 Reply Last reply Reply Quote 0
                            • undefined
                              dc42 administrators
                              last edited by 1 Oct 2021, 13:13

                              @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.

                              Duet WiFi hardware designer and firmware engineer
                              Please do not ask me for Duet support via PM or email, use the forum
                              http://www.escher3d.com, https://miscsolutions.wordpress.com

                              undefined 1 Reply Last reply 1 Oct 2021, 16:02 Reply Quote 1
                              • undefined
                                Marcossf @dc42
                                last edited by 1 Oct 2021, 16:02

                                @dc42 Ok, undestood. Thanks David.

                                1 Reply Last reply Reply Quote 0
                                • undefined
                                  dc42 administrators
                                  last edited by 4 Oct 2021, 15:38

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

                                  Duet WiFi hardware designer and firmware engineer
                                  Please do not ask me for Duet support via PM or email, use the forum
                                  http://www.escher3d.com, https://miscsolutions.wordpress.com

                                  1 Reply Last reply Reply Quote 0
                                  1 out of 16
                                  • First post
                                    1/16
                                    Last post
                                  Unless otherwise noted, all forum content is licensed under CC-BY-SA