Advanced Search

ok,

lets write it in here so any newbie can see, correct me if i am wrong;

- there is a folder /usr/share/qtvcp/screens/tester that folder has the sample .ui and .py file
- and there is a folder /home/<username>/linuxcnc/configs, u have to create a folder named tester in there and put tester.ini, tester.ui and tester_handler.py files in it

if u dont put tester.ini file in that folder, u can not see tester under My Configurations during linuxcnc launch.

when u put a tester.ini file "tester" can be seen during linuxcnc launch so that u can select it and load.

but i dont have a correct .ini file so linuxcnc gives errors during launch and exits.

question:

by using linuxcnc Pncconf wizard(i am gonna use mesa card) can i create the .ini file?

so in its display section if i enter "tester" does it load the tester.ui i created in qt designer?

most probably yes am i correct?

Hi Chris,

Thanks for the Lathe GUI. I've tried to set it up using 2.10 but ran into a few issues.  I did my setup for my lathe in pncconfig selecting QTDragon as a gui.  After I've completed the setup I changed the DISPLAY setting in the .ini file to qtvcp -d qtdragon_lathe.  Is this the correct way or is there another way to setup qtdragon_lathe?  I'll elaborate on the issues if my attempt was correct. 

I've modified a manual mini lathe to cnc to test some lathe features and would gladly assist with practical issues with the development of qt_lathe.

Well, I'm not in the position to tell you what you can or cannot do but your first problem is that you have to find out what kind of fieldbus is used. 'ferrocontrol CNC fieldbus' can mean anything. It might be CANOpen or something entirely proprietary. The only one that is reasonably well supported in LinuxCNC is EtherCAT which is not what your drivers use. I think there has been somebody here who got a CAN bus working through an EtherCAT interface.
In my opinion your best option is to get new drives and motors (preferably step/dir or if you feel like it Analog or EtherCAT). The costs of this can be calculated reasonably well and integration in LinuxCNC is well supported.
Everything else is certain to involve a massive amoint of time that is quite likely to lead you nowhere.

Thank you @Hakan! Is there a place in documentation that this can be referenced? I have found a few manuals like getting started and the ones listed at: linuxcnc.org/docs/stable/pdf/ but this command did not seem to be mentioned.

Thanks again,

Steve Cap

PCW, thanks for your eyes on it. Here the lines:

