Schaublin 125-CNC retrofit.

Thanks guys. I will see if I find time to try a 2.9.8 install on a second drive (I have an SSD laying around awaiting that I do the same task on the Maho, which is still on 2.7). I am not using any Python or glade code, other than Andy's Lathe Macros.

I might start off trying to halcompile the most current version of carousel.comp
Cheers,
Mark

Trylobite sent me a mail which really helped me understand the difference between the original Schaublin turret control, as mine still is, and the mods he made.He replaced the hall sensors with microswitches, which activate once the turret rotates into position. He uses that to signal closing the pneumatic tool change valve, dropping the turret to lock.

Since my Hall sensors do not read high until after the turret drops, bringing the magnet into proximity, I can't use the switches for valve control.

I initially thought it would simply step through, one pocket at time, till the correct feedback sensor goes high. I started writing the attached draft HAL to include a second pause for the pressure to bleed off, dropping the turret onto the hall sensor. But carousel.comp step through pockets like that does it?

Using Carousel.comp, how do make it cycle three times, if it is in pocket #2, to get to pocket #1, verses only moving once to get to #3?

Trilobyte also pointed out that the carousel will keep cycling from one position to the next continually, as long as the pneumatic valve is held open. There is a delay of a few seconds at each position, which appears to be controlled by adjustable restricters in the valving. With those pauses, controlling  the pneumatic valve open loop with simple timing seems feasible. 

I guess I can have it calculate the modula number of pockets to the destination when a change is commanded.
If if measure the time for lift and turn, and the time of pauses, and setp the three delay times whether 1, 2 or 3 pocket moves are needed.
Then by holding the valve open for the appropriate time, it will turn the correct number of pockets.

Any suggestions how to easily make the carousel.comp step through till the desired pin goes high also appreciated.
Cheers,
Mark

RotarySMP wrote:

Any suggestions how to easily make the carousel.comp step through till the desired pin goes high also appreciated.
Cheers,
Mark

Remove the stationary magnet from the cover thing, and replace it with a spring-loaded magnet which remains in contact with the halls as the upper section rises and falls.  The halls will now get positional feedback when the turret is up or down, and carousel will keep the motor-fwd signal high until the appropriate hall sensor is triggered.

Doesn't look like there's any reason you couldn't just 3d print the top cover with appropriate mods for a captive, sliding, spring-loaded magnet.  I'd probably make an aluminum or brass 'carrier' tube for the magnet that presses in to the printed part so the magnet isn't sloppy but also doesn't get hung up on print layer lines.

I don't think I remember seeing another sensor to indicate the turret is down and locked, but as soon as carousel.comp turns off the motor-fwd output it should drop.  You will likely need to play with the hall alignment (or the top hat alignment, to be precise) to make sure carousel.comp doesn't drop the motor signal too quickly or too late to engage the alignment pin(s).

Above should let you eliminate the 'tp' component in your HAL example and just let carousel.comp treat your pneumatic system like a unidirectional motor.

And another thing...

The existing trigger magnet is a really old ceramic magnet.  You could potentially use a newer, much smaller, neodymium magnet with a square shape to get a cleaner rising edge from the hall sensors.

Or stick with a round one and fiddle with the alignment and possibly carousel.comp's decel-time setting.

That forty year old hall sensor module is already cracking, no way I will risk mechanical contact with it.

RotarySMP wrote:

That forty year old hall sensor module is already cracking, no way I will risk mechanical contact with it.

More powerful magnets may trigger the halls even with a bit of distance.  Try triggering them with a good (N50) neodymium magnet and see how much spacing you can get away with.  You might be able to stay with a fixed magnet and nothing touching the fragile hall ring.

If they need to be closer than the fixed position allows, you could cut a protective surface out of plastic sheet, glue it to the sensor ring, and let the magnet rest on that instead of the halls.  Basically reinforce the hall ring - which it probably needs anyway - and let the reinforcement take the wear.

With a light spring there shouldn't be any real up/down impact forces on the hall ring... just the magnet sliding along.

Mark, this is the solution you end up with, you need execution blocking for the tool changer hal component. here is my program, if you need my email address let me know. 

Hi Andy,

I got the Schaublin updated to Trixie and 2.9.8.

I really like the update you did to the look and button layout of Lathe macros. Thanks.

I was trying to work out how to address not having any feedback on the turret arriving in position. Because I am a shit programmer, I tried Chat GPT yesterday.

 

This is the set of requirements I gave:

 

The AI summary is rather accurate.

 

 

After a couple of back and forth, adding requirements, and accepting some AI suggestions, the result is the attached files.
Scary good how fast and efficient this is for a small project with very limited requirements, and how well it documents and explains the code. It would have taken me a few evening to get to this level, and my code would have been a mess of half-arsed work-around to avoid the gaping holes in my programming knowledge.

It failed to compile yesterday, due to some unknown character. I suspect the apple text editor has added some hidden ascii code. The attached files I cut paste into a different text editor. Off to test them now.
Cheers,
Mark