General Motors - DCS compliance problem

[kumarm2]

HI,
We are one of the Vendor to GM supplier.
I have problem while running DCS compliance.

DCS compliance is prerequisite as per GM standard.

I have used UGNX2 with same GM file checker(DCS compliance). It is working fine. But when i installed UG NX3. It is giving the below error message,

---------------------------------------------------------------------------------
***** MISCELLANEOUS NX AND UFUNC ENVIRONMENT ERRORS *****

ERROR NO. 1102: Could not validate the site_optional_refset file.
Reference set name: MODEL
Check that the site_optional_file is readable and correctly formatted.
----------------------------------------------------------------------------------

To fix this error i have tried several optons but i could not solve it.

Please give me some solution to resolve this issue?

Some members in this forum might be overcome the above mentioned problem.

Please help me out. I need to resolve this issue ASAP.

Thanks in advance.

 

[fgbrender]

Looks like the NX3 install changed your settings. You need to ad Model to your site optional reference set list.

 

[kumarm2]

Thanks fgbrender.


Welcome other people suggestions.

Please post your reply.

Thanks in advance.

 

[fgbrender]

Ok, a couple of questions...

Are you using Teamcenter?

What have you already tried?

Did you get the latest version of GMPDL for NX3?

 

[Xwheelguy]

Based on my own personal experiences with the Toolkit, I'd venture to guess that one of two things has happened:

1. There is an actual file that lists the names of site optional reference sets and the file was over-written or not copy/pasted during the toolkit upgrade (from NX2 to NX3).

2. The environment variable for site_optional_refset file has not been defined since upgrading to the NX3 toolkit.

I'd suggest combing through the installation directory of the toolkit and looking for a particular file for situation #1 above and/or looking at gmlaunch.bat, gmlaunch.dat or any other toolkit specific files that contain default settings.

If you can live without the MODEL reference set, then just delete it.

If not and you still can't find the problem, call the GM helpdesk for support. Their phone number is listed on gmsupplypower.com.

Tim Flater
Senior Designer
Enkei America, Inc.

http://www.enkei.com

 

[Xwheelguy]

Also, as fgbrander pointed out, you cannot use the NX2 toolkit with NX3...you have to upgrade the toolkit when you upgrade NX...unless GM specifies otherwise.

Tim Flater
Senior Designer
Enkei America, Inc.

http://www.enkei.com

 

[fgbrender]

I've spent many years working with GM's Data Creation Standards. As a matter I was part of the DCS team. As nkwheelguy pointed out, you may be able to delete the Model reference set but it will come back.

Now with that said, the error you are recieving means that the file that lists site defined reference sets is either read only or it does not exist. Have your site admin check the permissions on the file.

Also, make sure you have the GMPDL that was updated for NX3.

 

[Xwheelguy]

Straight from the toolkit documentation:

Error No. 1102: Could not validate the reference set.

Reference set name: XXXX

Check that the site_optional_file is readable and correctly formatted. Where ‘XXX’ is the reference set name.

Cause: Could not open the site_optional_file to validate named refset.

Solution: Validate that the site_optional_file in $FILE_CHECK_SITE_REFS is readable and correctly formatted. Where FILE_CHECK_SITE_REFS is an environment variable. Refer to File Checker Requirements Document.

Tim Flater
Senior Designer
Enkei America, Inc.

http://www.enkei.com

 

[kumarm2]

Hi all,

I want to thank all the people who posted your valuable feedback.

Special thanks to Tim flater.

When we had purchased the GM tool bit, we have missed it.
I couldn't find it from the GM tool bit.

I appreciate it.

Thanks,
Madhan kumar

 

[Xwheelguy]

Does that mean you fixed your issue or are you still having problems?

Tim Flater
Senior Designer
Enkei America, Inc.

http://www.enkei.com

 

[kumarm2]

Right now i am in USA at customer site. I don't have UG on my Machine. I have send your reply to india to look into this.They will work on your solution,I will get their reply only on tomorrow. It looks like ,it will solve our problem. Thank you very much.

Meantime, team asked me to send file checker requirements documents which i dont have it.

I have requested you to send it to me.Please, i appreciate it.

Madhan

 

[fgbrender]

Madhan,
When you say you are at customer site, do you mean GM? I can tell you who at GM can help you with your problem and possibly provide you with the documentation.

 

[Xwheelguy]

fgbrender,

I believe he's in the states and the people that are actually having the issue are in India...Madhan is sort of the "go between" if you will.

Madhan,