hanno@cnc2:~$ halcmd show all | grep spin
10 bit OUT FALSE halui.spindle.0.brake-is-on
10 bit IN FALSE halui.spindle.0.brake-off
10 bit IN FALSE halui.spindle.0.brake-on
10 bit IN FALSE halui.spindle.0.decrease
10 bit IN FALSE halui.spindle.0.forward
10 bit IN FALSE halui.spindle.0.increase
10 bit OUT FALSE halui.spindle.0.is-on
10 bit IN TRUE halui.spindle.0.override.count-enable
10 s32 IN 0 halui.spindle.0.override.counts
10 bit IN FALSE halui.spindle.0.override.decrease <== pdnt.spindle.override.decrease
10 bit IN FALSE halui.spindle.0.override.direct-value
10 bit IN FALSE halui.spindle.0.override.increase <== pdnt.spindle.override.increase
10 bit IN FALSE halui.spindle.0.override.reset
10 float IN 0 halui.spindle.0.override.scale <== pdnt.spindle-override.scale
10 float OUT 1 halui.spindle.0.override.value ==> pdnt.spindle.override.value
10 bit IN FALSE halui.spindle.0.reverse
10 bit OUT FALSE halui.spindle.0.runs-backward
10 bit OUT TRUE halui.spindle.0.runs-forward
10 bit IN FALSE halui.spindle.0.start
10 bit IN FALSE halui.spindle.0.stop
40 bit IN FALSE hm2_7i76e.0.7i76.0.0.spindir <== spindle-cw
40 bit IN FALSE hm2_7i76e.0.7i76.0.0.spinena <== pdnt.spindle.is-on
40 float IN 0 hm2_7i76e.0.7i76.0.0.spinout <== spindle-vel-cmd-rpm-abs
60 bit IN TRUE qtpyvcp.spindle-encoder-rpm.enable
60 float IN 0 qtpyvcp.spindle-encoder-rpm.in
60 float IN 0 qtpyvcp.spindle-load-indicator.in-f
60 u32 IN 0x00000000 qtpyvcp.spindle-load-indicator.in-i
60 float IN 150 qtpyvcp.spindle-load-indicator.max-val
60 float IN 0 qtpyvcp.spindle-load-indicator.min-val
60 bit IN FALSE qtpyvcp.spindle-override.reset
33 bit IN FALSE spindle.0.amp-fault-in
33 bit IN TRUE spindle.0.at-speed <== spindle-at-speed
33 bit OUT FALSE spindle.0.brake
33 bit OUT FALSE spindle.0.forward ==> spindle-cw
33 bit I/O FALSE spindle.0.index-enable
33 bit IN FALSE spindle.0.inhibit
33 bit IN FALSE spindle.0.is-oriented
33 bit OUT FALSE spindle.0.locked
33 bit OUT FALSE spindle.0.on ==> spindle-enable
33 bit OUT FALSE spindle.0.orient
33 float OUT 0 spindle.0.orient-angle
33 s32 IN 0 spindle.0.orient-fault
33 s32 OUT 0 spindle.0.orient-mode
33 bit OUT FALSE spindle.0.reverse ==> spindle-ccw
33 float IN 0 spindle.0.revs
33 float OUT 0 spindle.0.speed-cmd-rps
33 float IN 0 spindle.0.speed-in
33 float OUT 0 spindle.0.speed-out
33 float OUT 0 spindle.0.speed-out-abs ==> spindle-vel-cmd-rpm-abs
33 float OUT 0 spindle.0.speed-out-rps ==> spindle-vel-cmd-rps
33 float OUT 0 spindle.0.speed-out-rps-abs
27 bit OUT FALSE whb.button.macro-3 ==> pdnt.reserved.for.spindle+
27 bit OUT FALSE whb.button.macro-4 ==> pdnt.reserved.for.spindle-
27 bit OUT FALSE whb.button.macro-8 ==> pdnt.reserved.for.spindle.dir
27 bit OUT FALSE whb.button.spindle-minus
27 bit OUT FALSE whb.button.spindle-plus
27 bit OUT FALSE whb.halui.spindle-override.decrease ==> pdnt.spindle.override.decrease
27 bit OUT FALSE whb.halui.spindle-override.increase ==> pdnt.spindle.override.increase
27 float OUT 0 whb.halui.spindle-override.scale ==> pdnt.spindle-override.scale
27 float IN 1 whb.halui.spindle-override.value <== pdnt.spindle.override.value
27 float IN 0 whb.halui.spindle-speed-cmd
27 bit OUT FALSE whb.halui.spindle.decrease
27 bit OUT FALSE whb.halui.spindle.forward
27 bit OUT FALSE whb.halui.spindle.increase
27 bit IN FALSE whb.halui.spindle.is-on
27 bit OUT FALSE whb.halui.spindle.reverse
27 bit OUT FALSE whb.halui.spindle.start
27 bit OUT FALSE whb.halui.spindle.stop
bit FALSE pdnt.reserved.for.spindle+
bit FALSE pdnt.reserved.for.spindle-
bit FALSE pdnt.reserved.for.spindle.dir
float 0 pdnt.spindle-override.scale
==> halui.spindle.0.override.scale
<== whb.halui.spindle-override.scale
bit FALSE pdnt.spindle.is-on
==> hm2_7i76e.0.7i76.0.0.spinena
bit FALSE pdnt.spindle.override.decrease
==> halui.spindle.0.override.decrease
<== whb.halui.spindle-override.decrease
bit FALSE pdnt.spindle.override.increase
==> halui.spindle.0.override.increase
<== whb.halui.spindle-override.increase
float 1 pdnt.spindle.override.value
<== halui.spindle.0.override.value
==> whb.halui.spindle-override.value
bit TRUE spindle-at-speed
==> spindle.0.at-speed
bit FALSE spindle-ccw
<== spindle.0.reverse
bit FALSE spindle-cw
==> hm2_7i76e.0.7i76.0.0.spindir
<== spindle.0.forward
bit FALSE spindle-enable
<== spindle.0.on
float 0 spindle-vel-cmd-rpm-abs
==> hm2_7i76e.0.7i76.0.0.spinout
<== spindle.0.speed-out-abs
float 0 spindle-vel-cmd-rps
<== spindle.0.speed-out-rps
40 bit RW TRUE hm2_7i76e.0.7i76.0.0.spindir-invert
40 bit RW FALSE hm2_7i76e.0.7i76.0.0.spinena-invert
40 float RW 24000 hm2_7i76e.0.7i76.0.0.spinout-maxlim
40 float RW 1000 hm2_7i76e.0.7i76.0.0.spinout-minlim
40 float RW 24000 hm2_7i76e.0.7i76.0.0.spinout-scalemax
hanno@cnc2:~$

 

