Locked
Re: WOW 121/ERROR (308)
I am getting the same problem, and I know it isn't the command station or power Supply. I tried it on two different command stations and power supply's and get the same 308 error.
How ever if I just use the simple programmer to read or change CV's it works fine.
It is the "Read all CV's" or 'Sheet" that gives me the errors.
Dennis
|
Locked
Re: JMRI & Windows Vista
Hi Rich, Much will depend on whether you are able to get Java 8 running on it. That is the major JMRI requirement that you could run foul of as far as I can see. Wouter On 4 July 2017 at 04:02, modeltrainnut@... [jmriusers] < jmriusers@...> wrote:
I just dug out my old Toshiba Gaming Laptop which is still running Windows
Vista. Are any of the current versions of JMRI compatible with Vista, and
if so, would I be able to use current definition files with that version?
The laptop still has some useful software installed, and most Windows
upgrades seem to require me to wipe the hard drive clean and start anew. I
don't know where most of the older software source media is anymore...
Rich Velten
Ballwin, MO
|
Hi
Thanks, got it. Created a new mast with no user name and I can "move" an old mast to it.
Thanks again
Peter
|
Locked
Re: JMRI and Tsunami2 TSU-1100
On Jul 3, 2017, at 7:12 PM, breezlys@... [jmriusers] <jmriusers@...> wrote:
Could this be a Mac-specific issue? Certainly could be. For a long time, MacOS X came with the right drivers for the PR3; nothing needed to be added. But perhaps that¡¯s no longer true. My PR3 does work with macOS 10.12.5, though. Bob -- Bob Jacobsen rgj1927@...
|
Locked
Re: JMRI and Tsunami2 TSU-1100
Jay - you indicate Java 6. You need Oracle's Java 8.
Fred
Sent from the Twilight Zone!
toggle quoted message
Show quoted text
On Jul 3, 2017, at 7:39 PM, [email protected] [jmriusers] <jmriusers@...> wrote:
I tried a clean install of both 4.6 & 4.75. Neither would talk to the PR3.
Mac OS X 10.11 Java 6.
JMRI launches fine & gives no errors after setting it to the right port.
It sees the PR3, but will not talk to it.
Thanks!!
Jay - AT&SF
[Non-text portions of this message have been removed]
------------------------------------
Posted by: [email protected]
------------------------------------
------------------------------------
Yahoo Groups Links
|
Locked
Re: JAVA platform binary SE has quit working.
Jack,
When you say you "close it and try to open it again later", are you referring to exiting JMRI and starting it later, or are you physically closing and later opening the laptop itself?
If you're exiting and re-starting JMRI, Billybob's advice to check your PR3's firmware is spot-on.
But if you're physically closing and reopening the laptop itself, you're probably putting the USB port into a sleep or low-power state (if not turning it off completely). Java unfortunately copes with that poorly, resulting in the "Stopped working" message.
HTH,
Steve
"Breezlys"
---In jmriusers@..., <jceiermann@...> wrote :
I can open Panel Pro the first time I start the laptop. But when I close it and try to open it again later I get the message
Java platform binary SE has stopped working.
I'm using a VAIO and the latest JMRI. . W10. JMRI connection is PR 3. Port 4
Suggestions please,
Thanks,
Jack Eiermann
[Non-text portions of this message have been removed]
|
Locked
Re: JAVA platform binary SE has quit working.
Billybob,
There are two more potential causes for the "JAVA Platform binary has stopped working" message when using a PR3:
One is that if you plug it into a different USB port, Windows may think it's a different device and assign a different Com port number. The other is if your USB port goes into a low-power "sleep" state.
Java handles the lack of communication with the PR3 poorly in either of those cases, and the result is that not-very-helpful "Stopped Working" message..
As for Windows 10 and the PR3, they work just fine together. And depending on how current you are with your Windows updates, you may not even need to install the Digitrax "drivers". More into on that here: <>
HTH,
Steve
"Breezlys"
---In jmriusers@..., <jawhugrps@...> wrote :
Jack,
That's a frustrating experience!
Historically, the "JAVA Platform binary has quit working" message, when using a Digitrax PR3, is one of two things: PR3 firmware version or Windows PR3 drivers. Both are available from the Digitrax web site, in the "Downloads" section. For me, the PR3 firmware update solved my "binary stopped working" problems on a 64-bit Win7 computer.
You will want to use the "PR3 WIndows XP, Vista, 7, 8, and 10 Drivers". You can use DigiIPLII (available in the "SoundLoader2" package on the Digitrax web site "Downloads" page) to find out which version of firmware you have in your PR3. Use the DigiIPLII tool's "Find Devices" button to get the firmware version information. I think it is in the "S/W" column in the "Find Devices" table. Current PR3 firmware, as available on the Digitrax web site "downloads" page is "1.0".
An additional problem sometimes crops up - some USB cables shipped with the PR3 have been known to cause USB difficulties with some computers, and replacing them often solves USB problems.
I'll leave the Windows 10-specific investigations to those who have experience with it; I have thus far been able to not even touch a Win10 machine, so don't have any experience.
Depending on what JMRI version you are using, there may be a relationship to some new interface software that has been in very recent JMRI versions - ones where the so-called "PureJavaCommunications" library is used instead of the older "RXTX" library. What JMRI version are you using? Numbers are important here, as JMRI 4.6 can be significantly different from JMRI 4.7.6!
There are other possible causes, including "corrupted" JAVA installs, "corrupted" windows installs, etc. These are less-likely causes, and should be left for later investigations if problems persist after investigating the items above.
My bet would be PR3 firmware revision, but I could be wrong...
Regards,
Billybob
[Non-text portions of this message have been removed]
|
I just dug out my old Toshiba Gaming Laptop which is still running Windows Vista. Are any of the current versions of JMRI compatible with Vista, and if so, would I be able to use current definition files with that version?
The laptop still has some useful software installed, and most Windows upgrades seem to require me to wipe the hard drive clean and start anew. I don't know where most of the older software source media is anymore...
Rich Velten
Ballwin, MO
|
Locked
Re: JMRI and Tsunami2 TSU-1100
I tried a clean install of both 4.6 & 4.75. Neither would talk to the PR3.
Mac OS X 10.11 Java 6.
JMRI launches fine & gives no errors after setting it to the right port.
It sees the PR3, but will not talk to it.
Thanks!!
Jay - AT&SF
|
Locked
Re: JMRI and Tsunami2 TSU-1100
Could this be a Mac-specific issue?
Another user has reported experiencing the same issue when he moved a working PR3 installation from a W10 machine to an iMac: <>.
Customtraxx (George?) has reported that he's used the PR3/MacBook Pro combination in stand-alone programming mode for years with no issues, so we have to assume his JMRI preferences and physical/electrical connections are (or were) good: <>
And if I¡¯m reading his earlier post correctly, he also reported that another user at his club, apparently also a Mac/PR3 user, had the same issue: <>
Can any of the developers with a Mac and PR3 look into this from the Mac side of things? I'm not a Mac user, so I'm not able to help other than pointing out the above which seems like too much of a coincidence to me. FWIW, my PR3 is working fine with JMRI.4.7.6.R570b2bc on W10.
Steve
"Breezlys"
---In jmriusers@..., <decals@...> wrote :
I did that a few times. Still (306).
[Non-text portions of this message have been removed]
|
Locked
Re: JMRI and Tsunami2 TSU-1100
I did that a few times. Still (306).
|
Locked
Re: JAVA platform binary SE has quit working.
Jack,
That's a frustrating experience!
Historically, the "JAVA Platform binary has quit working" message, when using a Digitrax PR3, is one of two things: PR3 firmware version or Windows PR3 drivers. Both are available from the Digitrax web site, in the "Downloads" section. For me, the PR3 firmware update solved my "binary stopped working" problems on a 64-bit Win7 computer.
You will want to use the "PR3 WIndows XP, Vista, 7, 8, and 10 Drivers". You can use DigiIPLII (available in the "SoundLoader2" package on the Digitrax web site "Downloads" page) to find out which version of firmware you have in your PR3. Use the DigiIPLII tool's "Find Devices" button to get the firmware version information. I think it is in the "S/W" column in the "Find Devices" table. Current PR3 firmware, as available on the Digitrax web site "downloads" page is "1.0".
An additional problem sometimes crops up - some USB cables shipped with the PR3 have been known to cause USB difficulties with some computers, and replacing them often solves USB problems.
I'll leave the Windows 10-specific investigations to those who have experience with it; I have thus far been able to not even touch a Win10 machine, so don't have any experience.
Depending on what JMRI version you are using, there may be a relationship to some new interface software that has been in very recent JMRI versions - ones where the so-called "PureJavaCommunications" library is used instead of the older "RXTX" library. What JMRI version are you using? Numbers are important here, as JMRI 4.6 can be significantly different from JMRI 4.7.6!
There are other possible causes, including "corrupted" JAVA installs, "corrupted" windows installs, etc. These are less-likely causes, and should be left for later investigations if problems persist after investigating the items above.
My bet would be PR3 firmware revision, but I could be wrong...
Regards,
Billybob
|
Locked
JAVA platform binary SE has quit working.
I can open Panel Pro the first time I start the laptop. But when I close it and try to open it again later I get the message
Java platform binary SE has stopped working.
I'm using a VAIO and the latest JMRI. . W10. JMRI connection is PR 3. Port 4
Suggestions please,
Thanks,
Jack Eiermann
|
Locked
Re: Slow loading file with JMRI 4.7.4ish
Thanks for providing the file. That helps a lot. The largest amount of time was spent re-loading some parts of the Logix user interface as the sensors were loaded. Each time, the comboboxes for selecting a sensor were being recreated from scratch. As they got larger, that got slower. PR #3715 has a proposed fix, which should be in development builds later today. Bob On Jul 3, 2017, at 11:53 AM, 'David Parks' bearwestern@... [jmriusers] <jmriusers@...> wrote:
I have posted a problem file named SensorLoad.xml in the yahoo group upload
area (via Leo).
This file contains only Internal Sensors. Windows 10
4.6.0 - manual load time about 1 seconds
4.6.0 - auto load time about 2 seconds
4.7.4ish - manual load time 41 seconds
4.7.4ish - auto load time 21 seconds
I have tried a large number of variations of this file and found that simple
numeric names with no user names load faster, but still around 50 times
slower in 4.7.4 then in 4.6.0. The empty panel is displayed to make it
easier to see when the Sensors are finished loading. We have tried the same
load test in versions later than 4.7.4 and not found a difference in timing.
The discrepancy in Load time is not unique to Sensors and follows the same
pattern with complex files with many classes of entities.
David Parks
Los Altos, CA
-- Bob Jacobsen rgj1927@...
|
Locked
Re: JMRI sensors DCC++ and invalid XML files
Thanks for the updates folks.
|
Locked
Slow loading file with JMRI 4.7.4ish
I have posted a problem file named SensorLoad.xml in the yahoo group upload
area (via Leo).
This file contains only Internal Sensors. Windows 10
4.6.0 - manual load time about 1 seconds
4.6.0 - auto load time about 2 seconds
4.7.4ish - manual load time 41 seconds
4.7.4ish - auto load time 21 seconds
I have tried a large number of variations of this file and found that simple
numeric names with no user names load faster, but still around 50 times
slower in 4.7.4 then in 4.6.0. The empty panel is displayed to make it
easier to see when the Sensors are finished loading. We have tried the same
load test in versions later than 4.7.4 and not found a difference in timing.
The discrepancy in Load time is not unique to Sensors and follows the same
pattern with complex files with many classes of entities.
David Parks
Los Altos, CA
|
Locked
New file uploaded to jmriusers
Hello,
This email message is a notification to let you know that
a file has been uploaded to the Files area of the jmriusers
group.
File : /SensorLoad.xml
Uploaded by : pr_leo0 <lpescester@...>
Description : Sensor File load delay in 4.7.4ish but not in 4.6.0
You can access this file at the URL:
To learn more about file sharing for your group, please visit:
Regards,
pr_leo0 <lpescester@...>
|
Locked
New file uploaded to jmriusers
Hello,
This email message is a notification to let you know that
a file has been uploaded to the Files area of the jmriusers
group.
File : /ProblemsBeingWorkedOn/testjunct.xml
Uploaded by : johnpw22 <johnpw22@...>
Description : testjunction file giving errora from John W
You can access this file at the URL:
To learn more about file sharing for your group, please visit:
Regards,
johnpw22 <johnpw22@...>
|
Locked
Re: WOW 121/ERROR (308)
Thanks Steve,?On my way to pick up a New power supply!
Sent from Yahoo Mail on Android
toggle quoted message
Show quoted text
On Mon, Jul 3, 2017 at 11:09 AM, breezlys@... [jmriusers]<jmriusers@...> wrote: ?
John,
The 308 indicates that when the PR3 sends a programming command, it isn't hearing an acknowledgement back from the decoder. There are two likely causes.
One is that there's a bad connection somewhere between the PR3 and the decoder. It could be a loose wire somewhere, or even something as simple as the loco's wheels not making good contact with the programming track.
The other possibility is that the DC power supply you're using with your PR3 is insufficient for the WOW's programming needs. If you're using a PS12 or PS14, try something in the 16-18VDC range.
I have a WOW 121 in a Kato SD40, and my PR3 with an 18VDC regulated supply reads/writes from/to it with no issues at all.
HTH,
Steve
"Breezlys"
---In jmriusers@..., <j.barone43@...> wrote :
Good morning all,Recently installed a wow 121 kit into atlas locomotive. Started programming with Decoder Pro, some CV'S program with no problem, others don't seem to take programming?I.e. I try to change or remap a function, and I'll either get that (308) error message or if no message, when I try to activate the function, it doesn't work?I'm using jmri 4.6 Windows 10 ,pr3 to dedicated programming track.Any suggestions?Thanks John...
Sent from Yahoo Mail on Android
[Non-text portions of this message have been removed]
#yiv6497491742 #yiv6497491742 -- #yiv6497491742ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv6497491742 #yiv6497491742ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv6497491742 #yiv6497491742ygrp-mkp #yiv6497491742hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv6497491742 #yiv6497491742ygrp-mkp #yiv6497491742ads {margin-bottom:10px;}#yiv6497491742 #yiv6497491742ygrp-mkp .yiv6497491742ad {padding:0 0;}#yiv6497491742 #yiv6497491742ygrp-mkp .yiv6497491742ad p {margin:0;}#yiv6497491742 #yiv6497491742ygrp-mkp .yiv6497491742ad a {color:#0000ff;text-decoration:none;}#yiv6497491742 #yiv6497491742ygrp-sponsor #yiv6497491742ygrp-lc {font-family:Arial;}#yiv6497491742 #yiv6497491742ygrp-sponsor #yiv6497491742ygrp-lc #yiv6497491742hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv6497491742 #yiv6497491742ygrp-sponsor #yiv6497491742ygrp-lc .yiv6497491742ad {margin-bottom:10px;padding:0 0;}#yiv6497491742 #yiv6497491742actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv6497491742 #yiv6497491742activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv6497491742 #yiv6497491742activity span {font-weight:700;}#yiv6497491742 #yiv6497491742activity span:first-child {text-transform:uppercase;}#yiv6497491742 #yiv6497491742activity span a {color:#5085b6;text-decoration:none;}#yiv6497491742 #yiv6497491742activity span span {color:#ff7900;}#yiv6497491742 #yiv6497491742activity span .yiv6497491742underline {text-decoration:underline;}#yiv6497491742 .yiv6497491742attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv6497491742 .yiv6497491742attach div a {text-decoration:none;}#yiv6497491742 .yiv6497491742attach img {border:none;padding-right:5px;}#yiv6497491742 .yiv6497491742attach label {display:block;margin-bottom:5px;}#yiv6497491742 .yiv6497491742attach label a {text-decoration:none;}#yiv6497491742 blockquote {margin:0 0 0 4px;}#yiv6497491742 .yiv6497491742bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv6497491742 .yiv6497491742bold a {text-decoration:none;}#yiv6497491742 dd.yiv6497491742last p a {font-family:Verdana;font-weight:700;}#yiv6497491742 dd.yiv6497491742last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv6497491742 dd.yiv6497491742last p span.yiv6497491742yshortcuts {margin-right:0;}#yiv6497491742 div.yiv6497491742attach-table div div a {text-decoration:none;}#yiv6497491742 div.yiv6497491742attach-table {width:400px;}#yiv6497491742 div.yiv6497491742file-title a, #yiv6497491742 div.yiv6497491742file-title a:active, #yiv6497491742 div.yiv6497491742file-title a:hover, #yiv6497491742 div.yiv6497491742file-title a:visited {text-decoration:none;}#yiv6497491742 div.yiv6497491742photo-title a, #yiv6497491742 div.yiv6497491742photo-title a:active, #yiv6497491742 div.yiv6497491742photo-title a:hover, #yiv6497491742 div.yiv6497491742photo-title a:visited {text-decoration:none;}#yiv6497491742 div#yiv6497491742ygrp-mlmsg #yiv6497491742ygrp-msg p a span.yiv6497491742yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv6497491742 .yiv6497491742green {color:#628c2a;}#yiv6497491742 .yiv6497491742MsoNormal {margin:0 0 0 0;}#yiv6497491742 o {font-size:0;}#yiv6497491742 #yiv6497491742photos div {float:left;width:72px;}#yiv6497491742 #yiv6497491742photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv6497491742 #yiv6497491742photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv6497491742 #yiv6497491742reco-category {font-size:77%;}#yiv6497491742 #yiv6497491742reco-desc {font-size:77%;}#yiv6497491742 .yiv6497491742replbq {margin:4px;}#yiv6497491742 #yiv6497491742ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv6497491742 #yiv6497491742ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv6497491742 #yiv6497491742ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv6497491742 #yiv6497491742ygrp-mlmsg select, #yiv6497491742 input, #yiv6497491742 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv6497491742 #yiv6497491742ygrp-mlmsg pre, #yiv6497491742 code {font:115% monospace;}#yiv6497491742 #yiv6497491742ygrp-mlmsg * {line-height:1.22em;}#yiv6497491742 #yiv6497491742ygrp-mlmsg #yiv6497491742logo {padding-bottom:10px;}#yiv6497491742 #yiv6497491742ygrp-msg p a {font-family:Verdana;}#yiv6497491742 #yiv6497491742ygrp-msg p#yiv6497491742attach-count span {color:#1E66AE;font-weight:700;}#yiv6497491742 #yiv6497491742ygrp-reco #yiv6497491742reco-head {color:#ff7900;font-weight:700;}#yiv6497491742 #yiv6497491742ygrp-reco {margin-bottom:20px;padding:0px;}#yiv6497491742 #yiv6497491742ygrp-sponsor #yiv6497491742ov li a {font-size:130%;text-decoration:none;}#yiv6497491742 #yiv6497491742ygrp-sponsor #yiv6497491742ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv6497491742 #yiv6497491742ygrp-sponsor #yiv6497491742ov ul {margin:0;padding:0 0 0 8px;}#yiv6497491742 #yiv6497491742ygrp-text {font-family:Georgia;}#yiv6497491742 #yiv6497491742ygrp-text p {margin:0 0 1em 0;}#yiv6497491742 #yiv6497491742ygrp-text tt {font-size:120%;}#yiv6497491742 #yiv6497491742ygrp-vital ul li:last-child {border-right:none !important;}#yiv6497491742
|
Locked
Re: Decoder Pro inquiries
Hi Joe, Re 2): That is completely normal. Every decoder/gears/engine combination is unique - even when the models are the same and bought the same day. Wouter On 3 July 2017 at 12:15, Dave Heap dgheap@... [jmriusers] < jmriusers@...> wrote:
The check marks are intended as an aid to manipulating a speed curve to
achieve a desired result and are not stored in either the decoder or the
roster entry.
--
Dave in Australia
On 3 Jul 2017, at 9:59 am, Joebrann@... [jmriusers] <
jmriusers@...> wrote:
3. Since my speed matching lasted over several days I saved my roster
settings several times and noticed that on the speed table sheet the check marks
in the check boxes at the bottom of each speed step either didn't get
saved, or didn't get restored. Is this by design or should the check marks
and what they stand for be resorted. I would like ( and sorta excepted) that
they would be restored.
|
Bob Jacobsen
John Barone