No sir.

It sounds like to avoid this issue in the future, using decimals is the way to go. I just wish I knew why this was happening, as this program has a couple thousand of the "IF [#6 EQ 79] GOTO 41" checking for different values, so adding decimals will become quite a task. I also only see this rounding issue with certain numbers, which is even more mystifying. For those asking, this is a Mori Seki with a MAPPS IV control.

I have some macro code that is not behaving as I expect: N1 G65 P1501 K079 H00 A011 N2 #6 = [#6 * 10000] N3 IF [#6 EQ 79] GOTO 41 Line N1 sets #6 to 0.0079 Line N2 changes #6 to 79.000 which I visually confirmed. The program carries straight past N3 and errors out, when this line should be redirecting it to N41 I fixed this by changing N2 as follows: N2 #6 = ROUND[#6 * 10000] When looking at the value of #6 visually, the value appears the same as without the ROUND function, so does anybody know what is happening here?

Bumping this again. I need to export a .CSV file in order to import my mastercam libraries into ProShop

We are currently transitioning over to Proshop, and so far, I like what I see. The Mastercam integration looks promising, and I LOVE the idea of going paperless. Our prior system was MieTrak, which I would avoid at all costs.

Sheesh! Thank you!!

This just started happening. Doesn't happen in all files, only in some. When I left mouse click on an operation, it will select a whole bunch of operations instead of just the one. I could have multiple program groups, and it may or may not select operations in multiple groups. In one file, one operation group works as normal, but another is just impossible to select a single operation. I attached a small video showing it in action. Does anyone know what is going on here?!? toolpath_manager.mp4

I've noticed this seems to happen more regularly when I have more than one Mastercam instance open.

I've encountered this before, and as far as I can tell it is a bug. I have only seen this problem when using rectangular solids as stock, and then, it only occurs occasionally with certain files. What I have done for a workaround was to add a small .0005" chamfer to my solid, then it would come into verify properly. Not sure what I would do if I encountered this on an STL

I have had this happen as well. Configs are saved locally, no multiple instances running to explain things. Just cam in one morning and my toolbar and right click customisations were gone. Luckily I had already backed them up.

I did both of these, and still have the same warning. Strangely, the verification carries on perfectly fine anyways.

Did anyone ever figure out anything with this? Seeing the same issue after migrating from 2017 to 2020

Check to see if there is anything under the canned text section

The guys at Fanuc helped me. 3404 bit 0

Does anyone know if there is a parameter I can change so that single block will also step through comments? Thanks