Advanced Search

You are really making a great job of that retrofit.

The overview section of the documentation is a good place to start.  linuxcnc.org/docs/html/gui/qtvcp.html#sec:qtvcp-overview

The way your custom .ui file is loaded when starting LinuxCNC is via this line in your .ini file:DISPLAY = qtvcp <options> <screen_name>Where <screen_name> is the base name of your ui file - in your case you saved "tester.ui" so the basename is just plain "tester".   Generally you want this ui file to be saved in the same folder as the rest of your LinuxCNC config.

You might find it valuable to install one of the QtVcp "sim" demos, which will create a working set of configuration files for a simulated machine with a QtVcp GUI.  It's much easier to experiment and see how the pieces fit together when you're starting from something that works.  You can run or set these up via the screens that you get when you first run LinuxCNC from the applications menu.

I know this isn't the step-by-step guide you were looking for, but hopefully it's some help to get you going.

 

Hi Martin, I have the same VFD and use RS485, all you need is a USB-RS485 converter.
Here is my config and hal file for the communication via MB2HAL: forum.linuxcnc.org/30-cnc-machines/42869...nc-conversion#322586
With the Modbus communication you save some cables and get important load and error information as feedback.

Just wanted to share a small update on the configuration.
I used the MB2Hal Module in order to talk to a Delata MS300 VFD.
In the pdf file I highlighted all the relevant functions/parameters for most applications.
Here is the .ini file with all the relevant parameters and the .hal that makes use out of them.
Use at your own risk/ go ahead and configure them!

These commands can be used for testing in the HalShow execution window:
#    setp mb2hal.00.command_input.int 010010
#    setp mb2hal.01.frequency_input.int 400

Hope it saves some time to someone!
Fritz