开云体育

Hi Jon,

I don't really see it as *much* of a problem. After all, any update
possibility is really a free improvement to a poduct already paid for in
the past (well, unless paid for, obviously). If that requires something you
don't have, I'm sure the factory can do it for you, but then you'll have to
send it in, just as if there were a defect. On the whole, I am rather
impressed with how many products these days can be updated. It isn't as if
we have any right to improvements post-buy, so I am generally rather happy.

An unwelcome side-effect is thatt sometimes product quality is allowed to
slip, because fixing errors in a laer update is a possibility. I'm not very
pleased if I buy something and have to update it first in order to make it
work. That's just sloppy. It lands the end user with part of a task that
should be the manufacturer's: testing.

Two sides to the coin.
Wouter

On 15 August 2017 at 15:51, Jon Miller atsfus@... [jmriusers] <
jmriusers@...> wrote:

/On 8/15/2017 12:48 AM, Mick Moignard mick@... [jmriusers]
wrote://
/

/1. Ensure that the DCS240 is at the latest firmware level, 0.3, Feb 28
2017. If it isn't, all sorts of stuff just doesn't work properly
(extended slots, loco functions, bad packets on the track, and index
CV programming were some of them). /

While for the most part I love modern technology, HOWEVER if a
product has to have firmware updated, from the time you purchase it, and
the only way to do that is buy another product from the company I see a
big problem. All my stereo and computer equipment can be updated
either from the net or they will send a CD to do it. If DCC
manufactures can't do the same there is a problem or don't other see
this problem?

--
Jon Miller
For me time stopped in 1941
Digitrax Chief/Zephyr systems, JMRI User
NMRA Life member #2623
Member SFRH&MS

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

/On 8/15/2017 12:48 AM, Mick Moignard mick@... [jmriusers]
wrote://
/

/1. Ensure that the DCS240 is at the latest firmware level, 0.3, Feb 28
2017. If it isn't, all sorts of stuff just doesn't work properly
(extended slots, loco functions, bad packets on the track, and index
CV programming were some of them). /

While for the most part I love modern technology, HOWEVER if a
product has to have firmware updated, from the time you purchase it, and
the only way to do that is buy another product from the company I see a
big problem. All my stereo and computer equipment can be updated
either from the net or they will send a CD to do it. If DCC
manufactures can't do the same there is a problem or don't other see
this problem?

--
Jon Miller
For me time stopped in 1941
Digitrax Chief/Zephyr systems, JMRI User
NMRA Life member #2623
Member SFRH&MS

Thanks Dave, much appreciated.Mike.

From: "Dave Heap dgheap@... [jmriusers]" <jmriusers@...>
To: jmriusers@...
Sent: Tuesday, 15 August 2017, 11:31
Subject: Re: [jmriusers] Consist lights, CV21 and CV22 values. Reminder please.

? While the NMRA standards define the bit mappings of CVs 21 & 22, various manufacturers have modified and extended these, so you need to rely on the Consist pane for each roster entry.

The overall principle is that F keys that control consist-wide functions (sound, brakes, etc.) should have the appropriate bit set in CV21 or CV22 so all locos respond to them.

As far as F keys that control lead-only functions (such as headlight, horn, etc.) are concerned, what you set in CV21 or CV22 depends on your DCC system:
- For an NCE system, you leave these bits cleared in EVERY loco. You drive the consist by selecting the lead or rear loco address. The command station takes care of redirecting speed commands to the consist address and sends function commands to both lead and consist addresses. This achieves the desired result and you never need to change CV21 or CV22 after initial setup, irrespective of whether a loco is mid-consist or lead.
- For some other DCC systems, you have to set these bits in the lead loco only. You drive the consist by selecting consist address. The lights, horn etc. will work as desired. But you will need to reprogram CV21 and/or CV22 if your loco changes position in the consist.
- Other DCC systems do it differently. I cannot advise on these.
--
Dave in Australia

On 15 Aug 2017, at 7:23 PM, mikepayne1402@... [jmriusers] <jmriusers@...> wrote:

Just need a reminder for CV setting for intermediate units within a consist. I know I have it somewhere, just can't find it!

