开云体育

Creeping locomotives (was Re: DigiTrax DCS100 missing LocoNet packets

Bob Jacobsen All Messages By This Member #162140 Could I ask some more info on these? With the creeping locomotives, what kinds of decoders do they have? On Jul 15, 2019, at 9:08 AM, Don <donmcgil@...> wrote: BUG alert - While I am talking about the Monitor Slots Window I have noticed that the "Estop All" button sets the locos to a speed of 1 not 0. As a result they start creeping and eventually cause issues (shorts at turnouts, collisions derailments etc). -- Bob Jacobsen rgj1927@...
Steve_G All Messages By This Member #162142 Hi Speed step 1 means Emergency Stop (i.e. Stop NOW and ignore deceleration settings). Which dcc system / command station are you using? Steve G. toggle quoted message Show quoted text On July 28, 2019 5:20:38 PM EDT, Bob Jacobsen <rgj1927@...> wrote: Could I ask some more info on these? With the creeping locomotives, what kinds of decoders do they have? On Jul 15, 2019, at 9:08 AM, Don <donmcgil@...> wrote: BUG alert - While I am talking about the Monitor Slots Window I have noticed that the "Estop All" button sets the locos to a speed of 1 not 0. As a result they start creeping and eventually cause issues (shorts at turnouts, collisions derailments etc). -- Bob Jacobsen rgj1927@... -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Steve_G All Messages By This Member #162144 Hi Missed the title. If the throttle is being shared between a real digitrax throttle and JMRI, or is just a real throttle, if you E-stop it in JMRI the real throttle will just set the speed back to where it was after a few moments. Its best not to share throttles between JMRI and a Digitrax Throttle, and Dt500/402? with expanded slots enabled, and a dcs240, dcs52 and and dcs210 can actually block JMRI from controlling the loco. Steve G.
Don All Messages By This Member #162176 Hi Bob The Locos I noticed this with were fitted with ESU V4 LokSound decoders. ?But I now believe the issue I saw was probably just another manifestation of my fundamental problem which is a DCS100 which occasionally misses a LocoNet packet, The problems I have seen are when a LocoNet command such as turn a Horn On/Off or to Start/Stop a locomotive is missed when running auto trains. Missing a Horn start is not obvious, ?Missing a Horn stop is very obvious. ?Issuing a Monitor Slots command immediately after a loco does not turn off its horn shows that F2 is still on in the DCS100 but the F2 off command was sent to LocoNet (as seen on a second JMRI running on a second computer eaves dropping onto the LocoNet via a second PR4). A missed Loco start (Set speed of loco x to YY) command is evidenced by an auto train not starting a Transit or following a Pause until another Set speed of loco in slot x command is sued onto locket. ?Again refreshing Monitor slots shows the DCS100 did not get the Set loco speed command. A missed Loco stop (Set speed of loco x to 0) command generally breaks auto trains, results in memory leaks and eventually a processor core running parts of JMRI goes to 100% and JMRI freezes for a period of time. ?A JMRI restart is required to re-establish auto train operation. ?Again I have confirmed that JMRI sent the command to LocoNet and that the DCS100 did not see it. I have separated the layout control LocoNet (turnouts, block detection and signalling) from the DCS100 LocoNet ?(i.e. LocoNet and LocoNet2) and still observed the same behaviour with a similar frequency of occurrence. ?Tonight I was able to carry out the ultimate test using a borrowed DCS100. ?So far I have run for over 5 hours without any drop LocoNet commands with the system configured back to a single LocoNet bus. So it looks like my DCS100 has issues not seen on another. ? Thanks? Don McG
leo pesce All Messages By This Member #162181 What Don is explaining, I have seen it also on our layout, when we were running with Digitrax throttles (we have since replaced the throttles with NCE, because of the radio issues). We still program engines with Digitrax, and occasionally as I test the engine after programming (the program track has a switch to change from programming track to main line) using a DT400D (plugged in) when I turn the knob for 00, I find that the throttle goes back to 02 or 07, or never reaches 00. When this occurs, to set it back to 00 I have to advance the throttle up a few steps, and then slowly? At first I thought the problem was with the encoder knob in the throttle, so I changed it to another throttle (we still have a dozen of these DT400s), but the problem persists, occasionally. So I know it is not the throttle. Today the DCS200 we use, is for programming only, nothing else, as anything that was Loconet, is now LCC (turnouts, sensors, signals). BTW, our DCS200s (we have a few) are very old, going back to 18-20 years ago, so it could be these command stations are starting to decay a bit (?). Cheers Leo P toggle quoted message Show quoted text On Mon, Jul 29, 2019 at 9:56 AM Don <donmcgil@...> wrote: Hi Bob The Locos I noticed this with were fitted with ESU V4 LokSound decoders.? But I now believe the issue I saw was probably just another manifestation of my fundamental problem which is a DCS100 which occasionally misses a LocoNet packet, The problems I have seen are when a LocoNet command such as turn a Horn On/Off or to Start/Stop a locomotive is missed when running auto trains. Missing a Horn start is not obvious, ?Missing a Horn stop is very obvious.? Issuing a Monitor Slots command immediately after a loco does not turn off its horn shows that F2 is still on in the DCS100 but the F2 off command was sent to LocoNet (as seen on a second JMRI running on a second computer eaves dropping onto the LocoNet via a second PR4). A missed Loco start (Set speed of loco x to YY) command is evidenced by an auto train not starting a Transit or following a Pause until another Set speed of loco in slot x command is sued onto locket.? Again refreshing Monitor slots shows the DCS100 did not get the Set loco speed command. A missed Loco stop (Set speed of loco x to 0) command generally breaks auto trains, results in memory leaks and eventually a processor core running parts of JMRI goes to 100% and JMRI freezes for a period of time.? A JMRI restart is required to re-establish auto train operation.? Again I have confirmed that JMRI sent the command to LocoNet and that the DCS100 did not see it. I have separated the layout control LocoNet (turnouts, block detection and signalling) from the DCS100 LocoNet ?(i.e. LocoNet and LocoNet2) and still observed the same behaviour with a similar frequency of occurrence.? Tonight I was able to carry out the ultimate test using a borrowed DCS100.? So far I have run for over 5 hours without any drop LocoNet commands with the system configured back to a single LocoNet bus. So it looks like my DCS100 has issues not seen on another. ? Thanks? Don McG

Previous Topic Next Topic