Small victory in the war against the Cincinnati cinturn 12u

More
27 Oct 2022 22:38 #255255 by smc.collins

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

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. 

Please Log in or Create an account to join the conversation.

More
27 Oct 2022 22:50 #255257 by andypugh

The question I keep asking is, put what specifically into what file ? Copy the contents of the carousel comp into the hal file ? copy what you posted ?. 
 

In your home directory on the controller PC is a directory called "linuxcnc"
In there is a directory called "configs" and in there is the configuration directory for your machine. It consists of an INI file which specifies all the things that the system needs to know. That INI file will have a [HAL] section where one or more HALFILES are specified. 

You need to add the HAL commands that I have suggested to one of the HAL files. (or, of you want, to a new one, which can be added to the HALFILE list.)

It might help to read this doc to learn what a HAL file is, and does:
linuxcnc.org/docs/stable/html/hal/intro.html

I can't be much less vague at this point, as nobody knows what is in your config files (not even you, it seems?)

Attach the HAL and INI files from that directory to a post here and we will be able to be more specific. 


 
The following user(s) said Thank You: smc.collins

Please Log in or Create an account to join the conversation.

More
28 Oct 2022 03:57 #255288 by smc.collins
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

Please Log in or Create an account to join the conversation.

More
28 Oct 2022 09:43 #255291 by andypugh

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.


Actually, keep things separate for the moment, and create a new file in a text editor (geany is the one that LinuxCNC ships with, in the "development" menu) and add it's filename as a new HALFILE= entry in the ini file.

Are your motor and clamp relays wired back to LinuxCNC yet?

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


I do this for a hobby, and refuse to involve money.

Please Log in or Create an account to join the conversation.

More
28 Oct 2022 23:06 - 28 Oct 2022 23:44 #255351 by smc.collins
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.
Last edit: 28 Oct 2022 23:44 by smc.collins.

Please Log in or Create an account to join the conversation.

More
02 Nov 2022 23:38 - 02 Nov 2022 23:46 #255808 by smc.collins
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 ?
Last edit: 02 Nov 2022 23:46 by smc.collins.

Please Log in or Create an account to join the conversation.

More
03 Nov 2022 00:58 #255813 by tommylight

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

Yes and yes!
It can be on any hal file, but the main machine/coms/and very important stuff should go in the main hal, the rest can go in as many hal files as you like, just do not forget to add them to the ini call list.
There is also the option of calling the same hal file more than once, i think, PlasmaC uses it, i think.

Please Log in or Create an account to join the conversation.

More
03 Nov 2022 03:21 #255816 by spumco

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:
loadrt and2    count=10
loadrt timedelay  count=6
and
...
addf timedelay.3                servo-thread    #SPINDLE FAN
addf timedelay.4                servo-thread    #BLAST
addf timedelay.5                servo-thread    #FEEDHOLD LED
addf and2.0                       servo-thread    #AIR PRESSURE
addf and2.1                       servo-thread    #PDB ENABLE
addf and2.2                       servo-thread    #vc-p4s.hal
addf and2.3                       servo-thread    #BLAST
...
addf toggle.2                     servo-thread    #postgui MIST
addf toggle.3                     servo-thread    #postgui FLOOD

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.

Please Log in or Create an account to join the conversation.

More
03 Nov 2022 22:29 #255873 by smc.collins
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 ?

Please Log in or Create an account to join the conversation.

More
03 Nov 2022 22:42 #255874 by tommylight

#thisneedstobeignored or is #this needs to be ignored until the next line

After the # it does not matter, till a new line

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 ?

Once, at LinuxCNC start, in order they are in the ini file.
So not a loop and no call backs.

Please Log in or Create an account to join the conversation.

Moderators: piasdom
Time to create page: 0.111 seconds
Powered by Kunena Forum