Advanced Search

Moved the post with the second batch of images in here.

Yes, you don't need the hal encoder comp at all and unless you have a base thread
(not practical with an Ethernet connected device), the hal component will be quite slow.

Oh dear..My poor old brain.
So, the MPG is connected to the correct pins, but the input designation I should be using is perhaps hm2_7i92.0.7i73.0.2.enc0.count to get access to the high speed values?

So take the encoder count stuff out of the hal thread and instead couple
net mpg-out ilowpass.0.in <= hm2_7i92.0.7i73.0.2.enc0.count

I doubt this is all that helpful, but I did write a custom VFD module for a Commander SK over RS485/modbus, about a dozen years ago (for LinuxCNC 2.6 .. ancient stuff).  Here is the code, in case there's any value for you:

github.com/tangentaudio/cmdrsk_vfd

I'm going to revamp that machine soon and I most likely would choose one of the methods you're thinking about rather than stick with a custom component.
 

The cheap spindle on my router has failed (frozen water cooling damage???). I have a nicer spindle and a Commander SK VFD on the shelf that I planned on using as an upgrade. I use the gs2-vfd component for my router and mill and I use PWM with a Minarik inverter to control my lathe. I prefer the serial communications for controlling and monitoring the VFD. The new spindle and Commander work up to 1000hz, the GS-2 only goes to 400hz or I would have stuck with that. I do have the "Advanced User Guide for the Commander SK" that lists all the parameter to register mappings, but I need to decide on components to replace gs2-vfd.

It appears the choices are:
1) mb2hal (standard linuxcnc component)
2) vfdmod (unsupported???)
3) classic ladder (probably overkill for what I need)
4) mesa modbus (7i92)

Question #1 Can anyone can share a working Commander SK mb2hal setup.

Question #2 Is there any advantage to using a mesa serial port over the computer rs232 port for communication with VFDs? I currently use RS232 to RJ12 cables between computer and VFDs. 



 

Looks like you are using Qtaxis?
Looks like you are modifying the screen rather then embedding a custom panel?

You would need to follow Qtvcp docs for Qtaxis modifications. I can help once you confirm what you are doing.

The instructions in the manual are what you should follow for building or modifying a configuration.

Stepconfig, is a wizard application for creating basic machine configurations. It asks you questions and you fill in the answers about your machine config, then it builds the configurations files (*.hal, *.ini ...) for you. The end result being a set of machine config files that might work for you, or be a stepping off point giving you a framework to create a more complex configuration from.

PS once you've created a config using one of the wizards, if you make manual hand modifications to the config files, do not try to make changes using the wizards. Because the wizards do not look at the existing config files for info, any previous changes to them will be lost and overwritten. (They work from other files that are not used for running Linuxcnc.)

As others have mentioned, you definitely do not want DHCP and you do
need to set a static address.

You might try this:

       auto eth0
       iface eth0 inet static
           address 10.10.10.100
           netmask 255.255.255.0

DO NOT set a gateway or nameservers

 

They do seem to work. I've spent about 3 hrs tuning these so far. I'll have a hopefully final go next week. I've got 4 1kw servos (gantry). There are enough details in the manual to do the tuning. The velocity feed forward from Linux Cnc really helps with following error to a ramp, which is what I'm testing. I wish there was a way to restart communication without restarting the drives. It is tedious using the buttons on the drives. If I get a satisfactory procedure I'll write it up.