#yiv7841882015 #yiv7841882015 -- #yiv7841882015ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv7841882015 #yiv7841882015ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv7841882015 #yiv7841882015ygrp-mkp #yiv7841882015hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv7841882015 #yiv7841882015ygrp-mkp #yiv7841882015ads {margin-bottom:10px;}#yiv7841882015 #yiv7841882015ygrp-mkp .yiv7841882015ad {padding:0 0;}#yiv7841882015 #yiv7841882015ygrp-mkp .yiv7841882015ad p {margin:0;}#yiv7841882015 #yiv7841882015ygrp-mkp .yiv7841882015ad a {color:#0000ff;text-decoration:none;}#yiv7841882015 #yiv7841882015ygrp-sponsor #yiv7841882015ygrp-lc {font-family:Arial;}#yiv7841882015 #yiv7841882015ygrp-sponsor #yiv7841882015ygrp-lc #yiv7841882015hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv7841882015 #yiv7841882015ygrp-sponsor #yiv7841882015ygrp-lc .yiv7841882015ad {margin-bottom:10px;padding:0 0;}#yiv7841882015 #yiv7841882015actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv7841882015 #yiv7841882015activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv7841882015 #yiv7841882015activity span {font-weight:700;}#yiv7841882015 #yiv7841882015activity span:first-child {text-transform:uppercase;}#yiv7841882015 #yiv7841882015activity span a {color:#5085b6;text-decoration:none;}#yiv7841882015 #yiv7841882015activity span span {color:#ff7900;}#yiv7841882015 #yiv7841882015activity span .yiv7841882015underline {text-decoration:underline;}#yiv7841882015 .yiv7841882015attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv7841882015 .yiv7841882015attach div a {text-decoration:none;}#yiv7841882015 .yiv7841882015attach img {border:none;padding-right:5px;}#yiv7841882015 .yiv7841882015attach label {display:block;margin-bottom:5px;}#yiv7841882015 .yiv7841882015attach label a {text-decoration:none;}#yiv7841882015 blockquote {margin:0 0 0 4px;}#yiv7841882015 .yiv7841882015bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv7841882015 .yiv7841882015bold a {text-decoration:none;}#yiv7841882015 dd.yiv7841882015last p a {font-family:Verdana;font-weight:700;}#yiv7841882015 dd.yiv7841882015last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv7841882015 dd.yiv7841882015last p span.yiv7841882015yshortcuts {margin-right:0;}#yiv7841882015 div.yiv7841882015attach-table div div a {text-decoration:none;}#yiv7841882015 div.yiv7841882015attach-table {width:400px;}#yiv7841882015 div.yiv7841882015file-title a, #yiv7841882015 div.yiv7841882015file-title a:active, #yiv7841882015 div.yiv7841882015file-title a:hover, #yiv7841882015 div.yiv7841882015file-title a:visited {text-decoration:none;}#yiv7841882015 div.yiv7841882015photo-title a, #yiv7841882015 div.yiv7841882015photo-title a:active, #yiv7841882015 div.yiv7841882015photo-title a:hover, #yiv7841882015 div.yiv7841882015photo-title a:visited {text-decoration:none;}#yiv7841882015 div#yiv7841882015ygrp-mlmsg #yiv7841882015ygrp-msg p a span.yiv7841882015yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv7841882015 .yiv7841882015green {color:#628c2a;}#yiv7841882015 .yiv7841882015MsoNormal {margin:0 0 0 0;}#yiv7841882015 o {font-size:0;}#yiv7841882015 #yiv7841882015photos div {float:left;width:72px;}#yiv7841882015 #yiv7841882015photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv7841882015 #yiv7841882015photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv7841882015 #yiv7841882015reco-category {font-size:77%;}#yiv7841882015 #yiv7841882015reco-desc {font-size:77%;}#yiv7841882015 .yiv7841882015replbq {margin:4px;}#yiv7841882015 #yiv7841882015ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv7841882015 #yiv7841882015ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv7841882015 #yiv7841882015ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv7841882015 #yiv7841882015ygrp-mlmsg select, #yiv7841882015 input, #yiv7841882015 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv7841882015 #yiv7841882015ygrp-mlmsg pre, #yiv7841882015 code {font:115% monospace;}#yiv7841882015 #yiv7841882015ygrp-mlmsg * {line-height:1.22em;}#yiv7841882015 #yiv7841882015ygrp-mlmsg #yiv7841882015logo {padding-bottom:10px;}#yiv7841882015 #yiv7841882015ygrp-msg p a {font-family:Verdana;}#yiv7841882015 #yiv7841882015ygrp-msg p#yiv7841882015attach-count span {color:#1E66AE;font-weight:700;}#yiv7841882015 #yiv7841882015ygrp-reco #yiv7841882015reco-head {color:#ff7900;font-weight:700;}#yiv7841882015 #yiv7841882015ygrp-reco {margin-bottom:20px;padding:0px;}#yiv7841882015 #yiv7841882015ygrp-sponsor #yiv7841882015ov li a {font-size:130%;text-decoration:none;}#yiv7841882015 #yiv7841882015ygrp-sponsor #yiv7841882015ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv7841882015 #yiv7841882015ygrp-sponsor #yiv7841882015ov ul {margin:0;padding:0 0 0 8px;}#yiv7841882015 #yiv7841882015ygrp-text {font-family:Georgia;}#yiv7841882015 #yiv7841882015ygrp-text p {margin:0 0 1em 0;}#yiv7841882015 #yiv7841882015ygrp-text tt {font-size:120%;}#yiv7841882015 #yiv7841882015ygrp-vital ul li:last-child {border-right:none !important;}#yiv7841882015



