Advanced Search

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 !

For the sunix cards that use parport_serial you need to look here for the list of devices.
github.com/torvalds/linux/blob/master/dr...ort/parport_serial.c

But notice that the driver code used is different depending on kernel version. As I linked to before here.
linux-hardware.org/?id=pci:1fd4-1999-1fd4-0100

Use this page to search by PCI ID to see what drivers match what card.
linux-hardware.org/?view=search

Driver matching & Loading (binding)
docs.kernel.org/driver-api/driver-model/binding.html

Text removed

You'll have to forgive me guys but...

@tommylight - your statement is confusing... I assume you are meaning the .HAL file, because I specifically added the '[SPINDLE]' section to the .INI file. I won't claim it was correct or useful... it was what Google Gemini suggested when I asked (don't shoot me - I've had good success with the AI bots and frankly, I'm just TOO old to try to master 'everything technical'.

Taking your suggestion - I created a new config by starting LinuxCNC, selecting: (attaching screenshots of what I encountered in sequence) 
​​​​​​ 

Try searching for "rugbot" it does the same turning about the Z axis, but makes rugs.

You have my condolences.  I can't image.

I've attached the file.

In the meantime, I have changed my remap to Python. I still use the meaure_tool_inch.ng to measure tools.  I then compare that measurement to what I get when I manually measure the tool to check the accuracy.
 
John
 

Thanks Andy!

I'll give it a go.

ContinenteCNC wrote:

How is this information stored in kernel? Is it hardcoded?

LinuxCNC works with the parport_pc kernel driver. (previous to this you had to blacklist parport_pc).
This means that you can refer to parport0 and parport1, as enumerated by parport_pc, though I am not sure that many do. 

So the problem is somewhere in parport_pc. 

github.com/torvalds/linux/blob/master/dr...parport/parport_pc.c (maybe)

I have one more question about this issue recognizing Sunix cards.

So, let's assume these cards are not being automatically recognized as parallel ports because they are not listed as such in kernel.

How is this information stored in kernel? Is it hardcoded?

I know this isn't a issue that deservs so much talk, but if all it takes is someone to code it and ask a pull request to kernel I would love to do this work.

There are also some cards that load parport_serial driver instead of parport_pc. If this is the case I think that would be a coding I could do.

Again, not a big of a deal, but I would like to help and this seem to match my skills.

That's the go.

vre wrote:

All these CAM are dragknife not tangential.
Tangential knife has an extra C axis that is mounted on Z axis to actively rotate the knife.

Oh sorry I wasn't aware of the difference.

The Axis interface hides the spindle buttons if it doesn't see certain connections in the HAL file:

github.com/LinuxCNC/linuxcnc/blob/master...cripts/axis.py#L4201

The 0V, 5V and 12V pins highlighted look like test points to me. I wouldn't expect them to be scattered about the board like that if they were power inputs.

Nope, this one got away ... for now!

I think that this is probably a built-in assumption in the code.

The canned cycles really expect to be used in X and Y with Z as the drill, and that can only ever drill in the negative Z direction.

If you use this a lot then it might be worth looking at building your own "canned cycle" by using G-code remapping.

Or if you really want to distract yourself from getting the job done, you could look at fixing the source code and submitting a fix. (but discuss it first, so there is agreement on what a fix would look like)

github.com/LinuxCNC/linuxcnc/blob/master...nterp_cycles.cc#L110