Servo Wiring and Tuning detailed How To example Mesa 7i77.

Are you tuning the old Yaskawa drives with encoder feedback from the drives to 7i77? Those should be very easy to tune, just set the P value till the motors start to vibrate then lower it a bit so there is no or very litle vibration, then add FF1 a bit. Leave everything else at 0 excpet the deadband.
That should be it, it literarly took 5 minutes to tune all 3 axis last time i used them.
Make sure you have the drive enable wired to LinuxCNC and working correctly before everything else.

andypugh wrote: I have no idea who I am talking to, or about what any more.

I feel like that all the time.....Time to retire I think.

tommylight wrote: Are you tuning the old Yaskawa drives with encoder feedback from the drives to 7i77? Those should be very easy to tune, just set the P value till the motors start to vibrate then lower it a bit so there is no or very litle vibration, then add FF1 a bit. Leave everything else at 0 excpet the deadband.
That should be it, it literarly took 5 minutes to tune all 3 axis last time i used them.
Make sure you have the drive enable wired to LinuxCNC and working correctly before everything else.

I have 7i48 for servo control, but other than that - yes, it was pretty easy to tune motor for X axis. The table is too short to safely jog it at 45m/min, while looking at PC screen... Now I have to sort out missing encoder signal from Y motor.

BTW can you share some suggestions for controlling the VFD? At least some hints about wiring and pinout on VFD control signal terminal?

viesturs.lacis wrote: BTW can you share some suggestions for controlling the VFD? At least some hints about wiring and pinout on VFD control signal terminal?

Vhat VFD? Any schematics ?

tommylight wrote: Vhat VFD? Any schematics ?

I meant that Commander VFD in Biesse machines. Nevermind, I managed to find the manual: www.acontrol.com.pl/uploads/pdf/instrukc...er-CD-user-guide.pdf

I have a question about your tutorial. And particularly about the moment, when trying to jog a motor leads to a big jump. My problem is that the first thing I tried was changing the sign of "output scale", but that does not help. Is there any other potential cause for such behavior?
One thing that makes me think that there might be some bug, is that in INI file I manually entered "max output = 6, output scale = 6". Saved the file, started LinuxCNC, opened "calibration" and there I see "output scale = 1, max output = 6". If I close LinuxCNC and open INI file in text editor, I see "max output = 6, output scale = 6".
What I did was connected pwmgen-value to a slider widget in pyvcp panel and manually set the pwmgen-value to a very low number, like 0,003. Motor movement is really slow and smooth. That means that it is all about my config. Positive pwmgen-value brings moves the motor in negative direction. And vice versa. That makes me think that "output scale" should be negative to reverse this. Encoder works correctly. Is that correct? But the motor still makes a jump, if I try to jog it.
There is only one config - there is only one folder in "configs" and there is only one INI file in that folder, so that excludes possibility that I run LinuxCNC with one config and try to edit another config. Any ideas, how to check, what am I doing wrong?

Check the hal file and make sure the right encoder is using the right PWM.
When it jumps, does it trigger a disable ?