parport does not work in diection "in"

on my PC i have 3 parports, 1 is in built in, and the other 2 are connected on a PCI card, with a script that i found on the web i can find the address of my parports

parport0:
modes:PCSPP,TRISTATE,COMPAT,ECP
ADDR :0x378
IRQ :7
DMA :no DMA used

parport1:
modes:PCSPP,TRISTATE,COMPAT,ECP
ADDR :0x1030
IRQ :21
DMA :no DMA used

parport2:
modes:PCSPP,TRISTATE,COMPAT,ECP
ADDR :0x1020
IRQ :21
DMA :no DMA used


With parport0 (0x378) i control the machine, with parport2 (0x1020) i read signals from the pendant, but i can only use parport2 for my pendant because parport 1 (0x1030) even if set as "in" on the hal_parport cfg line it will not work as in, i can read input 10 but i don't see input from pin 2 to pin 9, same goes if i try to connect the pendant to the parport0 (0x378) it will not work properly even tough i set "0x378 in" on the hal_parport cfg line

But i can use parport2 (0x1020) as in or as out without problems, i don't understand why the other two ports work only as out, i need to ass supplementary inputs to control an automatic tool change but i'm stuck at making the port read my inputs, any help?

Hi

PCI parport cards can be a vexed question, you will need to provide more info.

Sounds like you have a single dual port card, one hard wired port and one on a flyer from a header on the card?

We will need to know make, model, what chipset etc and output from 'lspci -vv' before anyone can venture an answer.

regards

yes i have exactly what you described, i'll give you more info tomorrow, but even the parport built in the motherboard (0x378) does not seems to work in "in" direction...

The only one that works both ways "in" and "out" it's the one on the flyer...

even the parport built in the motherboard (0x378) does not seems to work in "in" direction...

Hi

Whilst the print you generated shows the available modes, it does not say what mode the internal parport is in, that will be controlled by BIOS setting

See below, setting to SPP mode seems most likely to be successful, but there are other considerations such as whether your pendant is buffered / isolated, before you consider attaching it directly to the built-in port.
Its much easier to replace a card than a motherboard.

www.linuxcnc.org/docview/html//hal_drivers.html

regards

PS

I would also be very sceptical about both the card port addresses from your print being correct, they are only 0x10 apart.

lspci -vv from my machine with a dual port card shows something much more familiar
0x5c00 is the hardwired parport and 0x5800 is the fly lead, which is currently unused

03:05.2 Parallel controller: NetMos Technology Unknown device 9865 (prog-if 03 [IEEE1284])
Subsystem: Unknown device a000:2000
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin C routed to IRQ 11
Region 0: I/O ports at 5c00
Region 1: I/O ports at 5800
Region 2: Memory at e0205000 (32-bit, non-prefetchable) [size=4K]
Region 4: Memory at e0204000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot-,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-

this is what lspci -vv give me

Communication controller: NetMos Technology PCI 9815 Multi-I/O Controller (rev 01)
Subsystem: LSI Logic / Symbios Logic Device 0020
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR+ INTx-
Interrupt: pin A routed to IRQ 21
Region 0: I/O ports at 1030
Region 1: I/O ports at 1028
Region 2: I/O ports at 1020
Region 3: I/O ports at 1018
Region 4: I/O ports at 1010
Region 5: I/O ports at 1000
Kernel driver in use: parport_pc
Kernel modules: parport_pc

i went in the bios and put the parport setting to SPP but nothing changed, i'm going to try and set it as bi-directional to see if it fixes the problem