Advanced Search

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

Yes. Tried it before. Might be a faulty 7i43. Or I shoul test with an old pc with an "real" parport.

PCW wrote:

Yes, all this will work on a parallel port.

something like this:

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 not
addf not.0 servo-thread
net cool-trigger siggen.0.clock oneshot.0.in
net coolant-out oneshot.0.out [some_parallel_port_pin]
net coolant-on not.0.in
net gate-coolant not.0.out oneshot.0.reset siggen.0.reset  # when coolant is off, reset both siggen and oneshot


 

Tried to test it but received an error. If I remove the lines that I have added in hal linuxcnc starts normally

You might try reversing the addresses based on the lspci order:

Region 0: I/O ports at d010
Region 1: I/O ports at d000

It may also be that the 7I43 is damaged

Mhmmm.
loadrt hm2_7i43 ioaddr=0xd000 ioaddr_hi=0xd010 epp_wide=0 config="firmware=hm2/7i43-4/SVST4_4.BIT num_encoders=0 num_pwmgens=0 num_stepgens=3"
gives me:

0xd400 cannot be a valid address as its not listed by lspci

that is,  "ioaddr_hi=0xd010" should be tested

Also hm2/7i43-2/SVST4_4.BIT is a bitfile for a 7I43-2, but you have a 7I43-4
 

I can get some strange results:
loadrt hm2_7i43 ioaddr=0xd000 ioaddr_hi=0xd400 epp_wide=0 config="firmware=hm2/7i43-2/SVST4_4.BIT

Gives me:
No parport registered at 0xd000. This is not always an error. Continuing.
hm2/hm2_7i43.0: invalid cookie, got 0x00000000, expected 0x55AACAFE
hm2/hm2_7i43.0: FPGA failed to initialize, or unexpected firmware?
hm2_7i43.0: board at (ioaddr=0xD000, ioaddr_hi=0xD400, epp_wide OFF) not found!
hm2_7i43: rtapi_app_main: Invalid argument (-22)

If I change to:
loadrt hm2_7i43 ioaddr=0xd010 ioaddr_hi=0xd410 epp_wide=0 config="firmware=hm2/7i43-2/SVST4_4.BIT

I have to change to the 7i43-4 firmware because linuxcnc said thats tghe wrong one. Wit 000 and 400 it is vise versa...

This version doesn't have the jog buttons, but the problem was the same when they were displayed.

Ok. that is new:

cnc@linuxcnc:~$ sudo mesaflash --epp --device 7i43 --addr 0xd000
[sudo] Passwort für cnc:

EPP device 7I43 at 0xD000:0xD400