SOLVED Board 3 not found



  • Good day,

    Not sure if I'm at the right category.

    Tonight I tried to update the firmware of my Duet 3 expansion boards.
    The messages received can be seen in the snap below:
    messages while updating.jpg image url)
    boards 1 and 2 updated correctly, however after checking the firmware on board 3, it suddenly says 3.1.0 without even having sent an update request. Another check suddenly comes back with response time-out. Updating is not possible either......

    On the interface screen of my PI, I get the message:
    Warning lost connection to Duet (timeout while waiting for transfer ready pin)

    What am I doing wrong?

    My boards are hooked up like on the picture below:
    Board set-up.jpg

    Setup:
    Duet 3, 3 expansion boards,
    board 1,2 and 3 both operate on 24 V
    Motherboard on 12 V
    Raspberry Pi for control
    Mother board 6HC: 3.1.1
    Expansion boards 1&2: 3HC 3.1.1
    Expansion board 3: 3.0 RC1



  • Usually the length and quality of wiring is negligible in a typical setup, but maybe you can elaborate a little on that just for good measure?

    But more importantly the jumpers are either wrong not clearly illustrated. Board 2 and 3 should not have jumpers behind the RJ11 plugs.

    Important! Just behind the RJ11 connectors is a 4-pin terminal block. On the last board in the CAN chain only (the one with a cable in only one of the RJ11 connectors), two jumpers must be fitted in that block to terminate the CAN bus. Jumpers must not be fitted in expansion boards that are not at the end of the CAN bus.

    https://duet3d.dozuki.com/Wiki/Duet_3_Expansion_Hardware_Overview#Section_CAN



  • @bearer
    Thank you for your reply

    Well you are right with regards to the jumper settings, however I did not find any permutation of jumper settings that did work.
    a12e1dee-6f85-49fb-8d7d-3f5c63d3c420-image.png

    as well as

    801a6302-af38-41a6-8754-241e3be90161-image.png

    gives the same problems

    Error: M115: Response timeout: CAN addr 3, req type 6024, RID=..<LF>ok<LF> on Yat
    and
    warning: lost connection to Duet (Timeout while waiting for transfer ready pin) on RPI interface.



  • @bearer I'm using 50 cm ethernet cables between the cards.

    5b86e072-cad2-457c-9476-17f0ac9025b6-image.png



  • Cables should be fine. Maybe you could wire straight from 6HC motherboard to 3HC expansion board 1 and see if it helps? (I.e. bypass board 2 and board 3, leave the jumper on board 1 in any case)

    Not sure how compatible the different versions are, but maybe its necessary to update the expansion to 3.1.1 before the 6HC motherboard. (You can either try installing the same version on the 6HC motherboard or wait and see if there are any other suggestions like addressing or faulty hardware potentially)


  • administrators

    Your second diagram looks correct to me.

    Your second diagram has the jumpers in the right place, however the board address is set to 4 not 3.

    Are you able to communicate with board 3 at all? Is the red LED on it flashing in sync with the other 3 boards?

    You can send M409 K"boards" to list the boards that have announced themselves to the main board.



  • @dc42 The led lights between the ethernet connectors are all blinking with the same pace, no difference ever since I switched them on. On board 1 and 2 it shortly stopped while updating.
    I understand what you are saying with the dipswitches, however yesterday, I updated board 1 and 2 successfully (stopping of blinking indicated transfer of firmware)
    Board 3 did not give a reaction at all. This having the dip switches in the shown positions.
    Nevertheless after your message, I changed the position of the dipswitches as indicated below.

    After changing the dipswitches, board 1 is showing version 3.1.1 and to my surprise board 2 is showing an old version 3.0. How can it be... no clue because yesterday it said differently. but let's forget it. Not important.

    I changed the dipswitches as per your message and per sketch below. Updated the expansion board firmware as I did yesterday. Next I used the M115 B0 / B1 / B2 / B3 to see the versions on the boards, the following is shown:

    M115 B0
    FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2020-05-19b2<LF>ok<LF>

    M115 B1
    Board EXP3HC firmware 3.1.0 (2020-05-15b1)<LF>ok<LF>

    M115 B2
    Board EXP3HC firmware 3.1.0 (2020-05-15b1)<LF>ok<LF>

    M115 B3
    Error: M115: Response timeout: CAN addr 3, req type 6024, RID=50<LF>ok<LF>

    M115 B4
    Error: M115: Response timeout: CAN addr 4, req type 6024, RID=51<LF>ok<LF>

    M115 B5
    Error: M115: Response timeout: CAN addr 5, req type 6024, RID=52<LF>ok<LF>

    Then I Used the M409 k"boards" as per your message. The following is returned:

    M409 K"boards"

    {"key":"boards","flags":"","result":
    [
    {
    "canAddress":0,
    "firmwareDate":"2020-05-19b2",
    "firmwareFileName":"Duet3Firmware_MB6HC.bin",
    "firmwareName":"RepRapFirmware for Duet 3 MB6HC",
    "firmwareVersion":"3.1.1",
    "iapFileNameSBC":"Duet3_SBCiap_MB6HC.bin",
    "iapFileNameSD":"Duet3_SDiap_MB6HC.bin",
    "mcuTemp":{"current":37.4,"max":37.5,"min":23.5},
    "name":"Duet 3 MB6HC",
    "shortName":"MB6HC",
    "uniqueId":"08DJM-956L2-G43S4-6J1D8-3SJ6M-9B6GG",
    "v12":{"current":11.4,"max":12.0,"min":0.1},
    "vIn":{"current":12.1,"max":12.7,"min":0.1}
    },

    {
    "canAddress":1,
    "firmwareFileName":"Duet3Firmware_EXP3HC.bin",
    "firmwareVersion":"3.1.0 (2020-05-15b1)",
    "mcuTemp":{"current":0,"max":0,"min":0},
    "shortName":"EXP3HC",
    "state":"running",
    "v12":{"current":0,"max":0,"min":0},
    "vIn":{"current":0,"max":0,"min":0}},

    {"canAddress":2,
    "firmwareFileName":"Duet3Firmware_EXP3HC.bin",
    "firmwareVersion":"3.1.0 (2020-05-15b1)",
    "mcuTemp":{"current":0,"max":0,"min":0},
    "shortName":"EXP3HC",
    "state":"running","v12":{"current":0,"max":0,"min":0},
    "vIn":{"current":0,"max":0,"min":0}},

    {"canAddress":126,
    "firmwareFileName":"Duet3Firmware_EXP3HC.bin",
    "firmwareVersion":"3.1.0 (2020-05-15b1)",
    "mcuTemp":{"current":0,"max":0,"min":0},
    "shortName":"EXP3HC",
    "state":"running",
    "v12":{"current":0,"max":0,"min":0},
    "vIn":{"current":0,"max":0,"min":0}}]
    }

    <LF>ok<LF>

    No clue what happened.

    I used the following configuration:
    d0a6b909-8067-4be7-85f7-407113b942a9-image.png



  • @ahwitmer said in Board 3 not found:

    canAddress":126

    seems to match https://duet3d.dozuki.com/Wiki/CAN_connection#Section_EXP3HC

    it'd be easier to follow if you addressed the boards with the same adress as on the labels. in any case 126 / boards 1 needs to be changed methinks.



  • Thanks for the reference! Allthough I have been reading and searching a lot, I have not seen this document before. Thanks!



  • @bearer
    As I understand the guide, the 3HC expansion boards are set via the dipswitches only. The 126 you get when all switches are off. The other type of boards are factory set to an address, which you can change by sending M952 command.
    So in my case I have chosen 1,2 and 3 as adress.

    The system does not seem to be stable, suddenly @ startup I get many errors and after that all my tools are gone and stay gone, this although the .g files are present at the duet.....
    Back to the drawing board

    5ec0d5fd-9753-4172-9ccc-38652500d215-image.png

    34b7647b-e47c-4c28-a960-8499a54de8d2-image.png M409 K"boards"

    {"key":"boards","flags":"","result":
    [
    {"canAddress":0,
    "firmwareDate":"2020-05-19b2",
    "firmwareFileName":"Duet3Firmware_MB6HC.bin",
    "firmwareName":"RepRapFirmware for Duet 3 MB6HC",
    "firmwareVersion":"3.1.1",
    "iapFileNameSBC":"Duet3_SBCiap_MB6HC.bin",
    "iapFileNameSD":"Duet3_SDiap_MB6HC.bin",
    "mcuTemp":{"current":35.8,"max":35.8,"min":31.6},
    "name":"Duet 3 MB6HC",
    "shortName":"MB6HC",
    "uniqueId":"08DJM-956L2-G43S4-6J1D8-3SJ6M-9B6GG",
    "v12":{"current":11.4,"max":11.7,"min":0.1},"vIn":{"current":12.1,"max":12.4,"min":0.1}},

    {"canAddress":1,
    "firmwareFileName":"Duet3Firmware_EXP3HC.bin",
    "firmwareVersion":"3.1.0 (2020-05-15b1)",
    "mcuTemp":{"current":0,"max":0,"min":0},
    "shortName":"EXP3HC",
    "state":"running",
    "v12":{"current":0,"max":0,"min":0},
    "vIn":{"current":0,"max":0,"min":0}},

    {"canAddress":2,"
    firmwareFileName":"Duet3Firmware_EXP3HC.bin",
    "firmwareVersion":"3.1.0 (2020-05-15b1)",
    "mcuTemp":{"current":0,"max":0,"min":0},
    "shortName":"EXP3HC",
    "state":"running",
    "v12":{"current":0,"max":0,"min":0},
    "vIn":{"current":0,"max":0,"min":0}},

    {"canAddress":3,
    "firmwareFileName":"Duet3Firmware_EXP3HC.bin",
    "firmwareVersion":"3.1.0 (2020-05-15b1)",
    "mcuTemp":{"current":0,"max":0,"min":0},
    "shortName":"EXP3HC","state":"running",
    "v12":{"current":0,"max":0,"min":0},
    "vIn":{"current":0,"max":0,"min":0}}]}

    <LF>ok<LF>



  • if you changed the address to make it clearer, you'd also need to change the config?

    the pins are references as CanAddress.PinName, so changing the address you need to change the pin references.



  • you can execute the config file to see any errors; M98 P"config.g"



  • @bearer I preferred to keep to the convention of card numbering because it is configured like that in my config file to keep the changes limited.



  • @bearer I will try that one tonight, thanks!



  • @bearer @dc42
    For some reason the system doesn't seem to be stable.
    The reponses of the system are not consistent.
    M98 P"config.g" does some times a lot and some times nothing at all
    Yesterday, I had no tools, tonight suddenly they are back

    The command M98 etc resulted in

    M98 P"config.g"
    <LF>
    RepRapFirmware for Duet 3 MB6HC Version 3.1.1 dated 2020-05-19b2 <LF>
    Ethernet is disabled. <LF>
    RepRapFirmware for Duet 3 MB6HC is up and running. <LF>
    Connection to Linux established! <LF>
    Warning: VIN under-voltage event (0.9V)Lost connection to Linux <LF>
    Connection to Linux established!<LF>Lost connection to Linux <LF>
    Warning: 12V under-voltage ok<LF>

    After that, I only get <LF>ok<LF> restarting sometimes gives the first message sometimes only the last result.

    The interface is showing at startup: Duet connected

    then after M98 P"config,g" I get on my interface:

    Error M574 pin "io1.in" is not free
    Error M574 pin "io0.in" is not free
    Warning M307: heater 0 appears to be overpowered, if left at full power its temperature is predicted to reach 365C
    the M568 command is not longer needed
    then the last two messages disapear automatically

    heater o is switched off according to the interface

    the first message I get from the M98 command, mentions vin undervoltage, could that be the cause of the inconsistent behavior?

    The RPI has its own power
    the MB runs on 12V
    the expansion boards run on 24V



  • @bearer @dc42
    Using the M409 K"boards" results in the info below.
    The thing that surprises me that the MB shows values for V12 and Vin
    The expansion boards show 0 values. Is that potentially the problem?

    M409 K"boards"
    {"key":"boards","flags":"","result":[
    {"canAddress":0,
    "firmwareDate":"2020-05-19b2",
    "firmwareFileName":"Duet3Firmware_MB6HC.bin",
    "firmwareName":"RepRapFirmware for Duet 3 MB6HC",
    "firmwareVersion":"3.1.1",
    "iapFileNameSBC":"Duet3_SBCiap_MB6HC.bin",
    "iapFileNameSD":"Duet3_SDiap_MB6HC.bin",
    "mcuTemp":{"current":36.2,"max":37.0,"min":32.3},
    "name":"Duet 3 MB6HC",
    "shortName":"MB6HC",
    "uniqueId":"08DJM-956L2-
    G43S4-6J1D8-3SJ6M-9B6GG",
    "v12":{"current":11.4,"max":11.9,"min":0.1},
    "vIn":{"current":12.1,"max":12.6,"min":0.1}},

    {"canAddress":1,
    "firmwareFileName":"Duet3Firmware_EXP3HC.bin",
    "firmwareVersion":"3.1.0 (2020-05-15b1)",
    "mcuTemp":{"current":0,"max":0,"min":0},
    "shortName":"EXP3HC","state":"running",
    "v12":{"current":0,"max":0,"min":0},
    "vIn":{"current":0,"max":0,"min":0}},

    {"canAddress":2,"firmwareFileNa
    me":"Duet3Firmware_EXP3HC.bin",
    "firmwareVersion":"3.1.0 (2020-05-15b1)",
    "mcuTemp":{"current":0,"max":0,"min":0},
    "shortName":"EXP3HC",
    "state":"running",
    "v12":{"current":0,"max":0,"min":0},
    "vIn":{"current":0,"max":0,"min":0}},

    {"canAddress":3,"
    "firmwareFileName":"Duet3Firmware_EXP3HC.bin",
    "firmwareVersion":"3.1.0 (2020-05-15b1)",
    "mcuTemp":{"current":0,"max":0,"min":0},
    "shortName":"EXP3HC",
    "state":"running",
    "v12":{"current":0,"max":0,"min":0},
    "vIn":{"current":0,"max":0,"min":0}}]}



  • (i'm out of my depth, a long time ago; maybe @Phaedrux or the other wizards can shed some light on it)

    ((d'oh, yes, please relabel diagram instead of changing addresses))


  • administrators

    Currently, it's normal for VIN and V12 to show zero for the expansion boards in M409, because the expansion boards don't report the voltages. I plan to fix this before firmware 3.2 release. Meanwhile, you can see the actual voltages using M122, for example M122 B1 to show the voltages for the board with CAN address 1.

    Feel free to set the CAN addresses 1, 2, 3 of your expansion boards any way you like, but in future please re-label the boards in your diagrams "Expansion board 1" for the board with CAN address 1, similarly for boards 2 and 3. Talking about "Expansion board 1" when that board has CAN address 2 or 3 is very confusing.

    Connection to Linux established! <LF>
    Warning: VIN under-voltage event (0.9V)Lost connection to Linux <LF>
    Connection to Linux established!<LF>Lost connection to Linux <LF>
    Warning: 12V under-voltage ok<LF>

    Those messages indicate that you have a problem with VIN power to the main board.



  • @dc42 I originally misunderstood the settings of the dip-switches. Didn't realize it was a binary setting. Thanks to remarks made by Bearer I got the place where I could find the functioning. Hence the setting of position of the dip-switches did not correspond to the board numbering. Sorry for the confusion.

    ac343fbb-120f-4538-aaaf-4897d2b1635e-image.png


  • administrators

    That looks good. Did you sort out the VIN power issue?



  • @dc42 I have not been able to reproduce the dialog at all.
    I got this result by using M98 P"config.g"
    Only answer I get back via the terminal screen is:
    ok<LF>

    On the screen I get a message M307 on heater 0 being overpowered (this is the bed), although the heater is swiched off.

    00b28477-88d8-41df-b694-dcfad9016a81-image.png


  • administrators

    @ahwitmer said in Board 3 not found:

    On the screen I get a message M307 on heater 0 being overpowered (this is the bed), although the heater is swiched off.

    That's common when you have a high-powered heater. It's warning you that you should install as thermal cut-out for safety.

    Is your current problem the 2000C reading on heater 4? What does M308 S# return, where # is the sensor number (T parameter) that you specified in the M950 H4 command?

    Please post your config.g file.



  • Sorry for the delay,

    In fact the over power warnings were given without having heated anything. Also the bed is powered via a solid state relay. For now the message does not persist anymore.

    De temperature issue of 2000C is caused by two problems but solved.
    I'm using an encapsulated thermistor. nicely fitting in the heater block.
    The contacts are not connected to the metal encapsulation, however when mounted in the heater block and fixed with the screw, one of the contacts is suddenly shortcutted with the metal housing. I ordered new ones.

    de1771e6-deb7-46fc-a6c4-825196b980df-image.png

    In itself not a huge problem be it, it was caused by an issue with my lighting.
    I'm using Cob lights which were screwed with plastic screws to the metal print head gantry. For some reason there was a metal connection between the negative pole of the lighting.

    Combination of the two issues resulted in the 2000C

    The bed thermistor issue I did not solve yet.

    Having a two year old running around, slows down progress somewhat....


  • Moderator

    @ahwitmer said in Board 3 not found:

    Having a two year old running around, slows down progress somewhat....

    Uhg, tell me about it!!



  • @Phaedrux @dc42 I think it is best to close this thread. My board is found and updated.
    I will open a new thread for other problems like homing.....


Log in to reply