Advanced Search

So I've decided to start with a new config and work from there, no embedded tabs to worry about.

New version of Linux, new version of Linuxcnc, new configuration, that's bound to open!!!..........not a bit of it. Another error box.

All as attached.

Any offers?

   
 

I can post if anyone is interested.

Please do.

If anyone is interested I now have a Logitech Dual action F310 controller working as a pendant in LinuxCNC for the Scorbot ER 3 Robotic Arm. I can post if anyone is interested.

Great, yes I have an unused 7i97. Let me know if you need any other info. 

Thanks! 

LinuxCNC/HAL is very powerful and customizable once you get
over the learning curve, looks like you are getting there...
 

I also like Axis a lot, it is like a duck = calm and easy on the surface but beating like hell underneath!

Again, you have one motor spinning in the wrong direction on Y axis, did you check that?

PCW wrote:

Another trick would be to sidestep the "not" issue
and use another (hopefully unused) function to get
the not functionality:

loadrt siggen
addf siggen.0.update servo-thread
setp siggen.0.frequency .1     # 10 second period)
loadrt oneshot
addf oneshot.0 servo-thread
setp oneshot.0.width 2           # 2 second on time
loadrt logic personality=2050
addf logic.0 servo-thread
setp logic.0.in01 true
net cool-trigger siggen.0.clock oneshot.0.in
net coolant-out oneshot.0.out [some_parallel_port_pin]
net coolant-on logic.0.in-00
net gate-coolant logic.0.nand  oneshot.0.reset siggen.0.reset  # when coolant is off, reset both siggen and oneshot


also note that "coolant-on" is a made up signal name, you need to replace it with the actual
signal name used in your configuration for this function
 

I made it work with the "NOT"

I changed

Loadrt not for loadrt not count=3 in main hal.
In postgui hal I have commented loadrt not
I also realized that I didn't change the name of "coolant-on" to the one in my configuration.

Now it works perfect.

What for any of you is a minute for me turns into days T_T
but I really like it because I'm learning a lot about linuxcnc.

thank you very much for the help.
 

Another trick would be to sidestep the "not" issue
and use another (hopefully unused) function to get
the not functionality:

loadrt siggen
addf siggen.0.update servo-thread
setp siggen.0.frequency .1     # 10 second period)
loadrt oneshot
addf oneshot.0 servo-thread
setp oneshot.0.width 2           # 2 second on time
loadrt logic personality=2050
addf logic.0 servo-thread
setp logic.0.in01 true
net cool-trigger siggen.0.clock oneshot.0.in
net coolant-out oneshot.0.out [some_parallel_port_pin]
net coolant-on logic.0.in-00
net gate-coolant logic.0.nand  oneshot.0.reset siggen.0.reset  # when coolant is off, reset both siggen and oneshot


also note that "coolant-on" is a made up signal name, you need to replace it with the actual
signal name used in your configuration for this function

Yes, there's another "not" component instantiated somewhere.
probably best to change the loadrt not command in the main hal
file so it instantiates all the "not" components needed

Pin 17 is an input on the breakout board.
It is an output on the PC.
(Technically, it is bi-directional)

yyao.ca/projects/ParallelPortLinux/

I've tried several mods but unfortunately I keep getting an error.

[qtpyvcp.app.launcher][[36mINFO[0m] Loading POSTGUI_HALFILE: /home/ismael/linuxcnc/configs/Fresadora1/probe_basic_postgui1.hal (launcher.py:96)
not: already exists

Make sure you don't have another 'addf not.0 servo-thread' in your 'probe_basic_postgui1.hal'. If you do you need to use another number (eg 'not.1')

Supposedly the Sunix based cards are OK for EPP mode

(the NetMOS 9805 based PCI cards do not implement EPP properly so can never work)

The python interface is the solution of choice for GUI development and easier to get support. linuxcncrsh is a bit of an exotic solution that few users have experience with.
You can run multiple python scripts that interface with the python API but you need to be aware that having more than one interface sending commands to linuxcnc can lead to race conditions, particularly when sending MDI commands (This is independent of what languages those interfaces use though).
With python you also need to be careful as one python script can block all the others (eg if you wait for an MDI command to finish execution) which can lead to problems like these :
github.com/LinuxCNC/linuxcnc/issues/3120
github.com/LinuxCNC/linuxcnc/issues/3129