Advanced Search

No, 7I96 TB2 pin 12 is the correct 5V source.

What are the scaling factors that you used?
(there must be a missing hal file  where plasma voltage scaling/offset is done)

They still in business and seem to have there own dedicated controller.

www.baruffaldi.it/wp-content/uploads/201...TB-TBMA-100-2016.pdf

I am using the same probe and probably the same tool setter.  I am using the QT_Dragon_hd UI and Basic Probe not Probe Basic but concept is the same.  I am using whatever QT_Dragon_HD comes with.  I am using a mix of fixed length tools via TTS and random length tools (mostly drills) in a Jacobs chuck. 

For the probe, it is the effective length that you are looking for.  That is the distance from the TTS seat face to the point where the switch opens.  That value will be less that the physical length with the switch not tripped.  What I do to measure that is to put a 123 block in my vise.  Then bring the empty spindle down to just touch the 123 block and note the ABS Z value.  Then I put the probe in the spindle and select tool 99.  Then probe the top of the 123 block. The difference between the previously noted ABS value with the spindle nose on the block and the ABS value of the trip point is the effective length of the probe.  I would do an actual probe of the block rather that manually moving the spindle down until the probe trips.  I think it is more accurate to do an actual probe.  Don't forget to subtract the amount that you have the probe back off of the black after the probe.

I think your issue with getting the "probe tripped during non-probe move" is because you are not in a probing mode G38.?.  It sounds like you are doing a rapid move.  I generally use a G38.2 at speed that is slow enough to find the prod point and then probe very slow when backing of the probe point to get the final probe value G38.2 followed by G38.4 at F1I hope this helps.John
 

I discover that Grizzly rebranded Seig KC6S

I asked they sent me a Manual and parts diagram.

Hello COFHAL,

i am really glad to found your topic. I hope i have the same turret, just one size bigger. I think it could be a TOE120.
Sadly i don’t have a Manual, Schematic, Spec sheet- to be honest it don’t even have a nameplate. i saved it from a beatiful GRAZIANO lathe maybe from the early 1990's? Anyway the machine was scraped with a crane i just could remount the turret in the last minute...

I try to give it a second Life with LinuxCNC, Your Hal, videos and the flow chart are great and a big step forward! Do you have more documentation that you could share? that would be tremendous!




Greetings
Tom

Removed all the old crusty wires.
While I probably could have repaired it is easier just to redo it with updated tech.
All the relays and contractors were 220v coils. Wire insulation was hard and crusty.


 

there is only to be one var file at any time, it can be named whatever you like, but the ini must call that file name. not knowing what version of probe basic you are on or what method of installation you used makes answering your question very difficult. for that purpose, i would say to remove probe basic and reinstall using the apt installation method. going forward this will update probe basic whenever you run sudo apt update sudo apt upgrade to update your system. any changes of note will appear on the status splash page so you should read the notes thoroughly to find if there are any changes required to update your config files and how to do so. this will put you on an easier path going forward. if you have a working config currently, you should be able to simply review the installation docs for the necessary files your config needs from the probe basic simulation as well as any possible edits to your ini file or existing hal files and subroutines folders. it is advised to always copy over the latest subroutine folder or at the least do a file change comparison with something like meld software to determine what changes were made. unless you are modifying the subroutines the easiest way is to simply copy and overwrite the existing subroutines folder.

my guess is that your installation is likely ahead of your outdated config folder, but again, i can't know what you don't disclose so the only sure way for me to instruct you in resolving is to reinstall probe basic. this also assumes you are on the latest Debian bookworm release and the lockdown version of linuxcnc 2.9.4

if you are unsure, i would recommend uninstalling linuxcnc as well and reinstall using the instructions in the probe basic docs. this will put you on the linuxcnc lockdown deb file install which will only be updated when linuxcnc sends out a lockdown release update. this is what probe basic is tested on and what we support.

hope this helps!

Chris

Hi,

I changed the planner's infrastructure so it can use different smooth algo's easy.
This was quite a lot off work.

Now this is the centroid smooth algo on the left. First iteration.
And a catmull rom spline on the right. Second iteration.
The distance from the corners to the spline is the exact G64 P[x] value.
First and last gcode line are original, not curved.

Does not look like pilot start, there is a missing connection for a usually red thinner wire.
More pictures?