Skip to main content
A
afraser-21-Visitor
1-Visitor
February 8, 2016
Solved

CAD Worker Printed Representation different from Drawing in Creo

  • February 8, 2016
  • 4 replies
  • 3757 views

Hello all,

 

I'm having a hard time figuring out why the pdfs generated by the CAD worker on our Windchill Server are different from the drawings manually printed to pdf from creo. Mostly commonly dimensions are flipped about a center line, but sometimes leaders lines are incorrect, or even angular dimension move! One trick we've found is that if the sketch plane of a feature is perpendicular to the view plane it seems to cause this issue. That is if a feature is sketched on a SIDE plane, but then the dimensions are shown on a FRONT view then those dimensions will often "move" on the printed representation.

 

 

I've already gone through all the config files, pentables etc etc that I can think of... Everything is the same between the CAD worker and our standard CREO installs. Does anyone have any other ideas what might be causing this issue?

 

 

 

From Creo:

Example 1 - CREO.PNG

 

From the CAD worker/Creoview:

Example 1 - CADWORKER.PNG

 

Extra info: We're on Creo 2.0 M120, and Windchill 10.1 M040


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
Best answer by TomU

Questions.

  • Is the CAD worker running the same version of Creo?
  • Have you attempted to open this file directly on the CAD worker machine to see how it looks?  (See if the dimension moves.)
  • Do you have an identical (or at least very similar) config.pro and config.sup on the CAD worker?
  • I find it very interesting that the number of decimal places displayed for the secondary units changed for the 4.000 dimension.  Do you possibly have "auto_drawing_update all" present on your CAD worker?  (Not necessarily a problem, unless it's only on the CAD worker and not on your local computer.)
  • Do you have the recipe file set to regenerate drawings?  If you open the drawing and manually regenerate it, do you see these same changes?

4 replies

T
23-Emerald IV
TomU23-Emerald IVAnswer
23-Emerald IV
February 8, 2016

Questions.

  • Is the CAD worker running the same version of Creo?
  • Have you attempted to open this file directly on the CAD worker machine to see how it looks?  (See if the dimension moves.)
  • Do you have an identical (or at least very similar) config.pro and config.sup on the CAD worker?
  • I find it very interesting that the number of decimal places displayed for the secondary units changed for the 4.000 dimension.  Do you possibly have "auto_drawing_update all" present on your CAD worker?  (Not necessarily a problem, unless it's only on the CAD worker and not on your local computer.)
  • Do you have the recipe file set to regenerate drawings?  If you open the drawing and manually regenerate it, do you see these same changes?
A
afraser-21-VisitorAuthor
1-Visitor
February 8, 2016

Thank you Tom for your questions/troubleshooting suggestions!

  • Yes the CAD worker is also on Creo 2.0 M120.
  • No I haven't tried opening the drawing directly on the CAD worker machine, but that's a good idea. I will probably have to enlist some outside help on doing that though as I believe it's hosted on a VM on the same server as our Windchill installation... And all that is a little outside of my knowhow and corporate permissions.
  • Yes working with our service provider, he's confirmed that we have the exact same config.pro files for the CAD worker as our regular users. We don't use a config.sup so that shouldn't be the issue. (although I guess I should double check there isn't a config.sup on the CAD worker).
  • No we aren't running the auto_drawing_update option. This was the only drawing we ever had where the decimal precision changed... We've since copied over all the config files, and haven't seen that issue since. The moving dimensions though we still see regularly.
  • I have no idea about anything in our recipe file ... I will pass on that thought to our service provider.


B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
February 8, 2016

In addition to what Tom is asking:

  • Are you using Quick print to PDF on your Creo machine for your PDFs? I have found that this changes things from what I plot from Creo and what publishes.
  • Are you using Save As and changing the file type to PDF for your Creo PDF files? You need to change to stroked fonts to duplicate the PDF from the publisher.
  • Are you using TrueType fonts or PTC fonts?
A
afraser-21-VisitorAuthor
1-Visitor
February 8, 2016

Thank you Ben for your questions/troubleshooting suggestions!


  • I don't know about the quick print to PDF... I will investigate that.
  • I don't fully understand your question... Normally I use the export to pdf feature from Creo to create pdfs of the drawings. (and therein I always have the stroke all fonts setting selected).
  • We're using PTC fonts, but we always stroke said fonts on exporting.

T
23-Emerald IV
TomU23-Emerald IV
23-Emerald IV
February 9, 2016

I just saw this come through from PTC.  Not sure if it's related to your case or not.

CS229017

A
afraser-21-VisitorAuthor
1-Visitor
February 9, 2016

Thank you for pointing that out! Hmm... It certainly sounds like my issue, but it's on the wrong version of Creo.

We can try the resolution though and see what happens.

A
afraser-21-VisitorAuthor
1-Visitor
February 11, 2016

Well I feel silly, the CAD worker was running Creo 2.0 M060.

Our maintenance provider has been assuring us for months that we were on the same version, but after I finally got login credentials myself to check lo and behold it's on an older version.

Thank you both very  much for your help Tom Uminn‌ & Ben Loosli‌ for your time helping out!

Terms & ConditionsAccessibility statement