Advanced Search

I did copy the output of `lcec_configgen` into `~/linuxcnc-dev/configs/` . After rebooting I did not notice anything different. Is there some initialization or command to get this xml processed by HAL? I have attached my xml to ensure it appears as expected.

Regards,

Steve Cap

HI, I need to modify the AXIS GUI, and so I have some questions about it:

1) Whatś the name of the file ?
2) Is written in Python?
3) Which application I need to work with or compile it?

I have to work with it on a Debian 12.

Thanks a lot

It's a relatively recent tool, developed by Scott when he overhauled lcec.
Bits and pieces are around, but I am not aware of any structured documentation on
how to set up Ethercat and find info like the one you asked for.

Sorry for disturb,i have an problem with my nvem board,is same as board on this topic,im write here but im undestand we are expert on pcb .....when im power on the grren led blink at 10% of light and speed,the item on pcbU7 "DE=G12" is hot and ,the led "D15" blink when insert a cable,the situation of led not change and switch or pc not blink he light.
we have any idea for solve my situation ??
sorry for disturb

Maybe i was not "tactful" enough:
-no need to be sorry at all
-i was trying to give you a push to move forward
-when you start wiring stuff it will be stressful, but when you see things move you will be very happy
-when you see the machine actually working, oh what a joy !

I got my touchscreen monitor delivered yesterday and just wanted to confirm that the issue I was having with touchscreen button not working right was a consequence of using Flex GUI in a virtual machine on windows. The Flex GUI that I made works perfectly on a real machine with touchscreen. For the real machine I am using a RPi 4b and a generic 10" touchscreen monitor.

For anyone else designing their GUI this way, I am using VirtualBox on a Windows 10 machine. The virtual Machine has LinuxCNC 2.9.4 installed from the live iso download. Here are the couple quirks I have found running it in the virtual machine. I want to stress that these issues don't exist once the .ui file is put on my RPi machine.

1. touchscreen buttons don't respond as expected in virtual machine
2. The machine will unexpectedly go to "Power Off" as soon as a motion command (Jog, MDI, or in a program) completes. Doesn't do it every time, but pretty often. Again, only in the virtual machine.
   
   I also want to again give thanks for this wonderful tool and to give a peek at what I am working on. I have a 3 axis benchtop mill (RF-45 size) that I converted to CNC a few years ago. I did this as a hobby and use the machine for my hobbies. It has been run with many things including LinuxCNC on an old tower PC with ancient monitor, keyboard and mouse, with GRBL on an Arduino hooked to a Netbook with my own Visual Basic interface, and I tried one of those standalone controllers, but sent it back because it was junk. I finally decided to just do it better and got a RPi 4b, installed LinuxCNC and have been working on an interface that for most of the way I use the mill can be done without ever touching a keyboard. I'll still have a small wireless keyboard with trackpad available if needed though. This is the interface I'm working on and I think it will suit me. I have the UI sized to perfectly fit the display that I bought to use as much space as possible. Thanks again for the very useful tool.
   
   John B
   
    
   

The spindle is off:

bit FALSE pdnt.spindle.is-on ==> hm2_7i76e.0.7i76.0.0.spinena
 

Start wiring stuff, make things move, stop worrying to much.
I do not recall the exact amperage, but i do recall it was more than enough for what you need.

Can you find a FBUC?
If you call Elumatec or FerroControl, make sure you are sitting when they tell you the price. I was asked 27000 Euro for the old PC!
Check the drive manuals if they can use something else for control, and if they do output encoder pulses, that would make things much easier.

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:~$