× Forum Header

Please help, I need some addvise

More
26 Apr 2013 22:28 #33249 by allenwg2005
Good to hear from you Todd, thanks for continuing to check in.

I should mention, I have installed three additional LPT ports to the machine in addition to the port on the mother board. (Should have mentioned that earlier, sorry).
I figured it wouldn't work with xmod so I got three.
I should also mention (if I missed mentioning it earlier) the third board is for a joy stick and not the primary driver functions. I will have to sort it out after I am able to get some control over the machine
with Linuxcnc.

Thanks again everyone.

Please Log in or Create an account to join the conversation.

More
26 Apr 2013 22:44 #33251 by allenwg2005
Andy, here's the output of "sudo lspci -vv"

:~$ sudo lspci -vv
[sudo] password for allen:
00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge
Subsystem: ASUSTeK Computer Inc. Unknown device 8118
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: 8
Region 0: Memory at e0000000 (32-bit, prefetchable) [size=64M]
Capabilities: [80] AGP version 3.5
Status: RQ=32 Iso- ArqSz=0 Cal=2 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge (prog-if 00 [Normal decode])
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: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: e8000000-e9ffffff
Prefetchable memory behind bridge: e4000000-e7ffffff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR+
BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:08.0 Communication controller: Unknown device 5372:6872 (rev 01)
Subsystem: LSI Logic / Symbios Logic Unknown device 0012
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at 8000
Region 1: I/O ports at 8400
Region 2: I/O ports at 8800
Region 3: I/O ports at 8c00
Region 4: I/O ports at 9000
Region 5: I/O ports at 9400

00:09.0 Communication controller: Unknown device 5372:6872 (rev 01)
Subsystem: LSI Logic / Symbios Logic Unknown device 0012
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 9800
Region 1: I/O ports at 9c00
Region 2: I/O ports at a000
Region 3: I/O ports at a400
Region 4: I/O ports at a800
Region 5: I/O ports at ac00

00:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. A8V Deluxe or A8N-VM CSM Mainboard
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: 32 (8000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 3
Region 0: Memory at ea000000 (32-bit, non-prefetchable) [size=2K]
Region 1: I/O ports at b000
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V Deluxe/K8V-X/A8V Deluxe motherboard
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: 32
Interrupt: pin B routed to IRQ 11
Region 0: I/O ports at b400
Region 1: I/O ports at b800
Region 2: I/O ports at bc00
Region 3: I/O ports at c000
Region 4: I/O ports at c400
Region 5: I/O ports at c800
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard
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: 32
Interrupt: pin A routed to IRQ 0
Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable)
Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable)
Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable)
Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable)
Region 4: I/O ports at cc00
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard
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: 32, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 10
Region 4: I/O ports at d000
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard
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: 32, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 10
Region 4: I/O ports at d400
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard
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: 32, Cache Line Size: 32 bytes
Interrupt: pin B routed to IRQ 11
Region 4: I/O ports at d800
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard
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: 32, Cache Line Size: 32 bytes
Interrupt: pin B routed to IRQ 11
Region 4: I/O ports at dc00
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard
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: 32, Cache Line Size: 64 bytes
Interrupt: pin C routed to IRQ 5
Region 0: Memory at ea001000 (32-bit, non-prefetchable)
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard
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: 0
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Subsystem: ASUSTeK Computer Inc. Unknown device 810a
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-
Interrupt: pin C routed to IRQ 5
Region 0: I/O ports at e000
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
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-
Interrupt: pin C routed to IRQ 5
Region 0: I/O ports at e400
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
Subsystem: ASUSTeK Computer Inc. Unknown device 80ff
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: 32 (750ns min, 2000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at e800
Region 1: Memory at ea002000 (32-bit, non-prefetchable)
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Unknown device 8118
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: 32 (500ns min)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at e4000000 (32-bit, prefetchable) [size=64M]
Region 1: Memory at e8000000 (32-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at e9000000 [disabled] [size=64K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [70] AGP version 2.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4
Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4

Please Log in or Create an account to join the conversation.

More
26 Apr 2013 23:28 #33253 by ArcEye

I have installed three additional LPT ports to the machine in addition to the port on the mother board. (Should have mentioned that earlier, sorry).


Looking at the advert, I suspect that they are the same card and chip that is used for a twin serial plus parport card, they just haven't connected up the serial ports
(you can see the spaces for the 2 header cable blocks)
This may explain why you have 3 ports apparently showing.

If so, from previous NetMOS cards I have dealt with, the likelihood is that the first address is the parport, the second a data register and 3rd and 5th would be serial if connected.
This is far from certain through

For now I would forget about using them with your drives and just put them into a normal stepper config and see if you can get them recognised
What I mean is generate a bog standard 3 axis mill config with no home switches, estop or limits and just one port at 0x378

Then once that will load, add the other port addresses to the hal file and have a look at HAL Configuration and use JTs port tester to see if they are correct
See www.linuxcnc.org/index.php/english/forum...-parallel-port-cards

Then you will be able to progress.

regards

Please Log in or Create an account to join the conversation.

More
27 Apr 2013 06:19 #33263 by allenwg2005
Arceye,

What a clever idea, I went through the step configuration wizard and I got it loaded.
This is the first time I have seen the Linuxcnc interface.

I am posting the “test_card.hal” file results so I can make sure what I have is what is supposed to be there and get the correct advise going forward.
Reading through the link you sent and comparing what I have as well as trying to remember the details
from the Hal Manual has left me a bit dizzy.

Please let me know how to proceed if possible.

Thanks

# Generated by stepconf at Sat Apr 27 11:31:05 2013
# If you make changes to this file, they will be
# overwritten when you run stepconf again
loadrt trivkins
loadrt [EMCMOT]EMCMOT base_period_nsec=[EMCMOT]BASE_PERIOD servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[TRAJ]AXES
loadrt probe_parport
loadrt hal_parport cfg="0x378 out "
setp parport.0.reset-time 5000
loadrt stepgen step_type=0,0,0

addf parport.0.read base-thread
addf stepgen.make-pulses base-thread
addf parport.0.write base-thread
addf parport.0.reset base-thread

addf stepgen.capture-position servo-thread
addf motion-command-handler servo-thread
addf motion-controller servo-thread
addf stepgen.update-freq servo-thread
net spindle-cmd <= motion.spindle-speed-out

net xstep => parport.0.pin-02-out
setp parport.0.pin-02-out-reset 1
net xdir => parport.0.pin-03-out
net ydir => parport.0.pin-05-out
net ystep => parport.0.pin-06-out
setp parport.0.pin-06-out-reset 1
net ydir => parport.0.pin-07-out




setp stepgen.0.position-scale [AXIS_0]SCALE
setp stepgen.0.steplen 1
setp stepgen.0.stepspace 0
setp stepgen.0.dirhold 46971
setp stepgen.0.dirsetup 46971
setp stepgen.0.maxaccel [AXIS_0]STEPGEN_MAXACCEL
net xpos-cmd axis.0.motor-pos-cmd => stepgen.0.position-cmd
net xpos-fb stepgen.0.position-fb => axis.0.motor-pos-fb
net xstep <= stepgen.0.step
net xdir <= stepgen.0.dir
net xenable axis.0.amp-enable-out => stepgen.0.enable

setp stepgen.1.position-scale [AXIS_1]SCALE
setp stepgen.1.steplen 1
setp stepgen.1.stepspace 0
setp stepgen.1.dirhold 46971
setp stepgen.1.dirsetup 46971
setp stepgen.1.maxaccel [AXIS_1]STEPGEN_MAXACCEL
net ypos-cmd axis.1.motor-pos-cmd => stepgen.1.position-cmd
net ypos-fb stepgen.1.position-fb => axis.1.motor-pos-fb
net ystep <= stepgen.1.step
net ydir <= stepgen.1.dir
net yenable axis.1.amp-enable-out => stepgen.1.enable

setp stepgen.2.position-scale [AXIS_2]SCALE
setp stepgen.2.steplen 1
setp stepgen.2.stepspace 0
setp stepgen.2.dirhold 46971
setp stepgen.2.dirsetup 46971
setp stepgen.2.maxaccel [AXIS_2]STEPGEN_MAXACCEL
net zpos-cmd axis.2.motor-pos-cmd => stepgen.2.position-cmd
net zpos-fb stepgen.2.position-fb => axis.2.motor-pos-fb
net zstep <= stepgen.2.step
net zdir <= stepgen.2.dir
net zenable axis.2.amp-enable-out => stepgen.2.enable

net estop-out <= iocontrol.0.user-enable-out
net estop-out => iocontrol.0.emc-enable-in

loadusr -W hal_manualtoolchange
net tool-change iocontrol.0.tool-change => hal_manualtoolchange.change
net tool-changed iocontrol.0.tool-changed <= hal_manualtoolchange.changed
net tool-number iocontrol.0.tool-prep-number => hal_manualtoolchange.number
net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared

Please Log in or Create an account to join the conversation.

More
27 Apr 2013 12:19 #33267 by ArcEye
Just change this line

loadrt hal_parport cfg="0x378 out "

to

loadrt hal_parport cfg="0x378 out 0x8000 out "

and look to see in Machine > HAL Configuration - Pins - parport1 if the parport pins are present
If not try the other numbers (alternate ones 3rd 5th)
Then you can test with JTs port tester

Do the same afterwards for for the other card

(Once you are happy with them you can change the second 'out' to 'in' and see if you are able to configure pins 2-9 as input if that is required)

regards
The following user(s) said Thank You: allenwg2005

Please Log in or Create an account to join the conversation.

More
27 Apr 2013 18:40 #33274 by andypugh

loadrt hal_parport cfg="0x378 out 0x8000 out "

and look to see in Machine > HAL Configuration - Pins - parport1 if the parport pins are present


I just tried this on a machine that definitely doesn't have a second parport at 0x8000 and hal_parport still cheerfully created the pins.

It might be worth trying the automatic enumeration method. Note that I think it will fail, and if it does it may leave the 0x378 parport "claimed", which is probably most easily fixed with a restart.

loadrt hal_parport cfg="0 out 1 out 2 out 3 out"

Will attempt to locate the 4 parallel ports automatically. The dmesg output might be interesting.
The following user(s) said Thank You: allenwg2005

Please Log in or Create an account to join the conversation.

More
27 Apr 2013 23:20 #33291 by ArcEye

loadrt hal_parport cfg="0x378 out 0x8000 out "

and look to see in Machine > HAL Configuration - Pins - parport1 if the parport pins are present


I just tried this on a machine that definitely doesn't have a second parport at 0x8000 and hal_parport still cheerfully created the pins.


It will create pins for spurious port numbers, but they obviously won't work.

You need to load the port by number and then test the pins to see if they work and are real.

I would be interested too, to see if HAL can automatically divine the ports, that would be really useful

regards

Please Log in or Create an account to join the conversation.

More
28 Apr 2013 00:43 #33294 by allenwg2005
I am going to take the time to ask what I'm sure are going to be stupid questions to the rest of you, rather than assume I know what I'm doing and create real problems.
I would rather look like a fool asking these questions than screw things up and waste everyone’s time trying to unscramble scrambled eggs.
It's off topic, but it may be worth mentioning that I am a tactile learner, if I can get my hands on it I can understand it, the problem here is, software is virtual, I can't get my hands on it!
To make matters worse software has a language all it own, and I don't fully understand it yet.
You've all been incredibly kind and patient already, please continue to bare with me.

Let me start buy asking how do I “look to see the hal configuration”, after making these changes?
I thought the .hal file was a configuration file.
Or do I type “halrun -I -f saved.hal” to see the configuration file in question?


After I sent the “test_card.file” (my last post) I made the changes Arceye suggested ahead of his response,

loadrt hal_parport cfg="0x378 out 0x8000 out "

I stopped there because of my next question:

I need to understand exactly were to type the following:

addf parport.1.read base-thread
addf parport.1.write base-thread
addf parport.2.read base-thread
addf parport.2.write base-thread

Or do I need these command at this time?
I know I need them in any case, so nailing this down now rather than later seems worthwhile.
The section in the Hal Manual on “addf” is brief, I know it adds a real time function to a thread, and it is done prior to loading net commands creating connections between a signal (a virtual wire) and the pins we are trying to make changes to eventually. (A pin, something physical, finally).
But is there a sequence or order to where these commands are added?

My next question:
When running John T's tester, I expect the best way to confirm the address and port are functioning correctly is to use the “Resistor to Gnd” method. The proximity or limit switch method (for my part) seems ambiguous at the moment. Is there any other method to use the “Testport Meter”?
Or, can I just toggle the buttons for now and get the results we need and use the resistor when we try and test for output at a pins?

Andy, I'm reluctant to try your suggestion until I have my mind wrapped around all of this.
Thank you for going to the trouble to do the testing you did, My guess is it will play a roll very soon.

Thanks again, Allen

Please Log in or Create an account to join the conversation.

More
28 Apr 2013 01:55 #33295 by andypugh

Let me start buy asking how do I “look to see the hal configuration”, after making these changes?


If LinuxCNC is starting up, then you can see the configuration in the menu option:
Machine->Show HAL Confguration.

The HAL components (such as hal_parport) all create lots of pins, many of which you can ignore most of the time.

If you are working from the command line (halrun prompt) then the "show" command such as "show pin" can show you what you have.

Please Log in or Create an account to join the conversation.

More
28 Apr 2013 05:56 #33302 by allenwg2005
Well that was easy enough.

Andy is right, it seems Hal will generate pins no matter what address I use with the same out, in-not and in results.
Example of pin 1:
1 out
Example of pin 15:
15 in-not
15 in
ect.

I may have gotten ahead of myself here but I tried Andy's command line:
loadrt hal_parport cfg=”0 out 1out 2 out 3 out”
Linuxcnc did not open and a restart didn't change anything, Linuxcnc didn't open.
If I did something wrong let me know I would like to help satisfy everyones curiosity about this.
I did look at dmesg before I made the following changes and I'll put a copy at the end of this post or attach it.

I changed the line back to:
loadrt hal_parport cfg=”0x378 out 0x8800 out”,
and Linuxcnc still would not start, I shut down and rebooted the PC and I have Linuxcnc back again.

What should I do next?

Please Log in or Create an account to join the conversation.

Time to create page: 0.115 seconds
Powered by Kunena Forum