Motor current idle factor not working over canbus?
-
@droftarts yup, running in SBC mode. Is our current running hypothesis that this could be an SBC-related issue? If so, would you like me to test without SBC mode on my end?
-
@mike_b said in Motor current idle factor not working over canbus?:
Is our current running hypothesis that this could be an SBC-related issue? If so, would you like me to test without SBC mode on my end?
Please do, if you're happy to. I'm confident it's working in standalone, just need @chrishamm to check if/why it's happening in SBC mode.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
Hey @droftarts, I hope this doesn’t make me sound crazy (though I wouldn’t blame you if it does!), but I just tested it in standalone mode, and the problem is still happening. I was sitting right next to the printer, with my hand under the print plate ready to catch it as soon as the low idle motor kicked in ... thankfully, I managed to catch it in time. I repeated the test several times with the same result. Anyway, I really don’t know what to do next. At this point I'm wondering if it's a hardware issue?
-
@mike_b Can you post your config.g, and the config.g on the Mini 5+-as-expansion? There should be not M906 in the config.g of the expansion board.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
Hey @droftarts, I shared the configurations for both boards just a few days ago - you can find them here
I need to include the
M906 I90command in theconfig.gfile for the expansion board; otherwise, the motors default to the default idle current, which causes my print plate to drop. For testing purposes, I remove that line. So, when I say the issue persists, I mean the problem still occurs when the M906 command is omitted from the expansion board’sconfig.gfile. This was a workaround recommended by @dc42 himself here. Sorry, I know this is all a bit confusing, happy to jump on a quick voice call, to explain everything, if you think it could help?EDIT: fixed links
-
@mike_b said in Motor current idle factor not working over canbus?:
Hey @droftarts, I shared the configurations for both boards just a few days ago - you can find them here
Sorry, senior moment, and that I was looking on my phone, I missed them!
I need to include the
M906 I90command in theconfig.gfile for the expansion board...I understand that. I didn't have it in the expansion board config.g in my test setup, so I need to work out the differences between your setup and mine. Unfortunately I had to take my setup apart to do some 3.6.0-beta.2 testing, and I won't be able to put it back together to test until early next week.
I've had a look through your config.g, and the only thing that stands out to me is that your drives are running in stealthChop mode (M569 ... D3 Vn) while I ran mine in spreadcycle (M569 D2). You also have stallguard enabled on X and Y axes. Could you test without stallguard and with the drivers in spreadCycle? I'm not sure why this would make a difference though. Otherwise I'll try and test early next week with your config.g. I don't feel like this is a hardware issue, just yet.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
This post is deleted! -
@droftarts said in Motor current idle factor not working over canbus?:
Sorry, senior moment,
LOL, no worries, I know the feeling!
Could you test without stallguard and with the drivers in spreadCycle?
Just tried it, unfortunately no luck, problem still persists.
Otherwise I'll try and test early next week
Thank you! And please do let me know if there is anything I can do on my end to help with the debugging.
-
Hey @droftarts - just noticed this issue has been closed in github. Was this by mistake? Or has there been some resolution I'm not aware of?
-
@mike_b I was able to replicate your issue in old firmware, but not with the updated versions, so as far as we can tell it's fixed. However, it doesn't explain why it's still an issue for you. Unfortunately, I haven't had time to rebuild the test set up to test with your config.g. I will try to early next week.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts Ok, thanks! I'll repeat here what I posted on github, because I think it's important: I really don't want to come across as overly demanding - I fully appreciate how challenging it is to allocate resources in an open-source project. That said, the safety implicating of this particular issue are significant. I do have brakes on my z-stage motors but brakes clearly don't help in this situation. Although I guess you could argue a belted z-stage is a terrible idea in the first place
anyway, again, I deeply respect the effort it takes to maintain an open-source project, so please don't take this as an entitled complaint - just a genuine concern I felt was worth sharing.All that siad, I’m more than happy to take a more active role in debugging this issue, whether it involves hardware (I have multimeters, oscilloscopes, etc.) or software troubleshooting.
-
@mike_b lets see if @droftarts can replicate it with your config.g and take it from there.
