I use LibreOffice Draw to edit pdf setup sheets created with Active Reports.

I save them as PDF's with the Cute PDF printer driver.

Honestly, I'd start with the Active Reports Tutorials. This should be available from your Reseller... That would get you a long ways towards doing the customization. You can certainly contact Jim and see if he offers training...

I used to be an X+ user until I sat down and hammered out a decent active reports setup sheet. Haven't looked back since.

I use exclusively X+ for over 10 years i tried other but X+ is always better

It *should* be 1x click and easily editable...

Depending on the customer's preferences, I use two different methods. Method 1 I use a "Dot Set File". (MILL.SET) This is essentially a modified Post Processor, that is setup to generate a Text Report. Since it is a Post Processor at it's heart, you can get any data you want from any of the Operations. The main reason I go with a .SET file, is because I can modify my regular NC Code Post Processor, to launch the .SET file automatically in the 'ppost$' Post Block. I pass the NCI file that I just finished processing to generate the NC File, and mine the NCI for the data I need in my setup sheet. The advantage here is that I get a perfect setup sheet, any time I post a new NC File. The process is 100% automatic, so I never have to worry about "Did I, or another Programmer, forget to generate a new setup sheet when I tweaked that RPM for the Tap? The only disadvantage with the DOT SET method, is you can't generate the pictures automatically. You have to do that manually if you want pictures with the Setup Sheet. Method 2 Jim Varco is a former Post Developer, who worked for a Reseller (I believe, if I remember my history correctly!) Jim really embraced the Active Reports, and learned how to customize the software to make the setup sheet automatic, grab any information you want from the Mastercam File, and also automate the generation of Pictures of the Setup, Operation Info, and Tool List info. He does a fantastic job of customizing the reports to give you exactly the information you need, and the price he charges is a bargain, for the value you get. http://varcoreporting.com/ If you want a cost effective, slick solution, I'd go with Varco Reporting all day, every day. This is money well spent. (Again, the price is cheap for what you get...)

perfectly normal we've got a whole bunch of very talented people hanging out here and we've got a bunch of goof balls too. We've even got talented goof balls Welcome to the forum... hope you'll stick around

I had an hour session with it a week ago and the results were so weird ( read unusable) that I ditched the whole idea . I went back to my old style , surface contour and old school shallow set at 10 degrees , with the size of the tool in shallow 0.3 mm larger that in reality. Gracjan

This is what appears to have done the trick. Haas updated the software today and, so far everything is working smoothly.

Members 3 6 posts Report post Posted March 7 We too have a Haas umc 750 and a Postability Post. Ours comes up with error codes 2.103 y axis servo error too large , 9971 excessive axis speed or acceleration , 949 internal feed error detected. The machine just stops, right after gouging my part, started doing it when I first started doing 5 axis simultaneous machining now it is doing it on simple surfacing. It has ruined (5) , 3500.00 parts in the last 2 weeks. Haas finally fessed up to the fact that they have a software issue and are going to up grade the software some day soon I hope .I would double check the WRZP numbers as I don't see any 12" numbers in the code you have posted It could be the software with yours as well. Good luck! Quote

As bad as I hate to throw this out there, I have had to do it. You can set an offset for every rotation and sneak up on it. I used an Excel spreadsheet to trig out the deviations and then plugged the data in a file I had a ton of G10s in. It got me close but if there was anything tight or critical I always snuck up on it. Let them see the cost of that for a few months vs just having the machine dialed in. You can likely get the procedure from the manufacturer to find center yourself. If not, get them in, watch and take notes. Then you can do it.

Hey Rich This is a prime example (to me) where some shortcuts make nooooooooooo sense. Whys isn't that R or D...

