Yesterday I installed my PR3 and loaded JMRI for the first time. Since then, though I have been able to EVENTUALLY open DecoderPro and PanelPro and work a little with them, I continue to have an issue actually opening the programs. I keep getting the Java message "Java platform SE binary has stopped working . . .". Yesterday when it first happened I must have installed/unistalled/reinstalled both Java and JMRI a half dozen times. It seems that when I get the message it sometimes seems that if I reboot my computer I can clear the issue, but today even that didn't work. I no longer want to unistall/install both softwares so I am asking if anyone knows what's going on. The computer is Win7-64 bit, JMRI is the newer release 3.6 and Java is newest release. Needless to say this is disappointing. Thanks all.
I had a virus in my computer that would want me to update everything i opened and it gave me a alot of trouble with JMRI. My virus scanner did not find it when i done a scan. I had to remove the virus manually . hope this helps.
Are you using the PR-3 in Loconet mode or Stand-Alone mode? I am also running this configuration on a 64 bit WIN7 laptop with the current JMRI(3.9-r24520) and current Java(1.7.0_51(en_US)) as well.
Jim
Modeling BNSF and Milwaukee Road in SW Wisconsin
Hi Jim. PR3 is in LocoNet mode. Java is Version 7 Update 51 (installed just yesterday). JMRI is their latest/just released version 3.6 (also installed just yesterday). The frustrating part is I finally got both DecoderPro and PanelPro to open yesterday (I even used DecoderPro to tweak the CV's in 2 engines), so everything sucessfully installed and was working, when I finally got it to open. Now today I keep getting "Java platform SE binary has stopped working" and can't open JMRI. I don't know if it is a Windows issue or a Java isuue or a JMRI issue or any combination. I am not savy enough at my "advanced age" to figure this one out on my own and need help. Thanks.
UPDATE-This is getting really strange. After my last post/reply to Jim from a half hour ago I ran a few trains and then was shutting down the layout for the day. So I figured what the heck, I'll try opening JMRI again, fully expecting to get the Jave platform message again. Don't you know DecoderPro opens! So now I really can't understand what's going on-why it wouldn't open an hour ago, I make no changes to anything, and now it opens. Something screwy is going on. Anyone have any idea? Thanks all.
Order of starting things up? Java has some serious faults in their serial port/USB driver area, in that if the device isn;t there when it tries to talk to it, Java just crashes. This also happens on my laptop after I let it go to sleep with JMRI still running - the instant I do something that accesses the PR3 after it wakes back up, Java crashes. If I don;t let it sleep, or set in Device Manager to not allow Windows to shut off the virtual serial port, I don't have this issue.
If you have it, try using the power supply with the PR3, even though you don't need it for MS100 mode. Turn that all on BEFORE trying to load JMRI.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
Thanks Randy. That may explain why it has opened sometimes and not open some times. So just to be clear, you are suggesting the following sequence: Wake up computer - power up PR3 (and entire Digitrax system) - insert USB into computer - open JMRI. BTW, I mention the USB step because it seems that is a secondary issue. Sometimes when JMRI has opened it doesn't reconize the USB connection, even though it is plugged in (and has been plugged in even during sleep mode), so I have been taking it out so that I can plug it in after the computer wakes up. For whatever reason it seems to make a difference. Does that make any sense?
Yeah if the computer doesn;t see the USB plugged in, it won't assign a port, and JMRI can't see it either. Also, always use the same USB port - for whatever reason, Digitrax never registered for an official USB ID, so if you plug in to a different USB port it will get a different virual serial port. Like, plug it into the left front USB, it's COM5. In the right rear USB port, it ends up COM8.
Another thing to remember when using a PR3 on a Windows computer is to ALWAYS plug the PR3 into the same USB port you had it plugged into when you first installed the PR3's drivers.
The USB chip that the PR3 uses doesn't have a unique serial number, so if you plug it into a different USB port, Windows may think it's a different device and assign it a different COM port number.
Then Java can't talk to it because your preferences are now "wrong", and you get the "Java has stopped working" error...
I'm really bummed at this point. I followed Randdy's sequence exactly and it wouldn't open. And Yes Stevert, I always plug the USB cable into to same port (thanks for suggesting that). Don't know where to go from here. Very disappoionted-had big plans for PanelPro to use with Digitrax BD168 and transponding to see what engines where occupying my hidden 8 yard storage tracks. Now I have to rethink this whole project. You would think with today's technology this stuff would just work, especially with this Java being an old product. Kinda makes me think this hobby was much more enjoyable in DC days-at least it was more simple and pure.
rrinker Order of starting things up? Java has some serious faults in their serial port/USB driver area, in that if the device isn;t there when it tries to talk to it, Java just crashes. This also happens on my laptop after I let it go to sleep with JMRI still running - the instant I do something that accesses the PR3 after it wakes back up, Java crashes. If I don;t let it sleep, or set in Device Manager to not allow Windows to shut off the virtual serial port, I don't have this issue. If you have it, try using the power supply with the PR3, even though you don't need it for MS100 mode. Turn that all on BEFORE trying to load JMRI. --Randy
Topias:
I don't know if this might be your problem but try a different USB cable to connect to your computer. I was having some intermittant problems with my LocoBuffer USB and traced it to a faulty USB cable. It was new but faulty allowing me to connect sometimes and not others.
Joe
Thanks Joe, that kinda worked. Tried a different cable and it open. Great I thought. Closed it, waited a few minutes and tried openiong again and failed. This is a royal P-I-T-A!
OK, I realize this is MY problem and by now you are all probably pretty bored, so just one more comment and then I'm out for today. With Joe's suggession of a different cable, I tripped over this - if I open DecoderPro WITHOUT the cable in the port it opens and a pop up come up indicating no COM6 port being used. So I close the pop up, and it move to the Preferrence screen, which is supposed to open only the first time you open DecoderPro. The port info. is in grey tone. I plug in the cable, save the preferrences and it opens correctly (i tested connectivity by turning on track power). So as long as I open it with the cable OUT of the USB port it seems to work, but it seems like an odd work around. Any suggestions that might make this work correctly? Again, thanks all for putting up with my problem-there are certainly more interesting topics for you all to read than this. I appreciate the help as always.
Not exactly the same problems you are having, but I have a Dell Optiplex desktop computer with Windows 7 Home Premium 64-bit on it that no matter what I try, will not recognize a Microchip USB to Serial Port Adapter, even though my two other computers work perfectly with it every time.
The two others have Windows 7 Professional 64-bit version, but I can't understand why Home Premium fails when the device drivers should be the same.
The only thing I can think of that might be causing this problem is the USB port drivers on the Dell, which are mother-board mounted, are not new enough to work with the Microchip device, although thumb drives and other devices have no problems.
So, your computer may be the root cause of the problem.
Thanks Cacole. My computer is a HP G62 laptop about 4-5 years old if that means anything.
In Device Manager, if you find the port being used, right click and select Properties. There should be a Power management tab, you cna uncheck the box that says "Allow the computer to turn off this device to save power". The harder part is finding which USB hub and controller it all is, because to really work you need to not allow it to turn off any component in the chain.
I kind of gave up, if I find my laptop has gone to sleep, I just exit JMRI and restart because I know I will get a Java stopped working error if I do anything else.
For a more long term reliable connection for automated operation and signal controls, the Locobuffer USB tends to not have these problems. I only use my PR3 as a standalone programmer, and even that I am considering replacing with the SPROG, mainly for performance reasons. My fixed layout computer actually runs JMRI under Linux and the interface there is an old serial Locobuffer built from hans DeLoof's circuit board, with a USB to serial adapter. That I have no problem with getting Java errors on, even if I haven't turned on the power supply to the Locobuffer.
Thanks for the tip Randy, but infortunately it didn't make any improveement. But I'm happy enough now that I can open JMRI with a little work around - wake up computer, power up DCS100 and PR3, unplug USB from computer, plug cable back into computer, open JMRI. Not the end of the world, at least I'm now confident I can at least get it open. Thanks to all for the advise on this, I appreciate it as always.
Gents: I stayed out of the discussion but have had the same problem getting into JMRI with the PR3. I have copied the sequence Tophias is using and will try it out. Hope it works for me too!
Owen, you should know that even the work around is hit and miss. It all comes down to the sequence of inserting the cable. You will just need to try all combinations, just be sure to always use the same USB port on your computer. And thanks to everyone who suggested: same USB port, Devise Manger/Power Management setting, different cable, powered hub and any other I can't remeber. I tried them all and nothing worked. Later today I will try un-installing Java (again!) and re-installing, though I don't think it will matter. I will also try an earlier version of Jave and even try it on my wife's newer Win8 laptop. About now it's beyond frustrating but having seen an interview of a severley wounded soldier last night and his struggles just to talk and walk I now have a much different attitude regarding my so called "problem". We need to put all this is perspective.
One other thing to try, that has been mentioned on the JMRI list as working on occasion, is to add a USB hub between the PR3 and the computer.
Both powered and unpowered hubs have been said to improve the situation, although which one in which situation seems to be hit or miss.
It's all very confusing to me; my PR3 has Always Just Worked on every machine I've ever tried it on (WinXP, Win7 32-bit and 64-bit, desktop, laptop, etc). Only if I intentionally assign the wrong COM port in my preferences, will I get the "Java has stopped working..." error.
"It's all very confusing to me;" - Tell mw about!! Thanks Stevert, I have tried a powered hub already (granted it's vintage 2002). Part of the frustration is when I first log on I usually get the JMRI pop-up "ComPort 6 no cable . . (or whatever is states) even though it's plugged into the same USB port. So I hit OK and it moves to the "Prefferences" window (as if it think this is my very first opening of JMRI), where in gray scale it already has my Comport 6 listed but as I say in gray scale so I hit save and it might open, might not, so I start again, maybe next time with the cable NOT plugged in. Somebody get me a gun!!!
Well finally I think (I hope) I have this figured out. In doing a google search yesterday I saw many postings from gamers (of which I am not one) and many indicated to go into Properties/Capatabilty aaand click on "Capatable with Windows 7". I think that finally fixed my problem, that plus be aware of the LED staus showing on the PR3. Just one last question (I hope): I found I can not have both PanelPro and DecoderPro open at once. I can open either one, but when I go to open the other I get a pop-up stating "Comport X in use". Is this normal? Is there a fix for that, though at this point I'm just happy to be able to open either one, one at a time. Again, thanks to all who help thru this mess. I appreciate the help.
That is normal. They are both shortcuts to the same program, really. In fact, they can have their own preferences, so the default for DecoderPro can be PR3 in standalone mode for programming and the default for PanelPro can be PR3 in MS100 mode to control Loconet. From within either program, you can access the screens of the other one. DecoderPro3 is a bit different as it opens specifically in programming mode without the same main menu you get with the others.
Yes, it's normal that you can't have both DecoderPro and PanelPro open at the same time, at least not when the preferences for both of them point to the same DCC interface device. Think of it as trying to burn a CD while you're listening to a different audio CD - It ain't gonna work if you only have one CD drive.
But you don't really need to have them both open. They're just different front-ends to the same code base, so each of them is capable of the same functions as the other. You might have to dig a little, for example, through the PanelPro menu to find a certain DecoderPro function, but they're there. AFAIK, only DP3 tries to hide some of the other stuff from you.
In my case, I have my DecoderPro preferences set up to use my PR3 as a stand-alone programmer, and my PanelPro preferences set up to use it in LocoNet mode. Then I simply have to start one or the other based on what I'm going to be doing, knowing that I can still access the "other" functions if necessary**.
**Keep in mind that the PR3 can only operate in EITHER LocoNet mode OR stand-alone programmer mode at any given time, and not in both modes at the same time. So depending on what other activity you select, you may "kick out" whatever the PR3 is doing at the time if your selection causes JMRI to change the PR3's mode.
Stevert and Randy, as always, thanks for the advise. Just checked it out. Actually pretty simple stuff, which makes it perfect for me! It's been quite a "journey" this past week getting this finally working and again I want to thank all who guided me-could not have done it without all your help.
owen w in california Gents: I stayed out of the discussion but have had the same problem getting into JMRI with the PR3. I have copied the sequence Tophias is using and will try it out. Hope it works for me too!
Owen, hope you got your computer/PR3/JMRI working. If not, there was one additional thing I did after my last post and it might help you. I changed the setting on my laptop such that it does not Hibernate or Power Off when idle; it only sleeps. Don'tknow if that makes a difference but mine has been bulletproof since then.
I had the same issue with the PR3 I just acquired. After trying with 2 different computers, I found the issue was in the JMRI settings. With my setup, the PR3 is connected to a DCS51 which needed to be specified in the Command Station type in the preferences.
Thanks for the follow up note Tophias. I'll be working on this over this rainy weekend here in So California. It's been hit or miss getting Decoder Pro up; sometimes it works, sometimes not. But, in all honesty, I have not been as organized as I should be in troubleshooting the order of startup steps. That's this weekend. Paper and pencil, step one....
I hear you Owen. As I previously mentioned it took me a week trying this and that, posting and getting great advise from everyone here, and even going out on the net for other input (from Gamers of all people). One last little bit, which may or may not matter, is be sure your computer is fully "awake" or powered on. I always open my browser first to be sure all is active, then plug in your USB cable and then open JMRI. Good luck. And good luck with your weather, hope you don't get any mud slide issues I have been seeing on the news.