If you can measure the temperature of your transformer, put a load, and check the temperature. As Tommy said, that's the unique concern. So, until 60°C, you are fine. Insulation can go above, but I'm not sure what would be safe for the insulation. I think I drove motors until 80°C, maybe 100°C, without damage but it's not a good idea at all, you will heat the cabinet and can hurt someone if touching it.

The sticker may be gone... It although may be printed on the side.

First of all thank u for your reply,

i loaded and checked some demos which came with linuxcnc, the thing i want to achieve is as same as qtplasmac_p_metric which is a 9:16 vertical design, its too bad that it is for a plasma, i need a cnc 4 axis mill version of it.

i know in general that .ini file declares the name of the .ui file and i dont know why but u guys make the general layout in qt and then style it with .qss file, qt is there for ui design is it not possible to create all ui with images or qt elements directly in qt? i mean is there some kind of limitation in qt for linuxcnc that u guys prefer to use coding for ui styling?

anyhow this is what i was looking for;

- create an .ini file which includes the following base code in it(a sample base code can be given) or copy one of the .ini files from demo screens,
- rename the screen name
- put it in a folder named tester under..... location together with the .ui file
- and copy tester.py from .... location .... to the same folder
- run linuxcnc and tester will appear under sample configurations/sim(i dont know if u put all in a single folder it will appear in there or not)

because if u dont say where to put and how to create all the necessary files in the document then its not a document its just general information thing.

I still dont know how to create(what to put in) .ini and where to put .ini and .ui file for linuxcnc to see them so that i can choose that ui.

Which folder is it?

and should i run any command for linuxcnc to load it at the first time?

Think about adding 2 resistors in series so that if one fails, the other one can still handle the voltage and power dissipation.
What I mean is to consider the risk that if R7 breaks into a short, you have the full DC going to the pcb. I would also suggest using "pulse-withstanding" resistors that are also flame proof, example something like this S5-47KF1 (yes expensive) but at least flame proof and "safety" SMF347KJT.

I think the differential approach is good vs a single ended. You might want to think about filtering the analog signal (differential and common mode), datasheet recommends LPF 10x sample rate.

Just my 2cents, if someone has better ideas or corrections I'm always happy to learn new things.

At the time that card was designed (2000 vintage), there were standard PCI card sizes.
(and card support slots  for those standard sizes)

I like that sturdy cast base they put this lathe on. You are making a really nice job on that retrofit.

There is a rule of thumb on electrical panels size. They always look 50% too large when you start, and turn out to be 20 % too small

I just got native homing working with an A6 servo the other day.  I have a system with mixed servo drives (two StepperOnline T7 (aka LeadShine EL7) and one StepperOnline A6).  I had to make some custom mods to both the cia402 and custom homecomp components.

Nothing is really documented aside for some sparse comments, so apologies for that.   I can vouch that these modules do work together for homing on an A6 when configured right.  The components are here:

github.com/tangentaudio/linuxcnc-bridgep...tree/main/components

For reference, this homecomp is based originally on the one from marcoreps, not Rod's.

The LinuxCNC config that has the A6 configured on the Z axis is here.  You might want to check out the .ini, .hal and the .xml for hints.

github.com/tangentaudio/linuxcnc-bridgep...eport-ethercat-pyvcp


 

Your retrofit is progressing nicely.

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.