The documentation is included with the toolkit, if it's downloaded from GTAC (UG's support site). If you install the toolkit, you will need to navigate to the install directory then browse to [toolkit install path]\gmpdl3b13\docs. There you will find all the documentation for the toolkit (that's included with the download). To find out what specific File Checker errors are, refer to the file named fc_users_guide.html.

If you have a specific issue where you need support and the toolkit guides are of no help, you can call or email GM's support folks at:

GEES Service Desk 1-888-238-1119, Monday through Friday, 7am-5pm, EDT or send an email to geescallcenter@eds.com.

Tim Flater
Senior Designer
Enkei America, Inc.

http://www.enkei.com

 

[fgbrender]

I understand that the problem is in India and I am well aware of the Helpdesk. I'm not sure who Madhan works for or who he is visiting here in the states but here is a little more info.

The help desk is level 1 general support. If you call them, ultimately you will be forwarded to someone else. The group that handles this type of problem for GM is called the Engineering Design Assistance Group. As I said before, I worked for 15 years at GM and worked as a Teamcenter and NX support person and trainer, among other responsibilities. If you are at the GM tech center, I can tell you who to contact regarding this issue for both help and documentation.

As for the problem with the file being in India, it's no problem as the support folks here have access to the India database.

Of course, this all means little if you are not visiting GM, but I am assuming since you are using the GMPDL that your client is GM. If that is the case there should not be a problem contacting the responsible folks at GM.

 

[kumarm2]

Thanks to Tim Flater and fgbrender .

Rightnow,I am not at GM site. We are one of the supplier to GM supplier and doing some Modeling and detailing work for GM supplier. We have end up this problem.

Based on your feedback,I have send your replies to india. This is what i received from india,


Suggestion 1:

Error No. 1102: Could not validate the reference set.

Reference set name: XXXX

Check that the site_optional_file is readable and correctly formatted. Where ‘XXX’ is the reference set name.

Cause: Could not open the site_optional_file to validate named refset.

Solution: Validate that the site_optional_file in $FILE_CHECK_SITE_REFS is readable and correctly formatted. Where FILE_CHECK_SITE_REFS is an environment variable.

REPLY FROM INDIA: This solution is available in DCS file checker help and we have read thro it already. In the same solution you can find “please refer File checker Requirements Document" and we have given a request for this doc in note # 2.

So try to get "File checker Requirements Document" from customer.

2) Suggestion 2:

A) There is an actual file that lists the names of site optional reference sets and the file was over-written or not copy/pasted during the toolkit upgrade (from NX2 to NX3).

REPLY FROM INDIA: We have newly installed GM tool kit for NX3 and we have only NX3 in our machine and our installation is not an up gradation.

B) The environment variable for site_optional_refset file has not been defined since upgrading to the NX3 toolkit.

REPLY FROM INDIA: We have already set the Environment variable site_optional_refset.

We think "site_optional_file" is referring to a file but we do not have any file by that name. so please confirm with the customer and try to get this file.


“FILE_CHECK_SITE_REFS=%GMPDL_DATA_DIR%\filechk\site_optional_refsets” This is the declaration set in the Gmlaunch.dat file in our installation. Please talk to customer and ask them any file is stored within this declared folder. We have this empty at our end.

Could please send me some feedback?

 

[kumarm2]

Even i have conducted GEES Service Desk. No Solution from them. They are also giving the same information.

 

[Xwheelguy]

Can the MODEL referece set that is causing the problem be deleted? If not, WHY? It is NOT required by GM and if it's causing problems with GM data, then don't use it.

What is happening is that the toolkit is looking for a file that defines ADDITIONAL reference sets that your company wants to use. YOU DON'T HAVE TO USE THEM!!! Either this site_optional_refsets file doesn't exist or it has the wrong permissions because you're using a reference set that DOES NOT BELONG with a GM part (based on GM's data requirements). If your company doesn't NEED additional reference sets, then the environment variable in gmlaunch.dat needs to be commented out with an asterisk (*) so the toolkit will stop looking for it. You will need to restart NX for the change to take effect. Commenting out the environment variable is NOT going to fix the problem in your part though...you need to also DELETE the reference set that doesn't belong!

I don't have any further solutions. I feel we have isolated the problem and now you need to figure out how to remove the reference set that is causing this whole problem. It's an OPTION (the MODEL reference set) and obviously your users do not know how to set up the toolkit so that user defined reference sets can be used. Since that's the case, then DON'T USE THEM!

There isn't a user guide that is going to solve this problem or tell you how to fix it, no matter how many times you ask.

One other option is to call GTAC and send them the part and have them remove the reference set (MODEL) that is causing the problem and then see if the file passes the file checker.

You can also try exporting the part to a NEW NX part and see if that helps at all.

Tim Flater
Senior Designer
Enkei America, Inc.

http://www.enkei.com

 

[fgbrender]

I have to agree with Tim. There is no documentation that will help you. What you need to do is make sure you have the GMPDL installed correctly and completely.

You stated that everything was fine in NX2. Well, the MODEL reference set existed in NX2 and you were set up to pass files with the MODEL reference set. This means that you did not update properly when you went to NX3.

You need to get ahold of GTAC and get the "site_optional_file". File checker will not work properly without it.

Also, deleting the MODEL reference set will not work because it is automatically created by NX3 when you have geometry. That is why GM revised file-checker to allow it.


I wouldn't mess with the gmlaunch.dat file. Instead you need to install everything EXACTLY as GM has installed.

Your IT guys should have some contact at GM that can help them.

 

[Xwheelguy]

I disagree about not messing with gmlaunch.dat file....but do as you wish.

I never understood why we have to "fit" UG to the toolkit (after we've already installed NX)...the toolkit should "fit" to where NX is already installed, not force you to install to C:\eng_apps\, which is NOT the default path NX3 wants to install to....perfectly logical, huh?

Tim Flater
Senior Designer
Enkei America, Inc.

http://www.enkei.com

 

[fgbrender]

Agree or disagree, if your doing work for GM and want it to meet their standards, you have to follow their rules.

Messing with the gmlaunch file is only asking for trouble. It is designed to give you the exact environment you need to meet their standards.

Believe me, I didn't always agree with them but ultimatly they are the ones paying and like it or not they are the customer.

With all that said, the best way to solve the problem that started this thread is to make absolutly sure that averything is installed per GM environment.