Are we talking about this documentation?
http://linuxcnc.org/docs/2.5/html/hal/basic_hal.html#_net_a_id_sub_net_a
if so, the syntax
net <signal-name> <pin-name> <opt-direction> <opt-pin-name>
doesn't really reflect what "net" will actually accept. I've revised
the documentation to hopefully improve things:
1.4 net
The command net creates a connection between a signal and and one or
more pins. If the signal does not exist net creates the new signal.
This replaces the need to use the command newsig. The optional
direction indicators <=, => and <=> are only to make it easier for
humans to follow the logic and are not used by the net command.
The syntax and an example:
net <direction>* <signal-name> <direction>* <pin-name>
(<pin-name>|<direction>)*
net both-home-y <= parport.0.pin-11-in
A pin can be connected to a signal if it obeys the following rules:
* An IN pin can always be connected to a signal
* An IO pin can be connected unless there’s an OUT pin on the
signal
* An OUT pin can be connected only if there are no other OUT
or IO pins on the signal
The same <signal-name> can be used in multiple net commands
to connect additional pins, as long as the rules above are
obeyed.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
