3.2.1 2nd toolbord problem...



  • Hi *,

    I had some problems with the bl-touch and a with a endstop so I thought that it could be a good idea to upgrade to 3.2.1.

    I have two toolboards (1LC) on a Mini5+. The first toolboard seams to work fine:

    m122 B121
    07/02/2021, 09:48:11	m122 B121
    Diagnostics for board 121:
    Duet TOOL1LC firmware version 3.2.1 (2021-02-03)
    Bootloader ID: SAMC21 bootloader version 2.2 (2021-01-16b1)
    Never used RAM 3580, free system stack 94 words
    HEAT 90 CanAsync 89 CanRecv 83 TMC 56 MAIN 218 AIN 64
    Last reset 00:04:57 ago, cause: power up
    Last software reset data not available
    Driver 0: position 0, 315.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 13, reads 17683, writes 13, timeouts 0, DMA errors 0
    Moves scheduled 0, completed 0, in progress 0, hiccups 0
    No step interrupt scheduled
    VIN: 24.1V
    MCU temperature: min 31.9C, current 36.9C, max 37.1C
    Ticks since heat task active 68, ADC conversions started 296401, completed 296400, timed out 0
    Last sensors broadcast 0x00000002 found 1 72 ticks ago, loop time 0
    CAN messages queued 3508, send timeouts 0, received 2577, lost 0, free buffers 36
    

    The second toolboard do not react any more:

    M122 B122
    Error: M122: Response timeout: CAN addr 122, req type 6024, RID=34
    

    The 1st one seems to work fine, at least the heater works as my index finger can tell. 😉 So I expect that at least the first toolbord has the first address and I guess that I do not have a address conflict. I changes the address of the first board to 123 and tried a reset of No. 2. And various reboots. But still nothing from that board, not from 121 or the old address 122.

    The red led is flashing constantly fast and I miss the short green flash which I see on the working board. :?

    I do not expect a problem with the can bus. Nothing has been changed or moved since the last print and at least the communication on the Can bus was working.

    Bootloader?

    Cheers, Chriss


  • administrators

    @Chriss said in 3.2.1 2nd toolbord problem...:

    The red led is flashing constantly fast and I miss the short green flash which I see on the working board. :?

    The red light flashing fast means one of these:

    1. A problem with the CAN wiring. You can check it with a multimeter.
    2. The tool board is running 3.3beta firmware and the main board is running 3.2.x firmware. But if this is the case, the tool board should still respond to some types of request, for example M115 and M122.
    3. A problem with the CAN interface on the tool board, but the tool board is otherwise working. This is unlikely compared to #1.


  • @dc42 Thanks David! I still wounder why I have that problem since 3.2.1 only. Exactly with that version to be precise here. The last view prints where fine.

    Anyway, I will double check the Can wires and the Signals.

    Cheers, Chriss



  • @dc42

    🤦 There is a mechanical problem. 😞 I turned the printer 180°, booted the Scope and started the printer and everything is OK now. 🤦 I double checked the signal with the Scope and the signal looks good to me. I think that I have to check the wireing...... sorry for the false alarm. I will but that drill on my "todo before post" list.

    I upgraded the toolboard to 3.2.1 now and it looks fine.

    Cheers, Chriss


  • administrators

    @Chriss said in 3.2.1 2nd toolbord problem...:

    @dc42 Thanks David! I still wounder why I have that problem since 3.2.1 only. Exactly with that version to be precise here. The last view prints where fine.

    Anyway, I will double check the Can wires and the Signals.

    Cheers, Chriss

    It wouldn't be the first time that a poor connection just happened to start causing trouble at the same time that a firmware upgrade was installed.

    Firmware versions 3.2 and 3.2.1 are compatible as far as CAN protocols are concerned, so if you remain convinced that the issue is connected with installing 3.2.1 then you can try downgrading the tool board firmware, or the main board firmware, or both.


Log in to reply