I underlined the important part. Are you saying that the same program will run without fault on either of the other two machines? Are you running with TCP and DWO? (G243 and G254) I've seen some very funky things on these machines, depending on the vintage (build date) of the particular machine. Keep in mind that the UMC-750's are Haas' first attempts at using more advanced software functions in their controls. From what I've personally witnessed, I believe that whoever is telling you that you need G93 is simply trying to pass the buck, since they themselves are incapable of solving your issue (and likely don't want to admit that they don't know how to properly solve the issue). I would highly recommend that you get someone (capable) at Haas to come in and tune the drives on all 5 axes of this machine. (Even though it seems to be the X-Axis only that is causing your issues...) My hunch is purely based on anecdotal evidence, but allow me to describe the situation I personally encountered: Back in 2008, or 2009 (can't remember the exact dates), I was helping the local Reseller in WA with a project on a brand new Haas VF-4 SS, with a TR-160 Trunnion table. I programmed and setup the job, and attempted to run it on the machine. This was a demo part, and was an attempt to show off some of the new High Efficiency Machining paths to some programmers at Boeing Auburn. When the program got to the section of "live 5-Axis" cutting, the drives on the Trunnion started stuttering, and shaking during the cut. Not only was the finish really bad, but I could tell that something was waaaay off at the machine level. I was unable to get the machine to run above about 20 IPM, without it trying to shake itself to pieces. Even when cutting very slowly, the path was faceting and leaving small gouges in the wall I was cutting. I got on the phone to Haas, and they sent out a AE to tune the rotary drives. Well, the first guy they sent wasn't very experienced, and while some improvements were made, the results were still very poor. I made a couple more calls, and felt like I was getting the runaround. After finally getting on the phone with the sales guy, and telling him in no uncertain terms that we would be sending the machine back if this didn't get fixed, they finally flew in someone from the headquarters in California to work on the machine. It took him about 30 seconds of watching it run to diagnose the issue as "improperly tuned rotary axis dive units", and he proceeded to change about 40 different parameters on the control. I didn't catch the entire description of what he had changed (I walked in on the middle of a conversation between him and the Reseller), but the gist of it was the feedback loop between the drives and the controller were set too tightly, along with the accel/decel parameters not being opened up enough. Once he finished tuning the drives, I was able to bump the feedrate up to about 150 IPM, and the machine ran the cut as smooth as silk. For purposes of this anecdote, we were running the machine in G93 mode (Inverse Time), so my "20 Inches per minute" and "150 Inches per minute" were the G93 equivalents of those feeds. Now, it is possible that running your machines in G93 mode would help, with the live-five portion of the program, but if the machine is also getting errors on the 3+2 motion, then G93 will not have any effect on fixing that error whatsoever! So, between my past history with having tuning problems with Haas machine axes, and the fact that you are getting errors when the rotary axes aren't even active in the cut, that leads me to believe that someone is trying to CYA and blow smoke up your butt. I would be on the phone, and making sure they pass you up the chain of command at Haas, until you can get to someone with enough authority to fix your problem. I believe the solution lies in having someone come and tune your machine properly, and/or install a newer version of the Control Software. The hardest issue with solving this problem will be that it is intermittent. You can't just run the program until it hits "block 2205", for example, and say "see, there is the alarm, fix it!". So that makes it a difficult problem to solve for any technician who hasn't dealt with tuning the drive motors before. Whenever you call for service on a machine (no matter the model or builder), the service department will always attempt to send the least costly technician (for them), to attempt to fix the problem. The issue you are facing won't be solved by a greenhorn. You'll need a Senior AE, or the equivalent to come fix this issue. If pleading doesn't work, get on the phone with the Sales Guy who sold you these machines, and tell him you are going to return all of them for being defective, and are going to replace them with Mazaks or Okumas (whomever they compete with the most, in your particular area), if this issue isn't fixed. Tell him this issue has caused your boss to go nuclear and that you need this solved within 2 weeks, or the riggers will be dropping the machines off at the Haas showroom floor. I literally had to use a similar threat to get my issue solved a decade ago...

There's a DX32 post on Mastercam's tech exchange.