You should consider CL.  For several reasons...

You can "see" the logic on the screen as you run the machine.  You can 
make changes on the fly (almost).  Stop, edit, start.  You can put 
various functions in
different sections of CL logic.  You can comment each line and use 
symbols to show what each contact or coil is.

Once you understand how CL works, making a logic rung is much faster 
than using a bunch of "and" in Hal.

I think the last machine I did has about 60 rungs of CL logic running in 
4 different sections.   If I was to try and do all of that in Hal, it 
would be very difficult to follow.

That said, the same machine also had some hal conversions and special 
stepgen connections setup in Hal so you can use both.  You don't just 
have to use one or the other.

Dave


On 8/7/2010 1:27 PM, Igor Chudov wrote:
> Jon, and others, thanks.
>
> My mill is essentially working fine in 3 axis as of now. Already
> totally usable, just some buttons do not yet do anything, but I can do
> everything with a keyboard.
>
> The future improvements are an encoder on the spindle and 4th axis
> (that Troyke table).
>
> I will give my best shot to doing things the proper way using element
> names in general HAL terms.
>
> i
>
> On Sat, Aug 7, 2010 at 12:16 PM, Jon Elson<[email protected]>  wrote:
>    
>> Igor Chudov wrote:
>>      
>>> I have a large number of machine controls that are on my Bridgeport
>>> Interact mill, such as jog controls, spindle
>>> forward/reverse/start/stop, brake etc.
>>>
>>> I would like to wire them all through EMC/PPMC.
>>>
>>> Where I am very concerned is producing a configuration that I will be
>>> able to understand 3-5-10 years from now.
>>>
>>>        
>> You have to document it.  Make a schematic of the actual wiring, once
>> you get it working the way you want.
>> With numbered wires and terminals, that makes it easier to trace later.
>>
>> Then, add comments for each HAL line that assigns an input pin to a
>> specific function.
>>      
>>> I looked into HALUI and HAL files and logical elements. While I think
>>> that I understand why things were done the way they were, I am very
>>> concerned that a while later, I will not be able to make any sense of
>>> the config and logical elements. That would spell doom for long term
>>> use of this mill.
>>>
>>>        
>> No, it just isn't that complicated.  I can go back to EMC configs I
>> haven't worked on in years and figure out what everything does in a few
>> minutes.
>>      
>>> I read almost all EMC docs yesterday and it would appear that classic
>>> ladder may be a better, more documentable way of looking  at control
>>> logic.
>>>
>>>        
>> I'm not sure Classic Ladder is any better at documentation that HAL,
>> unless you've spent your life in the industrial controls world and
>> ladder diagrams look like road maps to you.  If you have very complex
>> controls, like toolchangers with several arms and many many sensors,
>> then CL may be attractive.  But, I think you can do what you want very
>> concisely with HAL, too.  Some of these connections can be just ONE
>> single line of HAL, linking an input pin to some function in EMC or
>> pyvcp.  Others may need a latch, multiplexer or something.
>>
>> Jon
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Emc-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/emc-users
>>
>>      
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Emc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/emc-users
>
>    


------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to