Kirk Wallace wrote:
> On Fri, 2011-02-18 at 19:45 -0800, Doug wrote:
>
>> I believe I understand. File should read.
>> loadrt charge_pump
>> # net estop-out charge-pump.enable iocontrol.0.user-enable-out
>> net signal_name master slaves
>> net cp charge-pump.out parport.0.pin-17-out
>> addf charge-pump base-thread
>>
>> Does it the order make a difference?
>> How do I set the hall scope to fast period. I think I know how to set the
>> trigger to charge-pump.out pin.
>>
>> Doug
>>
> Oops, leave the "net signal_name master slaves" line out or comment it
> out.
>
> "
> loadrt charge_pump
> addf charge-pump base-thread
> # net estop-out charge-pump.enable iocontrol.0.user-enable-out
> net cp charge-pump.out parport.0.pin-17-out
> "
>
> The order of the lines does make a difference, in that, in order for a
> component's pins or functions to exist, the loadrt line needs to be
> invoked. After the loadrt line, the pins and functions will have been
> made so then they can be addf'd and net'd. After the loadrt line, the
> other lines can be in any order.
>
> There is an exception. Sometimes you might see a 1 or -1 following an
> addf line. A 1 overrides the line order and puts this command first. A
> -1 places the command last.
>
> Here is an example:
> "...
> # next connect the parport functions to threads
> # read inputs first
> addf parport.0.read base-thread 1
> # write outputs last
> addf parport.0.write base-thread -1
>
> ..."
>
> It's my understanding that the first word after "net" is always a signal
> name and the next word is always an output or master. It gets more
> complicated when the net command is broken into more than one line,
> which is allowed. See:
> http://www.linuxcnc.org/docview/html/hal_basic_hal.html#r1_1_4
>
No, the order of the pin names on a net line isn't important. The
following are all equivalent:
net cp charge-pump.out parport.0.pin-17-out
net cp charge-pump.out => parport.0.pin-17-out
net cp parport.0.pin-17-out charge-pump.out
net cp parport.0.pin-17-out <= charge-pump.out
The arrows ("=>, <=") are optional and for human eyes only. The pin
order makes no difference.
The above can also be split into multiple net lines:
net cp charge-pump.out
and later on
net cp parport.0.pin-17-out
The first net command will create the net and attach only the charge
pump output pin to it. The second net command will see that there is
already a signal named "cp", and will connect the parport pin to it.
- Steve
[snip]
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
