Torch Breakaway and Torch Pulse

I didn't know the pin name...

phillc54 wrote: I didn't know the pin name...

Code:

#net ohmic:type <= motion.motion-type #net ohmic:type => ohmicsense.motion-type-in net plasmac:motion-type => ohmicsense.motion-type-in

Thanks, as always. I need to find a way to mail you some metric-volume-measurement-units of beer, or start you a go-fund-me or something. :laugh:

I dont understand why we can get rid of the "ohmic:type". Every time I start to wrap my head around HAL, I get turned around. Also, Rod mentioned signals and pins. Stupid question, I'm sure, but how do you know which is which? I wish there was a visual or diagram or something to make this easier to understand. Maybe once it clicks, I'll make one...

ohmic:type is a signal name. Signal names are arbitrary and are only defined when you do a net command.
the pin_ names are defined in the component
the signal_name is whatever you want it to be

think of a LCNC component as being a component or chip on the circuit board say a 555 timer
The pin is a leg on the chip.
By itself its not useful until its connected to another component.
Pins can be outputs or inputs.
So a signal is the arbitrary name you give when you do: So you have now connected a wire called my-sig to a leg on the motion chip ( to an output)
So now you have a wire you can connect it to as many different pins as you like just like you can daisy chain a wire in a circuit.

I added the -in to my pin name to tell me its an input so it expects to receive an output pin from another component.
the <= and => are optional and also arbitrary. they can be left out. BUt the way I've done it, it is obvious what output is connected to my-sig and equally as obvious which inputs that signal is connected to.

I like to always make my declarations on seperate lines but Phill likes to put the signal and the input and the destination all on one line. I found some more complex lines connecting several pins at once need to be redone when I wanted to do something else with one of the pins on the line.

and outputs must be connected to inputs. You would expect that connecting one output on a circuit board could let the magic smoke out if it was connected to another output pin...

phillc54 wrote: ohmic:type is a signal name. Signal names are arbitrary and are only defined when you do a net command.

Code:

net signal_name pin_name => pin_name

the pin_ names are defined in the component
the signal_name is whatever you want it to be

I think it's the fact that they are on two different lines that confuses me. is the same as is that correct? or does it need to be: It seems like "ohmic:type" isnt needed. So I'm not sure why it needs to be there?

rodw wrote: think of a LCNC component as being a component or chip on the circuit board say a 555 timer
The pin is a leg on the chip.
By itself its not useful until its connected to another component.
Pins can be outputs or inputs.
So a signal is the arbitrary name you give when you do:

Code:

net my-sig <= motion.motion-type

So you have now connected a wire called my-sig to a leg on the motion chip ( to an output)
So now you have a wire you can connect it to as many different pins as you like just like you can daisy chain a wire in a circuit.

Code:

net my-sig =>plasmac-motion-type net my-sig => ohmicsense.motion-type-in

I added the -in to my pin name to tell me its an input so it expects to receive an output pin from another component.
the <= and => are optional and also arbitrary. they can be left out. BUt the way I've done it, it is obvious what output is connected to my-sig and equally as obvious which inputs that signal is connected to.

I like to always make my declarations on seperate lines but Phill likes to put the signal and the input and the destination all on one line. I found some more complex lines connecting several pins at once need to be redone when I wanted to do something else with one of the pins on the line.

Ok, Those examples make sense. So since Phill had made that signal in the other file, you can then hook many pins to it. I think I get it. I need to print this off and read it about 4,000 times.

Also the stuff being on different lines sometimes, and on the same line other times screws me up all the time :laugh:

snowgoer540 wrote: or does it need to be:

Code:

net ohmic:type motion.motion-type => ohmicsense.motion-type-in

It seems like "ohmic:type" isnt needed. So I'm not sure why it needs to be there?

That is correct, you need to give the 'net' a signal name so in this case is named ohmic:type

Ok, sorry for hijacking, we can get back on topic. I'm bookmarking this so I can read it each night before bed lol

To get back on topic, we had one vote "yes" from Tommy for an error message:

tommylight wrote:

phillc54 wrote:

snowgoer540 wrote: 1. Should there be an error associated with trying to pulse the torch and either the float switch or the breakaway (or both) is tripped? It might alleviate some inquiries here at a later date?

Dunno, see what others think.

That seems reasonable.

snowgoer540 wrote: Ok, sorry for hijacking, we can get back on topic. I'm bookmarking this so I can read it each night before bed lol

To get back on topic, we had one vote "yes" from Tommy for an error message:

tommylight wrote:

phillc54 wrote:

snowgoer540 wrote: 1. Should there be an error associated with trying to pulse the torch and either the float switch or the breakaway (or both) is tripped? It might alleviate some inquiries here at a later date?

Dunno, see what others think.

That seems reasonable.

While we are exercising our democratic rights:

If we do an error message should it be a popup or one of the standard GUI error messages.

I should also mention the when I did the interlock I included the float switch as that also behaves as a breakaway when not probing.
I also included the ohmic probe but I am not 100% sure if it should be included.