- LinuxCNC
- General LinuxCNC Questions
- Why my closed loop stepper runs on grbl(Arduino) and not on linuxcnc?
Why my closed loop stepper runs on grbl(Arduino) and not on linuxcnc?
- PhilipME
- Topic Author
- Offline
- Elite Member
Less
More
- Posts: 176
- Thank you received: 13
16 Nov 2021 04:20 - 16 Nov 2021 04:24 #226621
by PhilipME
Philip
Replied by PhilipME on topic Why my closed loop stepper runs on grbl(Arduino) and not on linuxcnc?
Thanks a lotIf those steppers are working with GRBL, they will work with LinuxCNC.
First make sure the drive/motor still works OK with GRBL, if at all possible (i am sure i read somewhere wires being moved, not sure it was this topic and no time to read again), then if that works:
Sorry if I confused the issue in the other thread. The wires were OK, that is why I started new thread. The color code stated by the supplier was ok and the db9 routing is ok. The drive and the motor run perfect with grbl.
Lover the velocity
lover the acceleration (if the drives are faulting this would be the first thing to lower, when everything else is OK)
set the base period to at least 100000 while testing,
When I take the base period to 80000, and try to jog the motor, it imediatly send error and trip
I will play with acceleration . The only thing I have not done.
after everything works you can lower this to the point of LinuxCNC complaining about latency errors then go back to last value with no warnings.
step time and step space should be set in the INI file, not in hal (pretty sure they are in periods in HAL, not in nanoseconds as in INI, long time since i used this)
unless I am missing something, those settings are in the hal file not in the ini file. Only the BASE PERIOD is in the ini file.
Philip
Last edit: 16 Nov 2021 04:24 by PhilipME.
Please Log in or Create an account to join the conversation.
- PhilipME
- Topic Author
- Offline
- Elite Member
Less
More
- Posts: 176
- Thank you received: 13
16 Nov 2021 05:06 - 16 Nov 2021 09:28 #226623
by PhilipME
I did not know how to change these values in the hal file, but when I changed these values in the first page of the stepconf wizard from drive geco drive to sherline, things improved a lot. Then I reduced the acceleration and the drive/motor were runnuing very good
there is a big difference in the values of those pre-set drives
geco 540
step time 5000
step space 5000
direction hold 10000
direction setup 10000
while sherline has :
step time 22000
step space 22000
direction hold 100000
direction setup 100000
Thanks alot
Philip
Replied by PhilipME on topic Why my closed loop stepper runs on grbl(Arduino) and not on linuxcnc?
Maybe use higher steplen and step dir?
try
setp stepgen.2.steplen 10000
setp stepgen.2.stepspace 10000
I did not know how to change these values in the hal file, but when I changed these values in the first page of the stepconf wizard from drive geco drive to sherline, things improved a lot. Then I reduced the acceleration and the drive/motor were runnuing very good
there is a big difference in the values of those pre-set drives
geco 540
step time 5000
step space 5000
direction hold 10000
direction setup 10000
while sherline has :
step time 22000
step space 22000
direction hold 100000
direction setup 100000
Thanks alot
Philip
Last edit: 16 Nov 2021 09:28 by PhilipME.
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
Less
More
- Posts: 19482
- Thank you received: 6533
16 Nov 2021 11:31 #226646
by tommylight
Replied by tommylight on topic Why my closed loop stepper runs on grbl(Arduino) and not on linuxcnc?
Yup, those are the timings to change.
Some drives will work with shorter times, some will not, same with BOB, as some use very slow opto couplers.
Some drives will work with shorter times, some will not, same with BOB, as some use very slow opto couplers.
The following user(s) said Thank You: PhilipME
Please Log in or Create an account to join the conversation.
- LinuxCNC
- General LinuxCNC Questions
- Why my closed loop stepper runs on grbl(Arduino) and not on linuxcnc?
Time to create page: 0.065 seconds