[Non-text portions of this message have been removed]

Further to Mick's point number 4:

" If you get a 302 programmer busy error that won't go away (the DCS240 programmer is prone to crashing), just power off the DCS240, wait 15 seconds and power on again to clear it, then repeat the DP operation."

This works, as written, if you are using something OTHER than the DCS240's USB connection (DCS240's internal PR3 functionality). Mick stated that he doesn't use the DCS240 USB connection, so the instruction works correctly for him.

But, if you are using the DCS240-internal PR3, the act of removing the DCS240 power may not necessarily clear the DCS240's USB functionality, which may be what is "locking up" and causing the JMRI "302 programmer busy" error. With this scenario, clearing up a locked-up programming track may require removing DCS240 power AND disconnecting the USB cable from the DCS240. But disconnecting the USB cable likely "confuses" the mechanism JMRI uses to talk to the DCS240. And that likely means that you will need to quit JMRI. Once DCS240 power is restored, you may re-connect the USB cable and re-start JMRI.

Regards,
Billybob

While the NMRA standards define the bit mappings of CVs 21 & 22, various manufacturers have modified and extended these, so you need to rely on the Consist pane for each roster entry.

The overall principle is that F keys that control consist-wide functions (sound, brakes, etc.) should have the appropriate bit set in CV21 or CV22 so all locos respond to them.

As far as F keys that control lead-only functions (such as headlight, horn, etc.) are concerned, what you set in CV21 or CV22 depends on your DCC system:
- For an NCE system, you leave these bits cleared in EVERY loco. You drive the consist by selecting the lead or rear loco address. The command station takes care of redirecting speed commands to the consist address and sends function commands to both lead and consist addresses. This achieves the desired result and you never need to change CV21 or CV22 after initial setup, irrespective of whether a loco is mid-consist or lead.
- For some other DCC systems, you have to set these bits in the lead loco only. You drive the consist by selecting consist address. The lights, horn etc. will work as desired. But you will need to reprogram CV21 and/or CV22 if your loco changes position in the consist.
- Other DCC systems do it differently. I cannot advise on these.
--
Dave in Australia

Hi All,
Just need a reminder for CV setting for intermediate units within a consist. I know I have it somewhere, just can't find it!
Many thanks,
Mike.

Having had a lot of trouble myself with a DCS240, and long chains of
discussions here and with Digitrax, I'd suggest to you from bitter
experience:

1. Ensure that the DCS240 is at the latest firmware level, 0.3, Feb
28 2017. If it isn't, all sorts of stuff just doesn't work properly
(extended slots, loco functions, bad packets on the track, and index CV
programming were some of them).
2. Ensure that your DP/JMRI is 4.8 or above. There were changes in
this version specifically to deal with the oddities (not documented by
Digitrax) of the DCS240 programming process, and a couple of new
preferences that might help. These are Preferences/Roster/Programmer, and
took at the last two preference ticks. Allow Caching will improve
programming speed but should be used with extreme care and understanding:
if you don't have that, don't select it. Confirm CV writes will slow
down programming speed but will decrease the already small possibility of
errors. I run with neither selected, most of the time/
3. I find that programming operations with a CS240 work better when
a: the track power is turned on (it assists Loconet stability!!!!) and
also to have a Soundtraxx PTB100 in the mix. Some decoders (Loksound 4
are one) just program more reliably with DCS240 in this configuration, and
particularly when a PTB100 is in use.
4. If you get a 302 programmer busy error that won't go away (the
DCS240 programmer is prone to crashing), just power off the DCS240, wait
15 seconds and power on again to clear it, then repeat the DP operation.
5. Be patient. DCS240 read All Sheets takes about twice as long as
DCS100 on a decoder like a Tsunami-2 or Loksound 4 with lots of indexed
Cvs. Each read of one of these CVs takes one or two writes to the index
CVs before it can read, and the DCS240 takes forever to do a any sort of
CV write. The belief, undocumented by Big D, is that it does a read-check
on every write. That's what the Allow Caching change is for; it supresses
the Index writes by DP if DP thinks that the index CV is already set
correctly. This is OK ***only*** if the decoder does not change the index
CV while reading or writing, If you don't know this for certain, don't
use this new preference.

