Centroid Community CNC Support Forum

I'm used to Heidenhain and would like to have an industry standard if I have to pay for it. There are errors in the calculation in the Probeapp. I prefer to use the Centroid function. A clearly defined structure is an advantage, especially under time pressure.

Houseman303 wrote: ↑Tue Aug 27, 2024 1:41 am Screenshot_2024-08-27-07-36-20-41_e2d5b3f32b79de1d45acd1fad96fbb0f.jpgScreenshot_2024-08-27-07-35-59-27_e2d5b3f32b79de1d45acd1fad96fbb0f.jpg

I'm used to Heidenhain and would like to have an industry standard if I have to pay for it. There are errors in the calculation in the Probeapp. I prefer to use the Centroid function. A clearly defined structure is an advantage, especially under time pressure.

The graphics in ProbeApp and CHIPS are based on the ones from CNC12 and they are all based on industry standard.

I value critical feedback as it makes the product better and many features have been added to CHIPS on users feedback. It’s a general wisdom that the chances to get something are much higher if you ask nicely. Demanding something because a product is not free is not very convincing, especially if nobody else has asked for the same thing in over several years.

Also in rare occasions where a real bug has been reported, the bug was usually fixed within a day or two.

What I don’t appreciate are the people who come here bad mouthing my products having errors that they never bothered to report and don’t bring any proof.

-swissi

I am a professional CNC-User on multiaxis machines for decades with Traub, Siemens, Fanuc and Mazak controls (Traub and Mazak are based on Mitsubishi)

There is no industry standard except for ISO 6983‑1, beyond this anyone is cooking its own soup

I use Centroid and CHIPS for my hobby, but I often whish the CNCs on my job would be as efficient and easy to use

Uwe

When I criticized the touching of individual axes because the measuring probe remained switched on the component, the only excuse was that others wanted it that way.

Houseman303 wrote: ↑Mon Sep 16, 2024 5:08 am When I criticized the touching of individual axes because the measuring probe remained switched on the component, the only excuse was that others wanted it that way.

That’s not really what you said in your last post. You made a defaming statement with the exact words "There are errors in the calculation in the Probeapp” without bringing any details or facts.

In the name of the hundreds of ProbeApp and CHIPS users, we would like to know what error you found that we haven’t noticed yet so it can be fixed in the interest of the community.

Regarding the behavior of the single axis probing moves keeping the probe in the tripped state, there are no excuses, only the fact why I have done it this way.

Unlike the CNC12 built-in Single Axis probing moves, the ProbeApp/CHIPS probing moves allow to do a WCS axis reset after the probing move. With the default configuration settings, the probe will move until it reaches the trip state. It will then show the trip coordinates and ask if the axis should be reset at this position. After the messages have been confirmed, the axis will reverse by the amount of the configured probing recovery distance to take the probe out of the trip state at the end of the probing cycle.

So the real reason the probe is being kept at the exact trip point is to allow the axis WCS reset to occur at the exact trip position without the introduction of any axis backlash error.

For those who just want an axis to be reset without being bothered by messages, the messages can be turned off in the App General Settings.

-swissi

Hello All,
I wanted to add a tip of the hat for this great addition to an already great product. I am two years into this journey updating my Bridgeport Boss to current controls and most recently added CHIPS to the system. I had bumps in the road getting to here but Swissi was patient and walked me through my troubles. The work flow and simplicity of use of the CNC Mill now is very close to what I had imagined when I started. Running G Code, automatically measures tools not in the library (drill bits), working with Touch Probe and tool touch off just like current tools by major manufacturers. If you are like I was sitting on the fence with Swissi's prior product(s), get past it, his price is very reasonable for the features and functions provided.

Regards,
PFM Dave

After checking all probing in Centroid (spindle probe, tool touch off and xyz touch plate) successfully and then installing CHIPS, mfunc6.mac wasn't generated.
I'm assuming just copying the mode 3 template over to mfunc6 works?
My other issue is probing with the spindle touch probe doesn't work like it does in the default probing in Centroid. In Centroid, it sees the touch probe tripping, stops and either backs up and goes again slower, or goes the other way (depending on where in the cycle). In Chips, it sees the probe trip and keeps on keeping on. I have new stylus' on the way... Chips reacts when I trigger the touch plate.
Any advice?

