Grip: 3 periods added to front of output files... why? 2

[Shadowspawn]

NX6.0.3.6 on Windows XP (32 and 64 bit machines)

Here's a new one... existing grip routines that have run fine previously are now having 3 periods added to the front of the output file names. We now have to manually remove the dots from the output file names when finished.

Subroutines that depend on output generated fine as well; grip seems to expect the dots in the file name so the routines continue ok... but the dots remain. The biggest issue is that other type programs (non-grip) depend on grip output... these programs don't expect the dots so they fail.

I suspect an env variable of somesort... but that's just a WAG. Has anyone encountered this or something similar?

AFAIK, there have been no changes to our NX environment that has coincided with this issue. Any help would be appreciated!



Regards,
SS

CAD should pay for itself, shouldn't it?

 

[Shadowspawn]

Problem apparently resolved.... apparently the ugpath env variable had 3 dots after the last slash that was getting picked up by the routines and added as part of the file name(s).

I've gotten new machines for my guys recently (last couple of months), and when setting them up the env variable on each machine was set wrong by the IT guys.

Is there a way to give myself a star?

Regards,
SS

CAD should pay for itself, shouldn't it?

 

[JohnRBaker]

Are these files being 'output' by your GRIP program text files or what? And in what version of NX do they still run as you expected them to?

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[JohnRBaker]

NO, but I will ;-)

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[jerry1423]

Oh heck, It's Christmas, I'll give you one too

 

[Shadowspawn]

The files output are typically txt files; outputting x/y/z pt info for CMM comparison, spline def points, converting customer supplied airfoil def to our standards, etc.

As far as the version of NX that they still run as expected; Since I've upgraded several machines lately, I decided not to load any version prior to NX 6 and didn't think to check machines that weren't replaced.

Regards,
SS

CAD should pay for itself, shouldn't it?

 

[JohnRBaker]

I just ran, using NX 6.0, a old GRIP program which creates a text file and it worked fine (no extra ...'s), so I guess we can assume that it was the result of the poor entry on the environment variable. Note that I did not try changing this on my system to see if I could reproduce the behavior which you saw, but if you've gotten it straightened-out, I guess we can just move on, OK?

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[Shadowspawn]

Very OK! Thanks for the responses and stars guys... & I wish everyone a very Merry Christmas!

Regards,
SS

CAD should pay for itself, shouldn't it?