After following the long installation process to the letter. I am struggling to wrap my head around the operation and there seems to be no videos on this specifically.
I can run the tool change test fine. But when I load a real job i constantly get the “Sub-programe file not found” error.
I have read the other messages regarding this and have moved all the sub-programs to my main folder along with the actual program, I have even also done the reverse and moved the job to the sub-routines folder just in case and in both instances still get the same error.
I am running Onefinity Masso RapidChange ATC Arc (mm) post processor and have made no modifications to this file.
Having successfully run the test file means the hard part is behind you.
The error you are getting will likely be due to the numbering of the tools, and making sure you regenerate and use the new subroutines after modifying tools/numbers. That is where I would start.
As suggested by 1F, Don at RapidChange will get you up and running, and like 1F support, he works 24/7
Don from Rapid Change was amazingly helpful in solving the issue which was down to the fact that one of my tools had a higher number and wasn’t defined in Rapid change tools database. Once added it also solved the can’t find file issue as the tool file for that tool number was also now visible.
I’m getting the same error, but it does not involve the ATC. I have put all the sub programs in the same folder but the main program is what gives the errors. I can bring up the subs with no problem, but the main will not load. what could be wrong in the main program that produces that error?
When I load the main file, I get an error message that says “Error-sub program not found” in red letters., and the screen is blank, not showing any tool path. I can go to edit, and the code appears. I can load any of the sub programs, and they will show a tool path.
Yes, all the files are in the same folder. I even tried putting them at the bottom of the main file with no avail. It has to be something in the main program that jams things up.
It is most likely a tool numbering issue/mismatch.
Check very carefully that the tool numbers that your main file will call, match those you have set up in both Masso and the WebUI, or Masso Rapidchange ATC if using that setup.