Spindle control not showing in Axis window...

INI =hal files and settings and scaling and....
HAL = connections between software and actual hardware
So if there is nothing about the spindle in hal = no spindle
And no shooting today, slept in total 5 hours in last 3 days, so i might miss !

OK - I now have spindle control...

@tommylight - your post(s) about 'no spindle' configurations and suggestion to make a new config finally helped my 'through the forest'.

Not that I would ever 'bite the hand that feeds me', I have to ask if you were coaxing me in to discovery? I mean - how much more effort would it have been to state something like "the line in you HAL 'net spindle-on      => parport.0.pin-09-out' does not initiate the spindle. It defines or assigns a pin to use (pin 9), but it doesn't actually make the pin 'do anything'. What you need is a line that connect the assigned pin to a function like this: 'net spindle-on spindle.0.on => parport.0.pin-09-out'"

First - I am just 'making this up' because I really do not understand the structure and syntax of the lines in the HAL file (something that I really think would have helped me in my discovery). Please feel free to delete this post or tell me to do so because I certainly do NOT want to confuse anyone else.

If this kind of documentation already exists somewhere - I certainly did not find it, but if you point me to it, I will be certain to explore. Meanwhile - thank you both again for your assistance and direction to resolving my issue!

Regards,
Arden

linuxcnc.org/docs/html/hal/intro.html

Is a good starting point

irwinger wrote:

Not that I would ever 'bite the hand that feeds me', I have to ask if you were coaxing me in to discovery? I mean - how much more effort would it have been to state something like "the line in you HAL 'net spindle-on      => parport.0.pin-09-out' does not initiate the spindle. It defines or assigns a pin to use (pin 9), but it doesn't actually make the pin 'do anything'. What you need is a line that connect the assigned pin to a function like this: 'net spindle-on spindle.0.on => parport.0.pin-09-out'"

Yes that would have been more helpful for sure, in the long run.
I insisted on making a new config as i have seen way to many wander of in the depths oh hal and getting utterly lost and dazed and confused, subsequently giving up on LinuxCNC altogether, so my main aim for new users is to make the machine work first and foremost, then we can chat about options and bells and whistles.
I am glad you are one of the more analytical types and jump head first into problems, will try to keep in mind that next time i reply.
And, no, i am not deleting this, nor do i want you to delete it, it is a valid and respectful response.

This is where i started back then, although i can not find a recent version of it not the exact one i used, but i had this printed and on my desk at all times for months
linuxcnc.org/docs/2.6/pdf/LinuxCNC_Integrator_Manual.pdf
The exact procedure was, i downloaded the 6.04 or 8.04 ISO, installed it, used the stepconf wizard, powered on the machine and it happily engraved EMC2 (that was LinuxCNC back then) on the table, albeit mirrored, so a bit of reading and found out i can edit the hal file and just add minus sign to scale to reverse the offending motor, opened the hal file and had a quick glance for about 10 seconds where my brain went boom thinking this is just like wiring stuff with wires!
Love at first edit.

Thanks you @tommylight - I was somewhat fearful that my response was offensive and it was by no means intended to be. @PCW pointed me to the HAL documentation (I didn't discover that part of the documentation myself because I was 'spindle' focused and not 'general hardware') which was still 'over my head' because (I think) it is written from an integrator's context/viewpoint.

EDIT:
Opened and browsed the 'Integrator Manual' you referenced. It's 342 pages in length... I think that competes with 'War and Peace' for 'longest book'. BUT! definitely where I should have been focused. That document will be on my desktop and as I have time - I will be reading it.

Thank you everyone for your hints and help - my 'voyage of discovery' has exited the rough waters of the storm (my system is yet again working) and I will be gracefully sailing smooth waters as I figure out how to implement 'auto-zero' for Z (not sure that's the correct term) and maybe even some custom G-code sequences for startup and shutdown.

Arden