-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Octopus max 5160ez no motors #29
Comments
My MPG wasnt connected yet as the steppers didnt even move. |
M122 returns "could not communicate with stepper driver" |
Update. They are detected when running Klipper. so the drivers, are fine |
I feel a little... stupid ngl. |
MPG works aswell when its connected. |
Glad you got it working in the end. I don't know if there is anything different with the driver configuration vs Klipper/Marlin? I do know that the stepper max current (from $14x parameters) gets set before enabling the drivers, as that was something I checked previously. I've got an SKR3 here with both 2209 and 5160 EZ drivers, and haven't experienced any issues with them. That said, it's only been used for development, running Nema17 motors with no load on them. |
Yea. sorry for all the notifications :D Turns out 2 were actually dead and not only one. grbl wont initialize the other ones if a dead one is connected. |
Sorry for re-opening but i think i did find an issue with how the drivers are controlled upon boot. it seems to be exactly like this: |
Hi @terjeio - the above issue has come up for a few people now, needing a delay before the Trinamic drivers are initialised or else getting a communication error. I've not been able to replicate, but perhaps dependent on rise time for the modules power supply? Anyway, do you have an opinion on adding a (configurable?) startup delay directly to the Trinamic drivers? I could add a delay to the H7 code before calling trinamic_init(), but I'd expect it might crop up in other drivers also? |
Just to check something - I've been assuming this issue only occurs on power-up, is that the case? |
@dresco correct. Only on power up |
ok, try now - I have increased the delay to 1000. |
@dresco Thanks. Let me know if you need any troubleshooting help. To rule the port out (even though it was highly unlikely as it didnt even show up in $pins), i tried using PC15 instead. No change, so my guess is that the probe=enabled gets lost somewhere |
Ah, I hadn't moved the probe definitions over to the new AUX claiming code.. I think this should do it, are you able to test with the following changes to your map file?
|
@dresco Sure, give me a few minutes and ill report back. Im at the CNC atm anywasy |
@dresco seems like it doesnt like that at all. |
im pulling a new git down now. just to verify |
i might have misinterpreted your code sample above. i thought that id need to remove the previous probe_pin and port (because of the - in front.) Compiling with the new code now. |
Yeah sorry, that diff wasn't perhaps the easiest to parse visually :) |
yep. compiles now. let me run down again to flash. |
@dresco that did the trick. Works like a charm now |
@T4KUUY4 Cool, thanks for the confirmation. Will get the changes pushed up to GitHub later.. |
@dresco Awesome Thanks. Basically, if you set the motors to not disable in idle (so they cant move), you cant jog/move anymore. Z Homing after a reset seems to work, but nothing will move after that. I dont know if thats a bug on my end or a general thing. Also, is the probe input pulled up? i seem to notice that it sometimes flickers as if it was floating for a second. Nothing gets interrupted though so it might be a visual bug. |
Not that I'm aware of, my CNC router has always been using
Seems to be, the Octopus MAX schematic shows a 10K pullup to 3.3V |
That would be awesome. let me know if you need anything tested. Thanks
Good to know. Must be a visual bug then. |
Afraid I'm not able to replicate here. My test setup is the standard SKR3 build from platformio.ini (5160, 3 axis, bootloader), with 3x steppers on X/Y/Z outputs. Reset all parameters, then |
Thanks for testing it. Then its either a buggy configured firmware on my end. Or because im using a ganged Y axis. |
What is your $4 setting (Invert stepper enable pins)? |
$4=7
Interesting, thanks. Hadn't noticed that $37 setting before.. |
@dresco @terjeio So ive did some more testing today on a different CNC project and i found that having stealthchop turned on by default in the motor_plugin tmc5160 section, made a drastic difference in terms of performance. I have some stepperonline 23he45-4204s motors here that i never managed to get over a certain speed (1300mm/min in my case). Even with nothing attached. (32 microsteps, 2A of current). It for some reason worked with some load on the X motor, but upon taking it out, it didnt again. which was very weird. I initially thought of having a dead motor so i just swapped in a replacment. issue was still present. Thats when i noticed that stealthchop, is hardcoded on. Why is that a thing? |
Hi and sorry for creating another issue.
I just cant get my head around why the motors are not working. Ive got 5160 ez on my octopus max. In the First 4 Slots.
Ive compiled on the webbuilder with ganged Y motors and EZ5160s with 0.075 sense resisor. Ive reset my grblhal settings but i still get no motor movement. I tried inverting the enable pins but no change.
stepper drivers do get warm so they are getting power.
Also, even though i havent fully confirmed yet, enabling mpg test 2 in the Firmware, makes it Crash a lot. Mostly "controller is halted" or error:20.
Any ideas?
Thanks in advance
Tom
The text was updated successfully, but these errors were encountered: