Menu
▾
▴
Re: [Jmri-reports] No locomtovie detected (301)
|
From: Walter T. <wal...@gm...> - 2017-09-20 09:45:17
|
Trouble shooting programming track problems DCS is you Digital Command Station *GENERAL* If you get short detected on the programming track (309) remove the loco and try again. If you still get 309's isolate more. If you get no loco detected, short the programming track and you should get a different error. *Digitrax Systems:* 1. Verify connection between DCS and the Programming track: Using a hand held throttle read CV8. If this fails JMRI can not read or write CV’s on the programming track. 2. Verify connection between JMRI and the DCS. 2a *If using a Locobuffer interface adapter go to “LoconetMontior LocoNet stats” after clicking this the panel that displays should have some data in it. 2b.*If using an MS100, open Tool Power Control in JMRI and turn the track power On/Off. Then using a “Handheld Throttle” turn the track power On/Off assuring that the JMRI Power Control tool screen changes with the Handhelds cmds. . (note, this takes two power On’s to get the track power turned On) 3. Verify connection between JMRI and the programming track. 3a. With out a programming track booster. With no loco on the programming track.. Open the ‘Service-Mode” programmer, and click the “Read type from decoder.” The bottom of the screen should display “Stopping due to error, No locomotive detected (301), No acknowledge from locomotive (308).” If you short the programming track you should get a response of just No acknowledge from locomotive (308). Reconnect Using a “Handheld” throttle assure that CV8 can be read. 3b. With a PowerPax booster with no loco on the programming track or if the programming track is shorted, the error message will be “No Acknowledge from Locomotive (308)” If this all works JMRI should be able to read CV’s from this loco on the programming track. Digitrax PR3 in Stand alone mode: On the JMRI start pane click on Loconet and then Moniotor Loconet Stats. The screen that open should have numbers in the fields. With out a loco on the PR3’s programming track doing a read with a JMRI Service mode programmer should post on the bottom of the screen "Programmer error: No locomotive detected (301); No acknowledge from locomotive (308)". With the PR3’s programming track shorted doing a read with a JMRI Service mode programmer should post on the bottom of the screen " No acknowledge from locomotive (308)". If those three things happen you should be able to program decoders on the Programming track. We recommend a power supply for the PR3 of 16 to 18 VDC for best results. *EasyDCC* 1. Verify connection between the Digital Command Station (DCS) and the Programming track: Using the Command Station Read CV8. See pages 49 and 50 in your manual. 2. Verify connection between JMRI and the DCS. Select the EasyDCC tab on the first JMRI screen that opens. Select CommandMonitor , Then Send Command. In the send command screen that opens type V then click Send. You should then see the version number on the Command Monitor screen. 3. If this all works JMRI should be able to read CV’s from this loco on the programming track. *NCE Systems:* 1. Verify connection between DCS and the Programming track: Using a hand held throttle read CV8. If this fails JMRI can not read or write CV’s on the programming track. 2. Verify connection between JMRI and the DCS. When you first start DecoderPro or PanelPro the connection should display in black. If it doesn’t then the driver for your USB to serial adapter is not working or you have the wrong com port selected. If after a few seconds the connection displayed turns Red the connection to the command station from the serial adapter is not working. If the connection displayed stays black the System Console, under help, will display the rev of the software in the DCS and JMRI has a connection to the Command Station. If this all works JMRI should be able to read CV’s from this loco on the programming track The NCE Power Pro command station has a habit of "getting lost" when reading a large number of CVs with JMRI. The symptom is a rapidly flashing light on the command station and no communications. Considering that the ESU Function Map has 640 CVs (and the whole decoder has ~1,000 CVs) you are quite likely to see this problem with the Power Pro and ESU decoders. Fortunately there is a simple workaround: - VERY IMPORTANT: Do not quit JMRI or click on "Stop Reading". Do not touch JMRI. - Turn off the power to your NCE Power Pro command station. - Wait a few seconds. - Turn the NCE Power Pro back on again and wait patiently. - Eventually JMRI will reestablish contact with the Power Pro and continue reading. - Repeat the above procedure as often as required until JMRI says OK. - VERY IMPORTANT: Do a "Read Changes on Sheet" (or "Read Changes on All Sheets" if reading all sheets). JMRI will pick up the ones it missed when contact was lost. - Repeat the step immediately above as often as required until JMRI does not find anything to read (watch the status line at the bottom of the Sheet window). *Lenz Systems: * 1. 1. Verify connection between DCS and the Programming track. Using a hand held throttle read CV8. If this fails JMRI can not read or write CV”s on the programming track. Verify connection from digital command station and JMRI by selecting XPressnet>XpressnetSystemInformation. Click on “Get System Info”, all fields should come back filled in. If problems are encountered see *http://jmri.org/help/en/html/hardware/XPressNet/index.shtmlStep* <http://jmri.org/help/en/html/hardware/XPressNet/index.shtmlStep> . If this all works JMRI should be able to read CV’s from this loco on the programming track *SPROG* Verify connection. Main menu bar should have SPROG. Click on SPROG, then "Get SPROG Firmware Version". You should see something like"SPROG II USB v.x". If you get "Timeout talking to SPROG" you do not have connection. For programming the System manufacturer in the JMRI Preferences file needs to be set for SPROG DCC and SPROG as the System connection to program decoders. (If the System connection is set to "SPROG Command Station" you can control up to 16 locomotives, but may only "program on the main".) With no loco on the track, open the `Service-Mode" programmer, and click the "Read type from decoder." The bottom of the screen should display "Stopping due to error, No locomotive detected (301)." If you short the programming track you should see "Found mfg -1 version -1; no such manufacturer defined". Also on the bottom you should se a 309 error. *Updated 201611213 Walter71342* On Tue, Sep 19, 2017 at 10:40 PM, Werner Kroebig <wjk...@gm...> wrote: > I set the baud rate in JMRI connections to 19200, saved that, exited JMRI, > restarted the computer, restarted JMRI and verified that the baud rate was > still set at 19200 in JMRI connection (it was) and verified that the com > port setting was still at 19200 (it was). It then tried to read the > decoder, this time I got a error of time out talking to the command station > (306). Suggestions? > > Sent from my iPhone > > > On Sep 19, 2017, at 8:17 PM, Werner Kroebig <wjk...@gm...> wrote: > > > > Just found it, trying now. > > > > Sent from my iPhone > > > >> On Sep 19, 2017, at 8:16 PM, Werner Kroebig <wjk...@gm...> > wrote: > >> > >> I have jumper 3 & 4 on to make the baud rate 19200 as required for > PowerCab v1.65. I was also able to set the port settings in Windows at > 19200 bits per second (left data bits at 8, Parity at none, stop bits 1, > flow control none). I can't seem to find where in DecoderPro an option > exists to change the baud rate. Edit/Preferences/Connections does seem to > have an option to change this. Am I looking in the wrong place? > >> > >> Sent from my iPhone > >> > >>> On Sep 19, 2017, at 6:51 PM, Ken Cameron <kca...@tw...> > wrote: > >>> > >>> The session.log file shows that JMRI never got a meaningful reply from > the > >>> USB. Generally there was a timeout but sometimes it was garbage. This > can be > >>> due to baud rate being wrong, a bad cable, or a bad board. You didn't > say > >>> what the jumpers on the USB are set for. Telling if you had jumpers on > or > >>> off would help. > >>> > >>> I suggest you change the baud rate in the JMRI connection details to > 19,200. > >>> Try this without any other changes. > >>> > >>> -Ken Cameron, Member JMRI Dev Team > >>> www.jmri.org > >>> www.fingerlakeslivesteamers.org > >>> www.cnymod.com > >>> www.syracusemodelrr.org > >>> > >>> > >>> > >>> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jmri-reports mailing list > Jmr...@li... > https://lists.sourceforge.net/lists/listinfo/jmri-reports > |
