Support for I2C during Tool Changing



  • Hi,
    I am using i2c to communicate with an arduino as an external controller. I use the M260 command to send bits to trigger the arduino controller. I also use M400 before this line as I realized i2c would not trigger somwtimes in the cgode without the M400.
    I am able to get this setup working with Tool1. But during a print where I have two tools, after I change tools from Tool2 to Tool1, the i2c command never issues. I found this happens only after tool changing.
    I have to restart the machine for i2c to be working again.

    Running Firmware 2.03 on a duet2+duex2 board setup.


  • administrators

    Please test again with 2.04RC1 - although to be honest, I don't expect any change.


  • administrators

    PS - also:

    • Are you just sending bytes using M260, or receiving them as well?
    • After selecting Tool1, if you deselect it using T-1, are you able to select it again?
    • What makes you sure that the I2C command isn't being sent, and it isn't a problem at the Arduino end?
    • What are the i2C error counts reported by M122 after selecting tool 1, and again after you try to select tool 2?


  • @dc42
    Hey, thanks for getting back, There was an M107 in the gcode file, which the slicer added and it disabled all the fan ports. one of these fan ports was powering the Arduino.


  • administrators

    @nr12 said in Support for I2C during Tool Changing:

    @dc42
    Hey, thanks for getting back, There was an M107 in the gcode file, which the slicer added and it disabled all the fan ports. one of these fan ports was powering the Arduino.

    M107 should only disable the fan assigned as the print cooling fan, which is Fan 0 unless you specify different fans in your M563 tool definition commands.


Log in to reply