stepper motor skip stepping control

More
8 years 1 month ago #116971 by alex123
I overlooked, corrected, worked.
Now so:
Code:
# ---closedloop stepper signals--- net z-pos-cmd <= axis.2.motor-pos-cmd net z-vel-cmd <= axis.2.joint-vel-cmd net z-output => hm2_7i92.0.stepgen.00.velocity-cmd # !!!!!!!!!!!так было до правки #net z-pos-fb <= hm2_7i92.0.stepgen.00.position-fb #net z-pos-fb => axis.2.motor-pos-fb # !!!!!!!!!!правка чтобы просто контролтровало перемещение по энкодеру и правило шаги мотора # !!!!!!!!!!к последующему пункту добавил <= pid.z.feedback работает то-же по внешнему разница не заметна!!!! #net z-pos-fb <= hm2_7i92.0.encoder.00.position <= pid.z.feedback #net z-pos-fb => axis.2.motor-pos-fb # !!!!!!!!!!правка чтобы просто контролтровало перемещение по энкодеру это работает но с полноценной обр связью по положению!!!!! # !!!!!!!!!!шаговик управляется по положению энкодера или линейки!!!!! net z-pos-fb <= hm2_7i92.0.encoder.00.position net z-pos-fb => axis.2.motor-pos-fb net z-enable <= axis.2.amp-enable-out net z-enable => hm2_7i92.0.stepgen.00.enable
BUT it gives full feedback on the encoder / ruler to the stepper motor.
In the current application, it is necessary that linux generates steps from the specified speed and distance, and the encoder stands on the motor shaft and counts the steps, if there is a discrepancy greater than allowed, it is necessary not to add steps to the motor and stop the machine (in other words, the encoder detects an emergency machine prevents shchagovy motor).
Work on the principle of the torque limiter in a screwdriver.

Please Log in or Create an account to join the conversation.

More
8 years 1 month ago - 8 years 1 month ago #116972 by PCW
That should be automatic with encoder feedback.
The following error limits in the ini file determine the allowable difference
between step motor position (step count/scale) and encoder feedback position
Last edit: 8 years 1 month ago by PCW.

Please Log in or Create an account to join the conversation.

More
8 years 1 month ago #116976 by alex123
In Mach3 feedback is not possible but there is a DRO for the encoder / line, I periodically compare the distance and the DRO when exceeding the specified mismatch - the program is paused. I'm not such an expert linux to do this in it.
1)How to implement this in linux?
2)7i92 has firmware 7i92_5ABOB_Enc but it's not in the configurator, Now I'm testing on the firmware 7i92_7i76x1D. How to transfer these settings to the firmware 7i92_5ABOB_Enc in it there are 5 encoders 3 of which I need to use?

Please Log in or Create an account to join the conversation.

More
8 years 1 month ago - 8 years 1 month ago #116978 by PCW
As I mentioned, LinuxCNC will automatically fault if the following error (difference between commanded and actual positions) exceeds the following error limits specified in the INI file. If faulting and aborting the program is OK, this is already the built in behaviour of your current setup. If you want to pause the program rather than fault and abort, then you will have to set this up in the hal file using the "near" component and some logic.

To use the 5ABOB_enc config I would just clone (copy/paste) your working axis hal file entries and change the encoder, stepgen, and PID numbers/names as desired
Last edit: 8 years 1 month ago by PCW.

Please Log in or Create an account to join the conversation.

More
8 years 1 month ago #116979 by alex123
But as it is now, it forces you to work with a large resolution encoder and precision (for a screw with a 10mm pitch, which is difficult for some reasons.) If you do not allow the program to DRO an axis along the DRO, with low resolution and encoder accuracy (100-300 marks) control whether there is a local stall motor stall from the emergency overload of the machine.

"To use the 5ABOB_enc config I would just clone (copy/paste) your working axis hal file entries and change the encoder, stepgen, and PID numbers/names as desired "
So I would, and where to get the hal and ini for this firmware 5ABOB_enc in which to insert, because there is nothing to generate

Please Log in or Create an account to join the conversation.

More
8 years 1 month ago #116981 by PCW
Yes if you are using the encoder for control feedback you will need a relatively high resolution encoder, but you can use a low resolution encoder in conjunction with the "near" component to verify tracking but this will require a more complex hal file

I would suggest reading a bit about hal files and components

You dont need a specific 5Abob hal file, _any_ mesa step/dir hal file will work as a starting point for hand editing

Please Log in or Create an account to join the conversation.

Time to create page: 0.071 seconds
Powered by Kunena Forum