Advanced Search

hi all 
im new here and i'm currently in school (mechanical engineering), we're making an plasma table for this semester project. as of right now we're almost done and during some test on it tho we cant figure out how to disable the probe when we start an test, we have made our setup so that it hits the material on the table and makes that the home, and then in the materials we have told it what hights it should cut it, so we dont need the probe, also atm. we dont have the waterbed on the table yet so we're trying to make the test up in the air.

 

We are just finishing up our linuxcnc retrofit with Probe Basic on our Mazak VTC16B. Everything seems to work just fine, except we are having an issue with the controller not keeping track of the current pocket number (Parameter #3990). The machine has a 24 position index style carousel ATC. It indexes correctly and on the first try after indexing, it will grab or store the appropriate tool in the appropriate pocket using M6 commands. After the first toolchange though, it's almost as if the controller resets itself as starting from Pocket 1. The GUI shows the correct pocket that is supposed to be used. 

For example, if we start with Tool 3 in our spindle, Pocket 3 empty, Tools 2 & 3 in pockets 2&3; just after indexing if we store Tool 3 in carousel, it will rotate to pocket 3 and store the tool. If we then run a M6 T2, instead of rotating -1 pocket to grab T2, it will rotate +1 pocket, as if it were starting back at pocket 1. When doing this, the GUI shows pocket 3 being the active pocket and rotating +1 to pocket 4.

I'm assuming it has something to do with parameter 3990 not being updated or called out properly. We had to make some changes to the default config to make it all work with our machine. I've attached some of the proper config files, would somebody be able to provide any insight on where to start diagnosing this?

Okay, well I don't _completely_ understand, but...

There's a competition going on between the M6 command, and the M3 that happens just before it. If I reverse the order, to "M6 M3", then all is fine.

And the answer probably lies in my quirky handling of M3.

I run my machine from an RPi. As I've written elsewhere, spindle_enable is connected to a Pi GPIO output pin. That output pin is connected directly to a Pi input pin. I have a script in which gpiomon watches that pin, and starts and stops the spindle based on its transitions. It handles stop pretty directly. But when starting, it first drops the atspeed signal, then puts up a dialog asking me if it's okay to start the spindle. If I cancel, it runs "halcmd setp halui.machine.off false" to shut things off. If I hit okay, it activates the smart plug, and a couple of seconds later enables at-speed, using "halcmd sets spindle-at-speed true". I know that all sounds like a lot of chewing gum and string, but I like being explicitly asked whether I want the spindle that's about a foot away from my face to start up. (I also like it turning off automatically at the end of the job.)

Anyway... somewhere in there, if the M6 follows the M3, the spindle goes off after being turned on. It's complicated further because at-speed doesn't fully pause the program -- it will keep running until it hits a G1. So the M6 happens while at-speed is low.

It's now making my brain hurt a little. I'll just be sure there are no M6 commands in my g-code from now on.

I started github.com/JTrantow/LightBurn_to_LinuxCNC. Currently it just sketches out the idea. No code added yet.
I can add you as a Github collaborator.
 

Oh! (replying to myself)

Reading the source for hal_manualtoolchange, I see that it's also his window is part of the AXIS manual toolchanger.the program responsible for the "This window is part of the AXIS manual toolchanger." window that shows up when I start Axis. I hadn't made the connection before. Lately that window has been appearing mostly off-screen, in a way that I can't read it. Since I always ignore it, I didn't worry about it. But now I wonder if whatever is causing that is also messing with the confirmation dialog somehow.

Clearly something to investigate.

paul

I broke a brand new (happily inexpensive!) bit today.  Right after program start, the spindle shut down, and the work kept going.  I hit E-stop, but not in time.

The culprit was code generated by kirimoto, which contained an M6 for an initial tool change.  I missed it when configuring kirimoto -- that M6 shouldn't have been there -- but even so, it should have paused.

It's reproducible -- M6 shuts down the spindle, but the program keeps going.

I use hal_manualtoolchange, set up pretty much by the book:
The only mention of tools in the .ini is "TOOL_TABLE = tool.tbl" in EMCIO.

I ran halshow, watching the hal_manualtoolchange pins, and the ioctrontrol tool-* pins.  The iocontrol.0.tool-prepare/prepared loopback flashes on briefly when I hit M6, but that's the only change I can see.  (I didn't use halscope.)

Any ideas?  Am I missing some config?
 

Got the right color RAL6011 
 

Here's a video of adding images to pushbuttons should be similar for labels.



JT

Any Government that supports / allows Windows OS and especially it's servers in there country.

What government??

When I write a reply I always tick the box “check this box to be notified of replies to this topic”, but I just don’t get any emails.

The Windows 11 slogan should be " We aren't spying for the Government honest." 

60000 packets transmitted, 59992 received, +8 errors, 0.0133333% packet loss, time 60099ms
rtt min/avg/max/mdev = 0.048/0.133/6.074/0.075 ms, pipe 9

Not good

What host hardware do you have (CPU and Ethernet chip)?
 

rodw wrote:

You have to subscribe. Its not automatic

It was for any topic you replied to or started. And you could subscribe to any topic manually.
No idea if that is the case now as i get e-mails for every post.

snowgoer540 wrote:

Ok. Guess if they work for you they work for everyone.

I did not say that.