Advanced Search

Perfect!

We established that P1 is Working and the on board rs-485 is working.

Now we can move on to the start:

How to implement pktUART on P1?

Hi Community,

I’m a hobby developer, relatively new to CNC systems, and I’m working on a project where I plan to use LinuxCNC as the controlling software for a robotic component. My use case requires only a limited subset of the CNC functionality, and I’m planning to develop a custom UI for the system. However, I’m struggling to fully grasp how LinuxCNC operates as a system, especially regarding control flow.

I understand that communication happens through NML (Neutral Messaging Language), but so far, I’ve mainly seen the configuration files, scripts, and binaries. What I’m trying to figure out is how the control flows when I jog each axis — how does LinuxCNC communicate down the stack, from generating G-code to sending signals to the motors?

Could anyone point me toward the right resources or provide a simplified overview of the LinuxCNC control flow? Any guidance would be greatly appreciated!

Thanks in advance!

 

For some reason, the pins are not being created.

net machine timer_4.machine_on <= halui.machine.is-on
net spindle timer_4.spindle_on <= halui.spindle.0.is-on
net running timer_4.running <= halui.program.is-running

After I commented them out, the program started, and I have a timer.

There is also a simpler way to turn off eoe by modifying the parameters in the firmware

Start LinuxCNC from terminal and watch for the output, you might see errors.

Norbert

This stems from the short coming of linuxcnc's status process or maybe better a lack of development of GUI communication process.

Gstat is an intermediate communication process between linuxcnc status and the GUi, that is easily modified/extended for the GUI needs.

If a single Gstat instance could be used/communicated to by all GUIs - that would be much better. You can kind of do this by using ZMQ etc to broadcast some data. I don't know if using ZMQ for all linuxcnc status would be fast enough. I was toying with adding it to HALUI as a test but again only some messages.

Or if linuxcnc's status was more easily extended and allowed GUIs to send messages that would be better too.

Chris
This is mostly beyond my programming skills.

Did you check the spam folder?
I did get the notification about your post just now as i get them for every post, and about 30% end up in spam, not in inbox, although they are originating from the same address. No idea why, except it's yahoo so it's a bit senile !

No, I didn't receive any notification.

I did some testing minths ago and have the same results.
With the Rt kernel, AMD graphics have the lowest latency numbers, with the onborad graphics disable into Bios.The onboard Intel ghaphics was 2a and the worst and I don't recommend to use was Nvidia cards. I teste one 1050 and a Quadro and the results are the same. For some reason the native drivers from Debian to Nvidia dont like the RT kernel, and I could no find a soluntion for it.

RNJFAB wrote:

This is awesome Rod !!!! Great work.

I'm just about to begin on my next cnc plasma so we may be in touch again as we move forward with this. 

 

Thanks, drop in any time. You know where to find me 

This is awesome Rod !!!! Great work.

I'm just about to begin on my next cnc plasma so we may be in touch again as we move forward with this. 
 

this drive supports fanuc pulsecoders
siemens resolvers and biss-ssi encoders?

Attached is a Function Block Diagram (FBD) and netlisting for toggling halui machine on/off. Since we are using FBD, signal names are insignificant in this case.  n.1 means net 1 ... etc. Hope this helps
 
#

---

# Load realtime Components and their counts
loadrt and2         count= 4
loadrt not            count= 4
loadrt or2            count= 2
loadrt toggle       count= 1
#

---

# Add functions to threads
addf and2.0                   servo-thread 
addf and2.1                   servo-thread 
addf and2.2                   servo-thread 
addf and2.3                   servo-thread 
addf not.0                      servo-thread 
addf not.1                      servo-thread 
addf not.2                      servo-thread 
addf not.3                      servo-thread 
addf or2.0                      servo-thread 
addf or2.1                      servo-thread 
addf toggle.0                 servo-thread 
#

---

# Set parameters
setp toggle.0.debounce                           5 
#

---

# Connect hal signals to hal component Pins
net gui.pb                     or2.1.in1  
net halui.mc.is-on         halui.machine.is-on  not.2.in  
net halui.mc.off             and2.3.out  halui.machine.off  
net halui.mc.on             and2.1.out  halui.machine.on  
net mc.pnl.pb                or2.0.in0  
net n.1                          or2.0.out  or2.1.in0  
net n.2                          toggle.0.in  and2.0.in0  and2.3.in1  or2.1.out  
net n.4                          toggle.0.out  not.0.in  
net n.5                          and2.2.in0  not.1.in  not.0.out  
net n.6                          not.3.in  not.2.out  and2.1.in1  
net n.7                          and2.0.in1  not.1.out  
net n.8                          not.3.out  and2.2.in1  
net n.9                          and2.0.out  and2.1.in0  
net n.10                        and2.2.out  and2.3.in0  
net pendant.pb             or2.0.in1  

 

Or get a used Dell or HP Z210 with parallel ports or headers, usually from 30 to 100$, built like tanks and never fail. Well they do, but very, very rarely.

Does this work with linuxcnc v2.9.3 ? I am trying to add this timer.But the panel is not created. After starting the program, linuxcnc creates the necessary file to store the times . am i doing something wrong or are there new files for this version