I use a Locobuffer/Loconet connection (see item 3 above). I have used the
USB connection option, and found that has its own quirks, but as I've not
used it recently, I can't recall what they are, but I do recall that it
also wasn't trouble-free,

Mick

______________________________________________________________________
Mick Moignard
Specialising in DCC Sound
p: +44 7774 652504
e: mick@...
skype: mickmoignard
IBM Notes and Domino: still has what it takes as an App Dev and
Collaboration platform.

Hi Bob

Some more info about what I've done using current 4.9.2:

After removing the previous decoderindex.xml from my user's folder (created with 4.9.1 when I updated the Zimo V36 Plus profile), and seeing that I was able to open roster entru or add a new entry:

1) I then recreated the decoderindex, thus creating a new "local" decoderindex.xml,
2) I was able to close then start JMRI again,
3) I was able to open roster, add a new entry (see below), update decoder definitions, rebuilt roster....
3) So all seems fine BUT:

I found a small issue with the 4.9.2: when creating a new roster entry, it doesn't show up in the roster.... I had to rebuilt the roster to see this new entry in my roster.

When using your latest built #1765 (4.9.3....) once a new entry is created, it shows in the roster.

Alain from Paris

Bob: I don't see where I have made any script references to jmridefaults.py, but renaming jmri_bindings.py to that name resolved my issue. Thank you (again). I had to change some script references to decodeJmriFilename(name) to jmri.util.FileUtil.getExternalFilename(name) to resolve some secondary errors, because that definition reference was buried in the original jmridefaults.py. I probably should have done that long ago anyway. And I have jython.exec=False and my scripts are under 100,000 characters, if that matters.
Randy

You need to go to Preferences->Connections and select a valid serial port from those available. The valid name for a SPROG connection will be something like cu.usbmodemxxxx (not the tty.usbmodemxxxx).

If you can see the SPROG in About this Mac, that merely indicates the SPROG is plugged in correctly. It doesn't indicate that macOS has loaded a driver and created a port.

If you can't see a valid port in JMRI, open the Applications folder and from there find and open the app called "Terminal". Into the terminal window that opens, copy and paste the following command (exactly as it is, punctuation and spaces):

while : ;do clear;ls -lt /dev|head;i=$((i+1));echo $i;sleep 1;done

Press ENTER and the window should show around 10 lines, with an incrementing counter at the bottom. Unplug the SPROG and wait a few seconds. Then replug the SPROG and wait a few seconds. The two entries at the top will be the SPROG ports (cu & tty). If nothing changes, your Mac is not loading a driver for the SPROG.
--
Dave in Australia

Bob,
I installed 4.9.2 again. Then I checked for the decoderindex.xml file and I did have that file under My_JMRI_Railroad. I moved it out of there then launched DecoderPro. I put it through lots of paces and for what I do, it has been solid and fast as expected.
I dug around my various backups. I backup before each update. It seems that file was not there when I updated to 4.7.8.
I think - based on the time and date stamps from my downloads and my backups - I think it came along when I installed and re-indexed a Soundtraxx decoder update file from this user group page .
Hope that info helps you figure it all out.
4.9.2 is running great now.
Thank you,
Tom Wilson

On Aug 14, 2017, at 11:33 AM, 'Ken Cameron' kcameron@... [jmriusers] <jmriusers@...> wrote:

I'm launching ok, but opening an entry in the roster takes a very long time
or never happens for some entries (>5 minutes).

Might be more than one problem.

Could you try the #1765 (or later) installer from please? It’s building now, should be done in about 20 minutes. Thanks.

Bob
--
Bob Jacobsen
jacobsen@... +1-510-708-5988 AIM, Skype JacobsenRG

Will look tomorrow when I get to club

Sent from Yahoo Mail on Android

User with problems with a DCS240 and a locobuffer. I would like to know what the version number of the loco buffer is.. Its the first number when you select Loconet>LoconetStats. Walt

If you have scripts referring to “jmridefaults.py”, please replace that with a reference to “jmri_bindings.py”.

Or you could copy the “jmri_bindings.py” file to be named “jmridefaults.py”. But the first approach is better.

Bob

On Aug 14, 2017, at 6:28 PM, randomburnout@... [jmriusers] <jmriusers@...> wrote:

Upgraded from 4.9.1 to 4.9.2 and now it does not like this line from jmridefaults.py and stops dead before showing any of my Layout Editor Panels. Any thoughts?
2017-08-14 21:18:35,692 script.JmriScriptEngineManager ERROR - Exception creating jython system objects [main]

javax.script.ScriptException: AttributeError: type object 'jmri.InstanceManager' has no attribute 'signalHeadManagerInstance' in <script> at line number 21

--
Bob Jacobsen
jacobsen@... +1-510-708-5988 AIM, Skype JacobsenRG

My programing track is less than 3ft away. We upgrade from a dcs 200. But we also have 5 sections each control 30 ft at max. My DCS240 is the main and controls antennas, programing track, and a 2 track main roughly 8ft long.
Sent from Yahoo Mail on Android

I would like to add some interesting observations here, I also hooked up a new dcs240 from a dcs 100.

Initially I had a 30 ft run from the command station on 12 gauge running to a dcc specialties programming booster with the laptop hooked up to a up5.

After hooking up the dcs 240 I first tried the locobuffer configuration with no luck kept getting a programmer was busy error. Next I removed the power booster and tried a 30ft usb cable with a repeater tied in to it with the same problem.

At the end of the day I has to use a short usb and a make shift programming track thst is now within 5 feet if the command station in order to not get a programmer busy error......tried just about every combination between the locobuffer and built in programmer in the command station.

Seems to be an issue with long runs of wire and the command station/Jmri being confused.

Tristan

I'm running 4.8..,

I get that error when the PR3 is in the wrong mode on my home set up with a DCS200.

Our club uses the 240 just for running the layout so we haven't run in to this with it. So not sure how to change modes like I can with a stand alone PR3.

David Klemm
Sent from my iPhone 7 Plus
________________________________
From: jmriusers@... <jmriusers@...> on behalf of Ron Merrill ronmerrill69@... [jmriusers] <jmriusers@...>
Sent: Monday, August 14, 2017 8:34:16 PM
To: jmriusers@...
Subject: Re: [jmriusers] DCS240 JMRI



Will need to get back with you, but I installed newest version that was not a test version, I think 4.8 production release

Sent from Yahoo Mail on Android

On Mon, Aug 14, 2017 at 9:28 PM, DAVID KLEMM davidklemm7511@... [jmriusers]<jmriusers@...> wrote: What version of JMRI are you running? The 240 was addressed around 4.7.2.

David Klemm
Sent from my iPhone 7 Plus
________________________________
From: jmriusers@... <jmriusers@...> on behalf of ronmerrill69@... [jmriusers] <jmriusers@...>
Sent: Monday, August 14, 2017 7:12:32 PM
To: jmriusers@...
Subject: [jmriusers] DCS240 JMRI

I installed a DCS240 on our Club layout. I did my research on the new system, reading online that the DCS240 used the same drivers as the PR3, so I installed just prior to a week of vacation. the programing track was reading and operating normally, main line was operating normally, on my return fellow club members reported that programing track was not working. I rechecked configuration. all settings were as I had set them, it has done a couple of things, 1) it read each cv then stopped (306) then next cv, same thing. 2) it completely stopped reading (306). fixes uninstall/redo drivers. what does everyone else think

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

------------------------------------

------------------------------------

------------------------------------

Yahoo Groups Links







[Non-text portions of this message have been removed]

Did you do the update v.3 on the DCs240?

On Aug 14, 2017, at 8:12 PM, ronmerrill69@... [jmriusers] <jmriusers@...> wrote:

I installed a DCS240 on our Club layout. I did my research on the new system, reading online that the DCS240 used the same drivers as the PR3, so I installed just prior to a week of vacation. the programing track was reading and operating normally, main line was operating normally, on my return fellow club members reported that programing track was not working. I rechecked configuration. all settings were as I had set them, it has done a couple of things, 1) it read each cv then stopped (306) then next cv, same thing. 2) it completely stopped reading (306). fixes uninstall/redo drivers. what does everyone else think

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]