No setting motor current with macro

dc42

@nriviera please confirm that you are running firmware 3.3 on both the main board and the tool board.

Do you see any error messages when running the power on macro? If you see CAN timeout messages, then it could be that your tool board is especially slow to start up. If that's the case, then upgrading its bootloader to the latest version (2.3) may help.

nriviera

@o_lampe Thanks, I didn't think of different slicer or tool profiles. I thought the config-overide but alas nothing in there to cause it.

nriviera

@dc42 I do get random CAN-bus unhandled inputs (2000, 3000, 2100 and sometimes others) so maybe that's it. I'll give it a go.

nriviera

@dc42 its been a while and the error messages never went away but I stopped having extrusion issues so I didn't pursue it. They seem to have come back intermittently this last week however. I've updated the bootloader to 2.4, running 3.4rc2 firmware. The config files are unchanged from above. Any idea?

Phaedrux

Update to 3.4 final.

https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.0

dc42

@nriviera said in No setting motor current with macro:

@dc42 I do get random CAN-bus unhandled inputs (2000, 3000, 2100 and sometimes others) so maybe that's it. I'll give it a go.

That's typically triggered by removing power to the tool board but keeping 5V power to the main board. Is that what you are doing?

nriviera

@dc42 yes. The 6HC 5v is always on as it triggers the 24v power which power the toolboards. I have a fairly large delay (I changed it to 10s but even 20s doesn't make any difference) to ensure the boards have enough time to boot but still get current issues intermittently.

nriviera

@phaedrux said in No setting motor current with macro:

Update to 3.4 final.

https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.0

I have done the update and still have the issue unfortunately.

@dc42 said in No setting motor current with macro:

@nriviera said in No setting motor current with macro:

@dc42 I do get random CAN-bus unhandled inputs (2000, 3000, 2100 and sometimes others) so maybe that's it. I'll give it a go.

That's typically triggered by removing power to the tool board but keeping 5V power to the main board. Is that what you are doing?

I'm not too fussed about the warnings and errors it's having to run a separate macro every-time I print is the annoying part. Should I use a very long delay?

dc42

@nriviera what bootloader versions are the tool boards running? To find out, use M122 B# where # is the CAN address of the tool board.

Some tool boards running older versions of the bootloader sometimes take a while to start up after power is applied.

nriviera

@dc42 weirdly the m115 output didn't have the bootloader but i updated it to the most recent last week so it should be 2.4

dc42

@nriviera it's M122 that displays the bootloader version, not M115.

nriviera

@dc42 sorry had a moment. Definitely 2.4