Small victory in the war against the Cincinnati cinturn 12u

arvidb wrote:

smc.collins wrote:

Manual states " use terminal" nobody want's to use terminal but die hard linux users and programmers. I'm like most people, I just want my machines to work, without having to write a thesis

Sadly, the fact that you want a nice GUI for your toolchanger configuration doesn't make one magically appear. (You are obviously very welcome to write one yourself and share it!)

smc.collins wrote:

Basically, treat me as if I am a monkey who eats a banana with his feet and slings poop on the wall. Seriously. and RTFM is not a viable or helpful answer, the manual is written in a way that assumes that a person knows linux and EMC very well.

So in other words, you want someone to read the manual for you, figure out how everything applies to your specific machine, and give you step-by-step instructions so you don't have to think? Drop the entitled attitude. Seriously. It's okay to ask for help, obviously, but don't assume by default that people will do the work for you.

/*rant off*/

    I am happy to PAY CASH MONEY to have the work done, I am under time constraints. I have said that NUMEROUS TIMES. DO you want $$ ? I will pay it. If I cannot find a solution by the end of the weekend I am calling centroid ordering their oak controler ponying up the $4k they want for the hardware/software machine configuration. 

ORRRR 

Could I pay one of you  $1000 to handle this for me ? I really just don't have time anymore to continue with this path of difficulty. My time is too valuable. It's not entitlement to offer to PAY someone for a service. I value your time, let's make a mutually beneficial arrangement. I pay someone for their expertise and knowledge, my machine gets making parts. 

i couldn't locate that hal page, and i kept searching the index, clearly makes more sense now. So i see 2 example hal files in my config folder.

rename 1 of them turret.hal, add signals an pins erc.

got it. I'm going to add a encoder run to the turret, i think it's capable of having more than 6 positions, I'll know more tomorrow, for now, the current switch array will do.

BTW the $1000 offer stands for the configuration work, or resolvers etc. I'm serious about paying for time. I'm swamped and i need it done asap

They are wired back to linux CNC but one of the switches is missing from the run of cables, not sure why but everything with this lathe has been a mess.

should I copy and paste all the availble commands from the carousel hal file ? or just the ones I need ? do I need to put any null statements // or other type of commenting ? I like to comment stuff so is that like typical c/c++ where you use a // denote a comment or is there something else ???

should I put my C axis configuration in it's own hal file as well ? or in the main hal file ?

Also, I still don't understand why setting the spindle to pwm gen 5 is not creating a voltage output to it in the hal file.

attached, these are clones I have on a VM, but everything is identical. I have not wired up much outside of the basic items so far. If you need to move pins around use whichever you like I can move the IO on my relay cars easily.

Alright, so I have been injesting hal documentation for a few days , now my brain feels mushy, ontop of having a work project that is truly driving me bananas, I cannot wait until I can get rid my day job and really focus on cnc top to bottom. 30 yrs of nonsense, I am so done with it.

on topic 


So I am a bit mixed about where speicifically I am supposed to put the calls for 

loadrt or load component etc, is that in the main hal file or in the custom files ? I know I can put the he custom hal configuis along side, but calling them from within themselves, seems a bit circular to me. also the command structure of components deosn't make a lot of sense, is that derived from hal functions or from within the compoonents themselves and can you get a list of commands from terminal or other ?

smc.collins wrote:

So I am a bit mixed about where speicifically I am supposed to put the calls for 

loadrt or load component etc, is that in the main hal file or in the custom files ?
 

From another newish LCNC user... some advice, or at least a suggestion as you develop your hal file(s):

Tommy is, of course, correct.  You can put the loadrt in a 'main' hal file or in another half file to be called via the INI file.  Some people put everything in a single half file, others like to break things up in to logical sections, like:

main.hal
mpg.hal
toolchange.hal

And the 'loadrt' can go in either place.  My preference is to put all loadrt and addf statements in my main hal file and then comment where the functions are - weather it's in a separate hal file or a section of the main hal file.

For example, a snippet from my main hal file:
and
This way I don't forget what each component is for or where it's located.  Of course, each 'section' of the main hal file is commented with #BLAST (or similar) so a text search is easy.

Another personal preference, but I don't rename components just to make them easier to read.  I prefer to leave them as 'or2.N' so I know what they do without referring back to the loadrt section.

So instead of
loadrt and2 names=gibberish1, gibberish2, gibberish3
I use
loadrt  and2   counts=3

One other function you may need to add is the 'TWOPASS=on' function to the INI file [HAL] section.  This function causes LCNC to scan through all the hal files a second time in case a component is used before the 'loadrt' and 'addf' statements are active.

As I am becoming more familiar, it is apparent that ##### is the commenting preceding character ? I assume that Hal reads line by line or does the #thisneedstobeignored or is #this needs to be ignored until the next line

ok ?

So, Hal reads and executes the file how often ? Is it a single loop subroutine ? or a single loop open ended main routine with a need for a callback to start ?