Advanced Search

If index is detected properly (at the identical rotor angle regardless of speed)
The Z Axis position should be in strict relation to spindle angle so this does seem to
suggest an Index issue or perhaps a Z axis problem (What are the following error limits?).

Perhaps plotting the z axis position and spindle angle in halscope
while threading at different speeds would shed some light on whats going on...

which one is which?

\\\

200\150\100\

?

I tested it and it works, thanks a lot for the good work.

After turning off the A axis, the tool path escapes towards coordinates 0, as in the screenshot, but this can be cleared by double-clicking the mouse.

An idea and a request to do one more thing.
I would like to be able to configure the color of the tool path depending on the type of movement g0, g1, maybe others..
Preferably with an alpha channel, so that individual path colors can be turned off and on.

You are correct, you can do this experiment by hand turning the spindle, and the Z axis will advance. I have not done this against the cuts at various speeds in the picture, so I don't know where the hand turned cut would be.

The behavior is exactly reproducible at the different speeds. That is, if you thread at 100 RPM and then run the program again at 100 RPM, it will cut the exact same thread. If you cut at 100, then at 150, and then back at 100 RPM again, the two 100 RPM cuts will align. I don't think that points towards a encoder/indexer error.

Yeah MrDe, if you can do some kind of write up with the flashing thing, that would be great. Im dont really know what the situation is for that

i think there should be some 5160's there somewhere also. The cnc guys like them because they have higher current rating i think. i like those edge card drivers, they are slick. ive been trying to get the 5160 going but i dont really know what im doing

PCW wrote:

Did you try isolcpus=3

isolcpus 1,2,3 leaves only one CPU for non-realtime tasks so
would likely be painfully slow...

Funny enough, isolcpus=3 and all the BIOS settings disabled I mentioned in my previous post is the final setup I'm going with. It holds steady at low 20μs and am able to multitask fine.

One thing I want to mention though is I was curious what Macanix and gambaf meant in this thread about mozmck's irq affinity hack being necessary. I see what they are talking about now when I started testing the Mesa card. All the issues mentioned in mozmck's thread is what I ran into along with some other threads, but it is running great now after applying the script!

If this thing had a built in parallel port, I think this would be a great, modern LinuxCNC device!

Thanks mozmck for all this info and the bash scripts! This solved the weird issues I was running with on this new N100 PC I have.

I decided to brush up on my bash skills and update the original script.  

Features

• Checks that script is being run as root/sudo.
• Attempts to ping the common Mesa card IP addresses (192.168.1.121 and 10.10.10.10) and if it finds a unique one it will set that as the NIC variable in the irq bash scripts. If it doesn't find one it lists the possible options for the user to choose.
  • Downside of this is that it is not as dynamic as mozmck's script if there are any Mesa card interfaces changes, but I figured people rarely change that anyways.
• Give instructions once the script is complete.

How to run

• Rename rt_setup.sh.txt to rt_setup.sh
• Make sure script is executable via command line:

  chmod +x /path/to/rt_setup.sh

  Replace /path/to/rt_setup.sh to where the actual file is.
• Run script: 

  sudo /path/to/rt_setup.sh

  Again replace to where the actual path of the script is

Hopefully this helps those that are not software savvy!

TMC SPI support is something I've always wanted to get up and going in Remora. My time is starting to free up with the new job being less demanding, always happy to receive hardware to work on. The SKR3 you sent is sitting next to me now with debug wires hanging off it

Great to hear and any help is greatly appreciated. Cakeslob as also been helping out the documentation.

It would be great to document how you got the probe up and running. This seems to be the hardest part for everyone with these boards, just getting the board to flash successfully can be a challenge.

In this QtDragon screen, the RPM showed seems to be the spindle-speed-in. Since I am not using any encoder, I want to show the spindle-speed-out instead. Any suggestion how to do this ? I am quite new with Linuxcnc and would appreciate some help. Thanks

I would do this with two components: a oneshot component and an and2 gate:

The oneshot would be set for 0.5 seconds and triggered by the drawbar signal.
The active high output of the oneshot would drive the low pressure solenoid
(so its driven for 0.5 seconds on the rising edge of the drawbar signal)

The high pressure solenoid would be driven by the output of the and2 gate
The and2 gate inputs would be the drawbar signal and the active-low output of the
oneshot. The active low oneshot output would disable the and2 output driving
the high pressure solenoid for the first 0.5 seconds when the low pressure solenoid
is activated.

 

Hi good folks  

I'm fairly new to linuxcnc, so please go easy on me lol.

I will try to explain what I need. It's not straight forward but im sure one of you geniuses will be able to help me out.

I have a haas mini mill, running linux cnc (probebasic), im 99% finished just the atc pneumatics to do. Now the haas mills have two solenoids to operate the drawbar.

 one opens and closes for 0.5 seconds first to pre charge the cylinder with 20psi. Like a soft push.

the second dose all the hard work and takes over immediately after the first and stays open untill the button is released.

how would this be accomplished?  I have found timedelay, but not sure how to implement it. 

I would also like to be able to control this action with a physical input button. 

I'm on latest linuxcnc using a mesa 7i95T.

Many thanks in advance.

Try this modified primative.py
It adds a new function HideCollection([part],component, pinname)

used something like this:

comp.newpin("hide-chuck", hal.HAL_BIT, hal.HAL_IN)
<snip make a machine with a A axis chuck>
chuckassembly = HideCollection([chuckassembly],comp,'hide-chuck')

Yes, that is common, just use the UV and W, and don't connect the inverted ones.