开云体育

Locked Error 303


 

I have a Digitrax PR3 hooked to programming track, a Digitrax DCS 51 Zephyr Xtra and a Windows 10 PC with Decoder Pro 4.18+R37ad3d0. No problems till all of a sudden I'm trying to enter some new engines. I placed the first on the programming track, checked that Programming Track is set on Decoder Pro and clicked on Nesw Loco as I've done many times before. I fails with the error message: "Stopping due to error: No acknowledge from locomotive (303)".I've tried several locomotives, restarted my computer and Decoder Pro several times, reinstalled the drivers, reset the PR3 holding down the two buttons till the stat light blinks red and green several times and reset the DCS51 setting Switch 39 to closed. Is there any way to get this working again?
--
Richard Richter


 

If you have done no changes what so ever, I would look in system restore and see when was your last update. Seems to be a rash of people complaining of sudden failure.
Makes me think some kind of update is occurring.

Inobu


 

开云体育

Richard,

?

  1. Are you using the PR3 as a computer interface between the DCS51 and your computer; OR are you using it as a ‘stand-alone’ programmer (without being connected to the DCS51?? (Your statement isn’t clear on this.)

?

  1. Do your JMRI connection preferences match your setup?? Also check ‘Defaults.’? Make sure they are all set for LocoNet.? (Edit; Preferences; Connection or Defaults)

?

  1. Is ‘303’ a typo ?? “303 - requested not implemented in command station”? ???“308 - No acknowledge from locomotive”? Full descriptions here:

?

  1. What decoder brand?? Does it have a ‘keep-alive’ attached?? Some decoders are known to be very difficult to read.? With some specifics we can better help you with specific techniques.

?

Resetting the PR3 will not likely help – JMRI sets the PR3 (based on your connection preferences).? I’ve never heard of resetting a command station helping with a programming problem.

?

Help us help you – please get us some more information.

?

Ross

?

?

?

From: [email protected] <[email protected]> On Behalf Of rprdds24@...
Sent: Thursday, April 2, 2020 5:03 PM
To: [email protected]
Subject: [jmriusers] Error 303

?

I have a Digitrax PR3 hooked to programming track, a Digitrax DCS 51 Zephyr Xtra and a Windows 10 PC with Decoder Pro 4.18+R37ad3d0. No problems till all of a sudden I'm trying to enter some new engines. I placed the first on the programming track, checked that Programming Track is set on Decoder Pro and clicked on Nesw Loco as I've done many times before. I fails with the error message: "Stopping due to error: No acknowledge from locomotive (303)".I've tried several locomotives, restarted my computer and Decoder Pro several times, reinstalled the drivers, reset the PR3 holding down the two buttons till the stat light blinks red and green several times and reset the DCS51 setting Switch 39 to closed. Is there any way to get this working again?
--
Richard Richter


 

Ross,
Thanks for your reply. You're right! I'm blind. It is 308. It pays? to clean my glasses every now and then. As to the rest of the quetions:

1. The PR3 is? attached to the computer with a USB cable and attached to the DCS51 with a Loconet cable. All cables have been checked and connections have been reattached.
2. I checked the Preferences and the Defaults and eveerything is correct.
3. As I said, it's "308"
4. I tried several engines with different decoders. When you're desperate, you'll try anything. A = BLI Paragon 3, B = Bachmann E-Z? Sound, C = Loksound 5 Micro. They all got the same result. B & C had been previously read successfully.

Again, thank-you for your help.
--
Richard Richter


 

Ross,
I should alsosay that the programming track is attached to the PR3 but I got the same result attaching it to the DCS51. Thjanks for your help.
--
Richard Richter


 

开云体育

Richard,

?

Let’s first get you working with one of the decoders you successfully read before.

?

When you successfully read the decoders was the programming track connected to the PR3 or DCS51?

?

When you changed the programming track connection between the PR3 and DCS51 did you change your JMRI preferences to match?

?

Did you plug the PR3 into the same USB port as when you earlier had success?

?

Was JMRI 4.18 or an earlier version used for your successful reads?

?

Ross

?

?

From: [email protected] <[email protected]> On Behalf Of rprdds24@...
Sent: Friday, April 3, 2020 8:48 AM
To: [email protected]
Subject: Re: [jmriusers] Error 303

?

Ross,
I should alsosay that the programming track is attached to the PR3 but I got the same result attaching it to the DCS51. Thjanks for your help.
--
Richard Richter


 

Ross,
Good Morning.
The previously successfully read decoder was the BLI Paragon 3 and the programming track was attached to the PR3.
I did not change the preferences. It has/had worked in both locations. I didn't know there was a suitable preference and never gave it a second thought. Admittedly, the only Preference I ever changed was the File Location. I honestly don't remember why I changed it.
The USB port has not changed. I checked the port in Device Manager and all is well with the drivers and it recognizes the PR3 though it doesn't use that name.
JMRI 4.18 has worked for the BLI and other locomotives as well as previous versions.
Thanks for your help.
--
Richard Richter


 

开云体育

Richard,

?

Ok – Let’s get to work.? We now know that you are using your PR3 in ‘stand-alone’ mode since the programming track is connected to the PR3.? I have several things for you to check.

?

(I don’t have ready access to a PR3; if anybody sees an error or has suggestions please ‘jump in.’)

?

First, I suggest you confirm the Digitrax drivers are installed and functioning.? From the Digitrax PR3 Xtra manual; Troubleshooting guide:?

“To verify proper installation of the drivers, go to the Windows Device Manager. Under Ports (COM & LPT) there should be a Communications Port (COMx) listed, where COMx is the communications port number or com port.? Right clicking on the communications port and then clicking on Properties should show Digitrax, Inc. as the Manufacturer.

Note:? The Ports (COM & LPT) may only be visible when the PR3 is connected to a USB port.)