mobilemcclintic wrote: ↑Thu Jan 09, 2025 12:39 am After checking all probing in Centroid (spindle probe, tool touch off and xyz touch plate) successfully and then installing CHIPS, mfunc6.mac wasn't generated.
I'm assuming just copying the mode 3 template over to mfunc6 works?
My other issue is probing with the spindle touch probe doesn't work like it does in the default probing in Centroid. In Centroid, it sees the touch probe tripping, stops and either backs up and goes again slower, or goes the other way (depending on where in the cycle). In Chips, it sees the probe trip and keeps on keeping on. I have new stylus' on the way... Chips reacts when I trigger the touch plate.
Any advice?

Let's start with the missing mfunc6.mac macro. When you select the CHIPS Operation Mode, CHIPS will place the matching mfunc6.mac macro in to the C:\cncm folder unless there's already one there in which case you will get the option to backup the existing one and copy the CHIPS one in place. That's a pretty solid process and I've never seen that fail before so I'm pretty sure the mfunc6.mac was in place after you selected the CHIPS Operation Mode. What happened in your case is a CNC12 issue that many users don't seem to be aware of. If you don't select the option in the CNC12 Wizard that your system has a customized mfunc6.mac tool change macro, the Wizard will delete any existing macro every time you run the CNC12 Wizard. So check that CNC12 Wizard setting accordingly. Looking at your report file, there's the correct M6 tool change macro in place.

Regarding the touch probe issue, I can assure you that when a probe works properly in CNC12, it does work in CHIPS too. Looking at your report file, your TP is on input 6 and does not have a Detect Input configured. What's the make and model of your TP and is it of type NO (trips when it closes) or NC (trips when it opens)? Also post a copy of the CHIPS configuration file (C:\cncm\CHIPS\CHIPS.cfg) so I can verify your configuration.

-swissi

Hi Swissi.
I have 3 different installations backed up. 2 of them have CHIPS installed. I started over from scratch after bending my probe's stylus figuring the process of upgrading 4.8 to 5.2 and replicating settings possibly messed something up.

None of them had mfunc6.mac until I copied your template file as mfunc6. I did select Mode 3.
The probe is normally open (24V when untriggered on signal, 0V when triggered). It works as expected using default probing cycles in CNC12.
It is a generic powered 3d finder with indicator light, model TP05C.
I will check the wizard setting the customized Tool change macro and provide the CHIPS config file when i get home tonight. I appreciate your help.

swissi wrote: ↑Thu Jan 09, 2025 11:08 am
Let's start with the missing mfunc6.mac macro. When you select the CHIPS Operation Mode, CHIPS will place the matching mfunc6.mac macro in to the C:\cncm folder unless there's already one there in which case you will get the option to backup the existing one and copy the CHIPS one in place. That's a pretty solid process and I've never seen that fail before so I'm pretty sure the mfunc6.mac was in place after you selected the CHIPS Operation Mode. What happened in your case is a CNC12 issue that many users don't seem to be aware of. If you don't select the option in the CNC12 Wizard that your system has a customized mfunc6.mac tool change macro, the Wizard will delete any existing macro every time you run the CNC12 Wizard. So check that CNC12 Wizard setting accordingly. Looking at your report file, there's the correct M6 tool change macro in place.

Regarding the touch probe issue, I can assure you that when a probe works properly in CNC12, it does work in CHIPS too. Looking at your report file, your TP is on input 6 and does not have a Detect Input configured. What's the make and model of your TP and is it of type NO (trips when it closes) or NC (trips when it opens)? Also post a copy of the CHIPS configuration file (C:\cncm\CHIPS\CHIPS.cfg) so I can verify your configuration.

-swissi

Hi Swissi,
I went into the Centroid wizard and told it I was using a custom tool change macro.
Then I went into Chip settings and re selected mode 3. This time it said I had a mfunc6 macro and asked about replacing it. I let it replace it with the new copy of the same file.
I tested again, and in CNC 12 default cycles, I can use the probe and it works. It stops when triggered and measures as expected. In Chips, the status box shows the probe tripped, but whatever operation (single axis, bore calibration, it doesn't matter) just keeps on moving until I trigger either the touch plate or the tool touch off, wherein it stops, backs up, probes again, then if a slot or bore, goes the opposite direction. Attached is my Chips config. I see T10 says "no probing" in the config file, but I don't see anywhere to set it in the interface. There's a screenshot of it in the manual, but that is in operation mode 1.