gene heskett wrote:
> Greetings;
>
> As I read the hal manuals getting started section, where the keywords 
> loadrt, setp, addf, and net are defined, I didn't understand at first that 
> arg[3], arg[4] arg[5] etc of a "net" commend can be repeated to add sending 
> something from arg[2] to more than one load.  But I can't name a previously 
> used output and send it to the 2nd place it needs to go.  Its s show 
> stopper error.
>
> Is this intentional, or do I likely have a deeper miss-understanding?
>
>   
If some process is feeding data to a pin, you can't feed different data 
to the same
pin.  First, you have to UN-link the original sender of the data before 
you can
link a new sender.  The less well known command unlinkp <pin  name> 
unlinks that
pin from any signal that is sending it a value.  You can then link it 
with a new
net command.

I am not sure this is the info you needed, but since nobody else made 
this interpretation
of your question, I thought I should mention it.

Maybe THIS is what you are asking, though!  You have an output pin, 
linked to
a signal.  You now want to link that output pin to a different signal.  
that is not
permitted, as far as I know.  BUT -- you can link the already existing 
signal
to MORE input pins later.  So, the following is legal :

net siga  out.pin.1  in.pin.1 in.pin.2
net siga in.pin.3 in.pin.4

Now, the output pin out.pin.1 is sent to siga.  The second net command 
extends
what pins the value of siga is sent to, so the same value is now sent to
in.pin.1 through in.pin.4

Jon

------------------------------------------------------------------------------
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

Reply via email to