Advanced Search

Delete the red potion and make sure the lines above and below it are there still for the manual tool change.

need some lines in your main hal file also, check the docs it spells it out very clearly in the machine config setup docs. step 5.

kcjengr.github.io/probe_basic/machine_config.html

Hello All!

We are preparing to merge a BIG Probe basic update. it will require some config setting updates and some new folders be added.  I have added a new "Update Release Notes" section to the docs page which should be very helpful going forward for when we have updates release.  please feel free to have a look and give feedback!

kcjengr.github.io/probe_basic/update_notes.html

My manual tool changing does the Probe Basic. 
If in MDI I use "T2 M6 G43" , the line stays active with the play icon, but never ends.  The same issue in NC files.

Nothing happens, no pop-up, etc

Here is probe_basic_postgui.hal

forum.linuxcnc.org/show-your-stuff/32784...-15-retrofit?start=0
Payed much more (3280 Euro + Mesa boards) for this but it was working...till mice had a run at it in my shop!
Retrofitted and working with LinuxCNC (see videos on that link), so yes it is worth retrofitting it.
Difficulty is high for sure, so see if you can get the schematics for it, that will save a lot of time and headache.

Do it, we are here to help as much as humanly possible.

I am new to LinuxCNC, but I play a software engineer in life.  I have identified a few areas where new or updated (and refactored) components could be beneficial.  What is the current best practice to build HAL components?  I would assume halcompile, but more specifically, .comp files or just long-hand .c?  The components that I am currently thinking about are in the user-space.   The first one I want to tackle is an updated/new hy_gt vfd component.  I am running 2.9, so backward compatibility is not a personal concern for me, but maybe people don't update?

Any feedback would be appreciated.
Thanks
 

Saw this old iron while entertaining the machinery buying itch today on Kijiji -- www.kijiji.ca/v-other-business-industria...i-hit-18s/1716314528

That link will go dead with time, so for the record it looks like a Hyundai HIT 18S for $2k Canadian, not working. Seller says it has some repaired drives. I probably need to ask more questions, just not sure what all the right ones are.

Seller might be asking too much, but says he's open to offers. Any thoughts from more experienced heads here, whether or not something like this is worth a look and a retrofit? Or should I be running the other way fast as I can? I don't have any impressions, good or bad, about Hyundai quality, and I'm not sure what dead machines should generally go for.

On the scale of difficulty for retrofits, where does a machine like this fall? I'm no expert with HAL but have dabbled a little. Built my own plasma table with 7i76e and a couple THCAD's by riding on the shoulders of giants on this forum.

Thanks in advance for any time you spend looking at this.

The latest QtDragon version at github.com/persei802/QtDragon_hd has a button for using a manual tool gauge. You use it by selecting Manual Tool Gauge in the Settings page, then lowering the tool until your gauge reads 0 and then press the Manual Touchoff button. 
Jim
 

the repo in the github configured like this:

you get:
4 step-generator
1 encoder-counter
gpio input pins (10, 11, 22, 26, 27, 28)
gpio output pins (12, 13, 15)
1 pwm channell (gp14)

so you can use it with a cheap printerpot breakout board. i currently working on a breakout board mixed with the io-samurai project to add +8 digital output and 16 digital inputs to this ().

but you can configure other ways if you want, more encoders for less inputs or no ecoder for extra 2 input or output. the hal driver uses the same configuration file so only 1 place change is need to change the configuration.

The configuration file is in the repo (firmware/w5100s-evb-pico/inc/config.h)

or if you want much more inputs and outputs use my io-samurai project, open source with the PCB production files. (only works with the W5100S-EVB-PICO or equivalent pico + w5100s breakout board)

if you want faster response please use the discord link in the repo.

 

 

Yes, that could definitely be the case. It's a very old machine—27 years old—but I decided I want to give her a new life. The structure is really solid, plus it has vacuum and lubrication for aluminum, which is great.
So, I want to do this retrofit, and I think the setup I posted here should get the job done. The only thing I have to do is adapt the old motor frames (they have a small gearbox), because the old motor is 89x89mm and the Leadshine is 80x80mm. I hope it won’t be too difficult.
Once the machine is up and running and I’ve done some work with it, I can swap the spindle and install an automatic tool changer. That would be so cool!

Do you have any general advice? Does the setup look good to you guys?
By the way, I’ve installed the LinuxCNC ISO on an old PC with an Intel i5. Now I’m just waiting to buy the Mesa board and start configuring everything.

Thanks for the replies, but some misunderstanding here.
The system is fine, up and running LinuxCNC 2.9.3, configured for the X-axis with joint0 and joint1 as it should be (cutting a big slab of 5 mm Alu while I am typing this). The only thing I am adding is a racking detector (for which I use encoder_ratio looking for a mismatch on encoder disks on both X axis).

While browsing through the HAL functions I ran into Matrixkins, and I wondered if this is not an easier way than changing some HAL values to square the axes. Since it does not apply to a tandem axis, I'll drop the issue.
But thanks for the replies anyway.

Robert

I was thinking 2 motors that move opposite to one another and increase the effective distance (one moves left 5CM, the other moves 10cm right; total displacement is 15cm)

Yes.
When mounted inside, the encoder wires have to go inside, and those are the ones most susceptible to interference.

No need, since 2.8 the joint/axis is implemented in LinuxCNC, so just choose "tandem joint/axis" in the wizard.