cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X

JLink startup....

BrianKrieger
7-Bedrock

JLink startup....

Has anyone had a challenge getting a user to integrate a JLink program.
I can run it fine on my computer as can he. On his computer, I can run
it fine but it won't for him. I've opened access to all files, folders,
etc. that I can think of. I then scaled it back and just tried the test
program from PTC. I actually used his login to compile the JLink test.
I'm kind of at wit's end here. Is there a "hidden" security challenge
happening somewhere?



Brian Krieger

Peterbilt Motors

4 REPLIES 4

Brian -

This sounds like a configuration problem for your end user on his
machine. My suggestion is that you review the J-Link User Guide,
particularly the sections "Setting Up J-Link" and "Java Options
and Debugging".

My immediate suggestion would be to compare his CLASSPATH to yours,
as well as the PRO_JAVA_COMMAND variable. I set both of these
variables in the proe.psf file. They might also be defined in
other places, such as a startup script or the System control panel.

I believe that the user's CLASSPATH must include the path of pfc.jar,
which contains the J-Link classes.

|+| M a r k |+|

Mark Stallard
Engineering Information Management
Integrated Solutions & Development
Integrated Defense Systems
Raytheon Company



(business)
+1.978.436.6016
(cell)
+1.617.331.5443
(tie line)
239.6016
-

880 Technology Drive
Billerica, MA 01821
www.raytheon.com


This message contains information that may be confidential and privileged.
Unless you are the addressee (or authorized to receive mail for the
addressee), you should not use, copy or disclose to anyone this message or
any information contained in this message. If you have received this
message in error, please so advise the sender by reply e-mail and delete
this message. Thank you for your cooperation.





Hello Brain

What type of JLink application are you running, Sync or Async? If you are running a Async then you need to review your environment variables. The example of the paths are shown below.

path = (ProE LoadPoint)\i486_nt\lib\

PRO_COMM_MSG_EXE = (ProE LoadPoint)\i486_nt\obj\pro_comm_msg.exe

And make sure that the pfcasync.jar file is listed in the path statement. It is best to set these environment variables in the start Pro/E bat file.

Now for a Sync App:

Check to the see if the protk.dat file is register and make sure all the paths in the protk.dat file is valid for the user.

If you have any questions or concerns you can reach me at jfelkins@felcosolutions.com

Hope this helps.

I'm sure everyone was on pins and needles about my startup problem.
Long story short, it turned out to be a (very odd) java mismatch
somehow. On the computer, one user (me), was path'd (not classpath) to
the jdk1.5.0.12 (development kit) for java. When the other user logged
in, he was path'd to the jre1.5.0.12 (runtime engine only). Same
everything except the kit versus the runtime. I changed the path to the
jdk and it worked, so now I just path'd them to a newer version of the
jre (1.6) and that worked as well, so we're up and going.



When I looked at the paths, I would simply look at 1.5.0.12 and just
never caught the jdk vs jre.



Just an FYI.



Brian


In the J-link I use to set up the menues I have these methods called:

System.setOut(new PrintStream(new
FileOutputStream("d:\protrail\jlink_system_out.txt")));
System.setErr(new PrintStream(new
FileOutputStream("d:\protrail\jlink_system_err.txt")));
System.out.println("Java Runtime: " + System.getProperty("java.home"));

Then in the d:\protrail\jlink_system_out.txt I call always see which
java version is used on the client.

/Bjarne



Brian Krieger <->
08-12-2009 14:47
Please respond to
Brian Krieger <->


To
-
cc

Subject
[proecus] - RE: JLink startup....






I?m sure everyone was on pins and needles about my startup problem. Long
story short, it turned out to be a (very odd) java mismatch somehow. On
the computer, one user (me), was path?d (not classpath) to the jdk1.5.0.12
(development kit) for java. When the other user logged in, he was path?d
to the jre1.5.0.12 (runtime engine only). Same everything except the kit
versus the runtime. I changed the path to the jdk and it worked, so now I
just path?d them to a newer version of the jre (1.6) and that worked as
well, so we?re up and going.

When I looked at the paths, I would simply look at 1.5.0.12 and just never
caught the jdk vs jre.

Just an FYI.

Brian

Top Tags