?

?

Next, verify your DecoderPro ‘Connection’ and ‘Default’ settings.? From the DecoderPro drop-down menu;

Edit -> Preferences -> Connections

I expect you have one connection tab named ‘LocoNet’ displaying;

System Manufacturer – Digitrax

System Connection – LocoNet PR3

Serial Port: (From test above)

Command Station Type:? PR3 standalone programmer

Connection Prefix - L (preset)

Connection Name - LocoNet (preset)

?

Edit -> Preferences -> Defaults

All should be set to LocoNet; NOT Internal

?

‘Save’ and re-start DecoderPro

?

?

What is the voltage on your PR3 power supply?? (If using a Digitrax PS14 please check the specs on the plug; older units are 14 volts DC; newer units are 14.9 volts DC.)??

?

FWIW, BLI Paragon 3 are often difficult to read.? A higher voltage power supply often helps.? ‘Old’ printer or laptop power supplies are often regulated 16- or 18-volts DC.? Mark Granville reported success with Paragon 2 & 3 decoders using a 17-volt DC power supply in a recent discussion on the Digitrax list.? You could also try another decoder you’ve successfully read in the past.

?

HTH,

Ross

?

From: [email protected] <[email protected]> On Behalf Of rprdds24@...
Sent: Saturday, April 4, 2020 10:43 AM
To: [email protected]
Subject: Re: [jmriusers] Error 303

?

Ross,
Good Morning.
The previously successfully read decoder was the BLI Paragon 3 and the programming track was attached to the PR3.
I did not change the preferences. It has/had worked in both locations. I didn't know there was a suitable preference and never gave it a second thought. Admittedly, the only Preference I ever changed was the File Location. I honestly don't remember why I changed it.
The USB port has not changed. I checked the port in Device Manager and all is well with the drivers and it recognizes the PR3 though it doesn't use that name.
JMRI 4.18 has worked for the BLI and other locomotives as well as previous versions.
Thanks for your help.
--
Richard Richter


 

Ross,
I checked the comm port and everything was as described. I even checked that the drivers were up to date.
The? preferences were spot-on. The defaults had no Internals checked. As for LocoNet, all were checked except Command Station.? Nothing I could do could get it to check.
The PS14 is 14.9 volts.
I had experienced the problem with BLI and contacted Digitrax and they told me to use the blast technique. This is the link to the article:

Thank-you,
--
Richard Richter


 

开云体育

Richard,

?

I had focused on getting your PR3? programming track working since you had indicated it worked before.?

?

“Blast’ programming is very effective for setting? the address.? However, “You will not be able to read back CVs using Blast Mode Programming.”

?

Not to worry.

?

Once the address is set, you can use DecoderPro to complete all further programming using ‘Programming on the Main’ (aka POM).? POM is fast and reliable; and with DecoderPro maintaining a record of your CV settings you don’t need to worry about the lack of CV ‘read-back.’

?

FWIW,? I rarely use the programming track; and if I do it is only to set an address.? I complete nearly 100% of my programming using POM.

?

The exception is LokSound decoders which ‘must’ be read first because there they don’t use a standard template for sound project development; each project is unique.? I use a LokProgrammer to read my LokSound decoders; then export the CV file then import it into DecoderPro.?

?

Good luck.? Let us know if you need any more help.

?

Ross

?

From: [email protected] <[email protected]> On Behalf Of rprdds24@...
Sent: Saturday, April 4, 2020 5:35 PM
To: [email protected]
Subject: Re: [jmriusers] Error 303

?

Ross,
I checked the comm port and everything was as described. I even checked that the drivers were up to date.
The? preferences were spot-on. The defaults had no Internals checked. As for LocoNet, all were checked except Command Station.? Nothing I could do could get it to check.
The PS14 is 14.9 volts.
I had experienced the problem with BLI and contacted Digitrax and they told me to use the blast technique. This is the link to the article:

Thank-you,
--
Richard Richter