Jump to content

Welcome to eMastercam

Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.

Use your display name or email address to sign in:

The IT Guy

Verified Members
  • Posts

    17
  • Joined

  • Last visited

Profile Information

  • Interests
    Making computers talk to machines

Uncategorized

  • Location
    Work

Recent Profile Visitors

603 profile views

The IT Guy's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. This is the memory card internal to the DataServer itself. If you open the cabinet and look at the DataServer, it's a little SoC with a CF Memory card stuck in it. This should be visible externally via FTP and that would be real quick and easy for you to prove out. Do it. You can DPRNT to the DataServer or to an External FTP server. The setup of both requires changing settings in multiple screens. The code to DPRNT a value from a variable looks like this: DPRNT[DATE=,*#3011[80]] DPRNT[TIME=,*#3012[60]] That will dump the current date and time, in CNC format, from the machine clock. Make sure the time on your CNC machine is set correctly. You can use these timestamps to calculate run time if you put them at the top and bottom of an operation you want to measure. There are many parameters that modify how DPRNT works. None of them are required. You have to look them up and make choices about how you want it to work. FANUC manual B-65270EN_07.pdf has all the stuff you need to know in it.
  2. Thanks for the offer and suggestion Matt. There is no way I can share any of our files. I understand that limitation makes it so you can't help directly.
  3. I have deployed computers with the latest CPU technology I could find today, the Intel i9 9900K. I participated in the benchmark thread to prove to my programmers that their computers are as fast as it gets today. Still I am hit with complaints that their legacy toolpaths take hours to complete on complex 5 axis operations. So much time is wasted waiting on MasterCAM. Is there anything that can be done? Is there some magical CPU that I don't know about that can handle the workload any faster? Can they use different toolpaths that are better optimized? (They tell me they have to use legacy toolpaths for this work) Are we just waiting on MasterCAM development to catch up with modern technology? I am expecting GPU accelerated math functions but it looks like they are still struggling with traditional multi-threading. Should we be using a different CAM software?
  4. pullo, the top link on the first post results in a 404 not found error. PKA is correct. We can't download it.
  5. Thanks for keeping this Benchmark going. It helped me show my engineers that our computers are good, it's MasterCAM that is slow. Here are some data points:
  6. I apologize for performing necromancy on this obviously dead thread. Ernie, When I copy the points out using Verisurf tools I get points in the global co-ordinate system regardless of what WCS I have selected. Is there any way to get the points to copy out relative to a selected WCS?
  7. I'm logged in and I get: Access Denied You do not have access to view this page within the website.
  8. Where is the manual for VeriSurf tools 2018? Just getting started with it
  9. Thanks guys! This thread sent me down the correct path. I couldn't find the security update cited by previous posters but I did get it handled. MY FIX: Install "Microsoft .NET Framework 4.7.1" Microsoft .NET Framework 4.7.1 (Offline Installer)
  10. Yes, I believe it was the start of the path. I am not looking at it anymore. He set it to a very small number and moved on but I'm not happy with a software that smashes the hard drive with temp files like this every time it has an error.
  11. Sorry, I mistyped. I meant to say when the Z clearance above a helix toolpath is set to zero. Not the helix itself. It can be set to a very small number but setting the clearance to zero causes some terrible error that MasterCam can't recover from. If it can't do it I do believe it should generate an error instead of filling the hard drive with temp files.
  12. I'm not sure if this is the correct forum for technical issues... Using the latest version of MasterCam 2017 we ran in to a strange bug. Normally, on this PC, regenerating a tool path is instantaneous. When setting the Z height of, the clearance plane above, a helix to zero the regenerate function hangs in an endless loop. If you let it run the Hard Drive slowly fills up until the computer crashes. The space is filled mostly by one file called "cut.tmp" in a local MasterCam cache directory. This one file is hundreds of gigabytes, limited only by the size of your partition. The folder name itself is gibberish. Has anyone seen runaway temp files like this before?
  13. Thanx, that is the kind of stuff I am looking for,
  14. I came to talk about what hardware configurations have the best performance in MCX3 and MCX4. Everyone knows that a good video card makes modeling much more smooth but what about generating toolpaths and posting etc? With extremely large, complex models we are experiencing slow number crunching time when generating toolpaths (6 mins or more per). The system is a Q6600 and X3 is only using one of it's cores. I thought memory might help but out of the 4 gigs in the system, only 2 are being used. With all that free memory I can't justify adding any more. If you have used MCX3 or 4 on many different computers I would like to know of any trends noticed. Or tell me how great it runs on your computer and give details about your hardware.

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us

×
×
  • Create New...