开云体育

Dan,
I'm not so sure Norman has a case of "a printer that doesn't quite work right with JMRI" so much as it might be that "JMRI (or Java?) doesn't work quite right with some printers".

I opened a bug a while back about 2-sided printing. When printing a manifest with double-sided set as the default for the printer, JMRI simply does not honor the 2-sided option without some manual intervention:

<>

As described in that bug, I had the same issue with two different printers from two different manufacturers so it's not likely the printer. The manual interventions to make it work differed slightly, but the bottom line in both cases was that JMRI ignored the default settings for that particular printer.

It sounds like Norman may have hit another variation of this same bug, with JMRI refusing to honor the printer's default settings.

Steve
"Breezlys".

---In jmriusers@..., <daboudreau@...> wrote :

Norman,

Instead of sending the file to the printer, try the "Microsoft XPS Document Writer" and send the output to me to review. You might have a printer that doesn't quite work right with JMRI.


Dan


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

Yes no matter how the xpressnet is connected (USB or xpressnet) you get the same functionality. POM and accessories (up to 256) also work. I'm still experimenting and don't use it as a main system myself at present. We found a lot of this out at a recent modular meeting where we had Loconet, Xpressnet and wifi throttles connected connected to a DR5000. The Lenz throttles stopped adding new locos with no reason showing. It wasn't until someone noticed slot full on a Digitrax throttle that we realisied the problem. The Lenz data base didn't work, but running Decoderpro with a Digitrax connection we could access it under the Loconet monitor slots, where we could clear unused slots and the Lenz throttles worked again.

It did prove the DR5000 works with both systems, running both types of boosters and throttles, just make sure railcom is off (on by default) when using boosters without it, that caused problems all weekend! We didn't figure it out until later when trying to reproduce the problem. I have tested the RS feedback bus and that works correctly on the DR5000, so long as the address offset is set to zero it matches a Lenz system.


A while back I did enquire about Lenz consisting and was told it was in the next update, but wasn't!
I now consist using CV's 29 & 19, which also gets past the Lenz no consist function problem when running on Lenz.
The system is still being developed and is easily updated from a download via the configuration software.


Mike

Art, if the phones have Wi-Fi you can use the Wi-Fi to install the app. I have a smart phone that is not activated as a phone but I can use Wi-Fi to connect to the internet using my router. Hope this helps,
Al Babinsky


Sent from Alto

/On 6/22/2017 8:44 AM, yooper_from_49827@... [jmriusers] wrote://
/

/Has anyone tried using old cell phones and WiThrottle? The cell phones
would not be activated to any cellular service provider but would
simply use the WiFi connection. One problem would be how to get the
WiThrottle or Engine Driver app installed./

I have and they work fine. Most/all of those phones still have
internet. Just park next to the coffee shop (or go have coffee) and
download.

I got a couple on eBay for 15/20 bucks. Price might be higher now.

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

Can you be more specific as to it's specs and the Dell model? Not only
could we then tell you if it will run, if you want or need to upgrade it I
could point you at the parts that will work for you.

Mike Piazza

Mike, I am traveling for work. When I get home I will get the specs on the laptop.Thanks
Perry #yiv0035466149 #yiv0035466149 -- #yiv0035466149ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv0035466149 #yiv0035466149ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv0035466149 #yiv0035466149ygrp-mkp #yiv0035466149hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv0035466149 #yiv0035466149ygrp-mkp #yiv0035466149ads {margin-bottom:10px;}#yiv0035466149 #yiv0035466149ygrp-mkp .yiv0035466149ad {padding:0 0;}#yiv0035466149 #yiv0035466149ygrp-mkp .yiv0035466149ad p {margin:0;}#yiv0035466149 #yiv0035466149ygrp-mkp .yiv0035466149ad a {color:#0000ff;text-decoration:none;}#yiv0035466149 #yiv0035466149ygrp-sponsor #yiv0035466149ygrp-lc {font-family:Arial;}#yiv0035466149 #yiv0035466149ygrp-sponsor #yiv0035466149ygrp-lc #yiv0035466149hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv0035466149 #yiv0035466149ygrp-sponsor #yiv0035466149ygrp-lc .yiv0035466149ad {margin-bottom:10px;padding:0 0;}#yiv0035466149 #yiv0035466149actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv0035466149 #yiv0035466149activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv0035466149 #yiv0035466149activity span {font-weight:700;}#yiv0035466149 #yiv0035466149activity span:first-child {text-transform:uppercase;}#yiv0035466149 #yiv0035466149activity span a {color:#5085b6;text-decoration:none;}#yiv0035466149 #yiv0035466149activity span span {color:#ff7900;}#yiv0035466149 #yiv0035466149activity span .yiv0035466149underline {text-decoration:underline;}#yiv0035466149 .yiv0035466149attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv0035466149 .yiv0035466149attach div a {text-decoration:none;}#yiv0035466149 .yiv0035466149attach img {border:none;padding-right:5px;}#yiv0035466149 .yiv0035466149attach label {display:block;margin-bottom:5px;}#yiv0035466149 .yiv0035466149attach label a {text-decoration:none;}#yiv0035466149 blockquote {margin:0 0 0 4px;}#yiv0035466149 .yiv0035466149bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv0035466149 .yiv0035466149bold a {text-decoration:none;}#yiv0035466149 dd.yiv0035466149last p a {font-family:Verdana;font-weight:700;}#yiv0035466149 dd.yiv0035466149last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv0035466149 dd.yiv0035466149last p span.yiv0035466149yshortcuts {margin-right:0;}#yiv0035466149 div.yiv0035466149attach-table div div a {text-decoration:none;}#yiv0035466149 div.yiv0035466149attach-table {width:400px;}#yiv0035466149 div.yiv0035466149file-title a, #yiv0035466149 div.yiv0035466149file-title a:active, #yiv0035466149 div.yiv0035466149file-title a:hover, #yiv0035466149 div.yiv0035466149file-title a:visited {text-decoration:none;}#yiv0035466149 div.yiv0035466149photo-title a, #yiv0035466149 div.yiv0035466149photo-title a:active, #yiv0035466149 div.yiv0035466149photo-title a:hover, #yiv0035466149 div.yiv0035466149photo-title a:visited {text-decoration:none;}#yiv0035466149 div#yiv0035466149ygrp-mlmsg #yiv0035466149ygrp-msg p a span.yiv0035466149yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv0035466149 .yiv0035466149green {color:#628c2a;}#yiv0035466149 .yiv0035466149MsoNormal {margin:0 0 0 0;}#yiv0035466149 o {font-size:0;}#yiv0035466149 #yiv0035466149photos div {float:left;width:72px;}#yiv0035466149 #yiv0035466149photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv0035466149 #yiv0035466149photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv0035466149 #yiv0035466149reco-category {font-size:77%;}#yiv0035466149 #yiv0035466149reco-desc {font-size:77%;}#yiv0035466149 .yiv0035466149replbq {margin:4px;}#yiv0035466149 #yiv0035466149ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv0035466149 #yiv0035466149ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv0035466149 #yiv0035466149ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv0035466149 #yiv0035466149ygrp-mlmsg select, #yiv0035466149 input, #yiv0035466149 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv0035466149 #yiv0035466149ygrp-mlmsg pre, #yiv0035466149 code {font:115% monospace;}#yiv0035466149 #yiv0035466149ygrp-mlmsg * {line-height:1.22em;}#yiv0035466149 #yiv0035466149ygrp-mlmsg #yiv0035466149logo {padding-bottom:10px;}#yiv0035466149 #yiv0035466149ygrp-msg p a {font-family:Verdana;}#yiv0035466149 #yiv0035466149ygrp-msg p#yiv0035466149attach-count span {color:#1E66AE;font-weight:700;}#yiv0035466149 #yiv0035466149ygrp-reco #yiv0035466149reco-head {color:#ff7900;font-weight:700;}#yiv0035466149 #yiv0035466149ygrp-reco {margin-bottom:20px;padding:0px;}#yiv0035466149 #yiv0035466149ygrp-sponsor #yiv0035466149ov li a {font-size:130%;text-decoration:none;}#yiv0035466149 #yiv0035466149ygrp-sponsor #yiv0035466149ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv0035466149 #yiv0035466149ygrp-sponsor #yiv0035466149ov ul {margin:0;padding:0 0 0 8px;}#yiv0035466149 #yiv0035466149ygrp-text {font-family:Georgia;}#yiv0035466149 #yiv0035466149ygrp-text p {margin:0 0 1em 0;}#yiv0035466149 #yiv0035466149ygrp-text tt {font-size:120%;}#yiv0035466149 #yiv0035466149ygrp-vital ul li:last-child {border-right:none !important;}#yiv0035466149

The upper limit nog wireless throttles is likely the limit of the wireless router you're using......the router gives out IP addresses, and most are limited to 50 or so by default, but might be able to be changed. The communications speed (baud rate) will limit the performance with many wireless connections, and many systems run at 9600 or 19200, which aren't fast.

Using only phones that don't have cell network access (no sim card or the equivalent) wiull work just fine with JMRI.....I've one of my old, slow, memory limited phones without cell access that I use daily for JMRI.

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 : /Problem with Signal Logic on 37 Heaven/Updated version/BritishRailSignals.zip
Uploaded by : frasersmith51 <fraser@...>
Description : Gif Icons for signals

You can access this file at the URL:


To learn more about file sharing for your group, please visit:


Regards,

frasersmith51 <fraser@...>

Background: We have a large O Scale club using NCE for our DCC. We have several people now who use their phone or tablet to run trains using the JMRI WiThrottle feature. Some use the Apple WiThrottle app and other use the Android Engine Driver.


Question 1. Does anyone have any experience with what the upper limit of users might be? Occasionally there is a slight delay but I don't know if that is the WiFi, the JMRI interface, or the NCE system causing it. I would like to know where the maximum user limit is before I run into it.


We use mostly NCE ProCabs with radio, nothing tethered. We are now reaching the maximum of 16 ProCabs in use.


Question 2. Has anyone tried using old cell phones and WiThrottle? The cell phones would not be activated to any cellular service provider but would simply use the WiFi connection. One problem would be how to get the WiThrottle or Engine Driver app installed.


As they say, inquiring minds want to know. I look forward to hearing from anyone who has experience with these issues.


Art Williams
Detroit Model Railroad Club

Just to be clear.
If you have NCE Power Pro system, and want to program Tsunami or any other decoder with CV numbers above 255 (Except ESU Loksound) you will need do one of the following:
1. Switch digital systems (Likely too much cost)
2. Get a standalone programmer such as SPROG (My preference) or PR3
3. program your Locos at a club or friends layout, that have other than NCE Power Pro system.

Thomas
DeSoto, TX

Tim,

I see two addresses being operated there, 837 and 2203, were those both being operated by Engine Driver?

At the end of the log, the last operation request for each locomotive was properly responded to by the command station. Can you run through this one more time, and check to see if there are any errors reported in the console?

If there are no errors in the console, then this is probably a communication issue between Engine Driver and the WiThrottle server, and not an issue between JMRI and the Z21. If this is a communication issue, it could be an issue in the WiThrottle Server (which might also be indicated in a console message), in Engine Driver, or some non-JMRI specific networking problem.

Paul

Ooops. Your question made me realize that I was having this conversation after apparently being misled by someone (maybe the engineers) into believing this is a problem. It appears now that I am mistaken about the full spur causing delay in setouts (I knew I was missing something).

After the last Op Session, the question was raised to me why cars cannot be delivered to a full spur when a pickup is scheduled. I thought it would work, but when I hurriedly looked at the build report and saw the initial rejection due to spur length (without looking further), I then changed my route to allow another visit (incorrectly) thinking that this was the problem. If I _had_ looked further in the build report, I would have found that the rejected car is re-visited and assigned to that spur. I have built all the trains for July 1 Ops Session, but will go back and fix it (in my spare? time).

What I posted was parts of the build report from my "work-around" route where the train goes back to that town a second time.

However, after reading your question, I went back and looked at previous switchlists and build reports (which I should have done rather than relying on anecdotal evidence from casual observations of the layout), and this is not an issue. Looking at each of the previous 3 months (monthly Op Sessions), cars are picked up and setout at the single-car spurs on the same visit. Meaning that the aggressive mode does work as expected, contradicting the casual report from the layout.

Dan, thanks for taking the time to read and reply, and thanks for your excellent contributions to an amazing suite of programs known as JMRI.

Phil in gorgeous Young Harris, Georgia, USA

On 06/22/2017 09:53 AM, tventonukgateway@... [jmriusers] wrote:

Trying out this nightly build version, I get a problem opening my panel. I'm using the Z21 for loco control and point control, plus MERG Cbus to control more points.

Using the production version, panel opens fine.

You will need to be more specific.

What error are you getting?

Paul

On 06/22/2017 06:50 AM, tventonukgateway@... [jmriusers] wrote:

Now onto the next but minor problem. I have done a workaround, but it is an annoyance. The turnouts are one digit out. If I choose the turnout 56, 55 is the one that moves.

That is a difference in interpretation of the XPressNet protocol, and has been a long standing issue when mixing hardware from Lenz and Roco. We have always used the Lenz interpretation of the addressing, which makes the Roco addresses off by one.

I can fix that for the Z21, but it will make Lenz handhelds used with the Z21 be off by one.

( This may not matter to you, but it does matter to me, since I have a sizable investment in XPressNet hardware from several manufacturers ).

Plus the thrown/closed indicator on the Multimaus is reversed to that showing in JMRI, and using the Invert command does not correct it.

The indicator being reversed again goes back to interpretation of the protocol. Lenz uses symbols ( + and - ) for turnout directions and not thrown and closed. The JMRI default interpretation is that + is thrown and - is closed (And looking at this now, I realized the + and - don't actually get updated if the turnout is inverted. I will need to fix that).

Invert for turnouts on the Z21 hasn't been implemented yet. I'll work on that. (I hadn't tested that with my Z21, and forgot it wasn't implemented).

Also, remember that the invert option is not about making the throttles match JMRI.
There are times when a turnout ends up being reversed on the layout (either electrically or mechanically) and the invert option is used to make JMRI show the position correctly. As such, you invert some turnouts and not others, so throwing turnouts on hand held throttles does not always match JMRI.

For a concrete example of this, when using a tortoise switch machine with a DCC specialties Hare as the decoder operating it, clearance dictates how you mount both the switch machine and the decoder (which plugs right into the switch machine ) on the layout. This may result in the normal Thrown state (indicated as diverging on the MultiMaus) sending the actual turnout into the Closed state (the actual turnout is going through the straight route). There's nothing we can do to make the hand held throttle show this correctly, but the invert option does let JMRI show that correctly.

Paul

Paul

as requested.

Tim

XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 70 and direction Forward In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 C6 08 00 00 00 A3 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 2203 To Speed Step 85 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C8 9B 04 55 00 00 00 00 ED 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 71 and direction Forward In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 C7 08 00 00 00 A2 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 2203 To Speed Step 87 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C8 9B 04 57 00 00 00 00 EF 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 72 and direction Forward In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 C8 08 00 00 00 AD 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 2203 To Speed Step 88 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C8 9B 04 58 00 00 00 00 E0 00 00 00 00 00 00 00
Z21 Serial Number Request
Z21 Serial Number Reply. Serial Number: 45,958
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 73 and direction Forward In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 C9 08 00 00 00 AC 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 2203 To Speed Step 0 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C8 9B 04 00 00 00 00 00 B8 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 74 and direction Forward In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 CA 08 00 00 00 AF 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 2203 To Speed Step 0 and direction Forward In 128 speed step mode.
XPressNet Tunnel Reply: EF C8 9B 04 80 00 00 00 00 38 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 0 and direction Forward In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 80 08 00 00 00 E5 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 1 Momentary Status for address: 2203 F0 continuous F1 continuous F2 continuous F3 continuous F4 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 0 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 00 08 00 00 00 65 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 1 Momentary Status for address: 2203 F0 continuous F1 continuous F2 continuous F3 continuous F4 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 2 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 02 08 00 00 00 67 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 1 Momentary Status for address: 2203 F0 continuous F1 continuous F2 continuous F3 continuous F4 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 3 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 03 08 00 00 00 66 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 1 Momentary Status for address: 2203 F0 continuous F1 continuous F2 continuous F3 continuous F4 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 5 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 05 08 00 00 00 60 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 1 Momentary Status for address: 2203 F0 continuous F1 continuous F2 continuous F3 continuous F4 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 7 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 07 08 00 00 00 62 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 2 Momentary Status for address: 2203 F5 continuous F6 continuous F7 continuous F8 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 10 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 0A 08 00 00 00 6F 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 2 Momentary Status for address: 2203 F5 continuous F6 continuous F7 continuous F8 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 13 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 0D 08 00 00 00 68 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 2 Momentary Status for address: 2203 F5 continuous F6 continuous F7 continuous F8 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 17 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 11 08 00 00 00 74 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 2 Momentary Status for address: 2203 F5 continuous F6 continuous F7 continuous F8 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 20 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 14 08 00 00 00 71 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 3 Momentary Status for address: 2203 F9 continuous F10 continuous F11 continuous F12 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 23 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 17 08 00 00 00 72 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 3 Momentary Status for address: 2203 F9 continuous F10 continuous F11 continuous F12 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 27 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 1B 08 00 00 00 7E 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 3 Momentary Status for address: 2203 F9 continuous F10 continuous F11 continuous F12 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 32 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 20 08 00 00 00 45 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 3 Momentary Status for address: 2203 F9 continuous F10 continuous F11 continuous F12 continuous
XPressNet Tunnel Reply: 61 82 E3
Z21 Serial Number Request
Z21 Serial Number Reply. Serial Number: 45,958
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 37 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 25 08 00 00 00 40 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 4 Momentary Status for address: 2203 F13 continuous F14 continuous F15 continuous F16 continuous F17 continuous F18 continuous F19 continuous F20 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 41 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 29 08 00 00 00 4C 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 4 Momentary Status for address: 2203 F13 continuous F14 continuous F15 continuous F16 continuous F17 continuous F18 continuous F19 continuous F20 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 45 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 2D 08 00 00 00 48 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 4 Momentary Status for address: 2203 F13 continuous F14 continuous F15 continuous F16 continuous F17 continuous F18 continuous F19 continuous F20 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 49 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 31 08 00 00 00 54 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 4 Momentary Status for address: 2203 F13 continuous F14 continuous F15 continuous F16 continuous F17 continuous F18 continuous F19 continuous F20 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 52 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 34 08 00 00 00 51 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 4 Momentary Status for address: 2203 F13 continuous F14 continuous F15 continuous F16 continuous F17 continuous F18 continuous F19 continuous F20 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 56 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 38 08 00 00 00 5D 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 4 Momentary Status for address: 2203 F13 continuous F14 continuous F15 continuous F16 continuous F17 continuous F18 continuous F19 continuous F20 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 59 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 3B 08 00 00 00 5E 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 4 Momentary Status for address: 2203 F13 continuous F14 continuous F15 continuous F16 continuous F17 continuous F18 continuous F19 continuous F20 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 63 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 3F 08 00 00 00 5A 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 4 Momentary Status for address: 2203 F13 continuous F14 continuous F15 continuous F16 continuous F17 continuous F18 continuous F19 continuous F20 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 66 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 42 08 00 00 00 27 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 5 Momentary Status for address: 2203 F21 continuous F22 continuous F23 continuous F24 continuous F25 continuous F26 continuous F27 continuous F28 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 69 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 45 08 00 00 00 20 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 5 Momentary Status for address: 2203 F21 continuous F22 continuous F23 continuous F24 continuous F25 continuous F26 continuous F27 continuous F28 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 72 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 48 08 00 00 00 2D 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 5 Momentary Status for address: 2203 F21 continuous F22 continuous F23 continuous F24 continuous F25 continuous F26 continuous F27 continuous F28 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 76 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 4C 08 00 00 00 29 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 5 Momentary Status for address: 2203 F21 continuous F22 continuous F23 continuous F24 continuous F25 continuous F26 continuous F27 continuous F28 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 78 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 4E 08 00 00 00 2B 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 5 Momentary Status for address: 2203 F21 continuous F22 continuous F23 continuous F24 continuous F25 continuous F26 continuous F27 continuous F28 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 81 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 51 08 00 00 00 34 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 5 Momentary Status for address: 2203 F21 continuous F22 continuous F23 continuous F24 continuous F25 continuous F26 continuous F27 continuous F28 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 84 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 54 08 00 00 00 31 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 5 Momentary Status for address: 2203 F21 continuous F22 continuous F23 continuous F24 continuous F25 continuous F26 continuous F27 continuous F28 continuous
XPressNet Tunnel Reply: 61 82 E3
Z21 Serial Number Request
Z21 Serial Number Reply. Serial Number: 45,958
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 86 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 56 08 00 00 00 33 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Function Group 5 Momentary Status for address: 2203 F21 continuous F22 continuous F23 continuous F24 continuous F25 continuous F26 continuous F27 continuous F28 continuous
XPressNet Tunnel Reply: 61 82 E3
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 88 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 58 08 00 00 00 3D 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 2203 To Speed Step 15 and direction Forward In 128 speed step mode.
XPressNet Tunnel Reply: EF C8 9B 04 8F 00 00 00 00 37 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 837 To Speed Step 90 and direction Reverse In 128 speed step mode.
XPressNet Tunnel Reply: EF C3 45 04 5A 08 00 00 00 3F 00 00 00 00 00 00 00
XPressNet Tunnel Message: Mobile Decoder Operations Request: Set Address: 2203 To Speed Step 16 and direction Forward In 128 speed step mode.
XPressNet Tunnel Reply: EF C8 9B 04 90 00 00 00 00 28 00 00 00 00 00 00 00

Trying out this nightly build version, I get a problem opening my panel. I'm using the Z21 for loco control and point control, plus MERG Cbus to control more points.

Using the production version, panel opens fine.

Tim

On Jun 22, 2017, at 12:58 AM, triangkeeper@... [jmriusers] <jmriusers@...> wrote:

Thank you for confirming my observations. I am planning of extending hardware bits using the shift register method and I am now a bit worried that C/MRI operation of updating changes may slow things down somewhat. Maybe more nodes might be a better approach.

What you do internal to your node is separate from the protocol on the line. For example, you could keep the current status in memory, then compare it when something new is written over the line. That way, you can see which bit(s) changed, and just tell hardware about them.

Bob
--
Bob Jacobsen
rgj1927@...

Regarding car locations, I use Excel (older version, 2000) to import the car roster export.

Before pre-building any trains for an Ops Session, I do this (Export) then create a spreadsheet with two worksheets: one is all cars sorted by number, and one is all cars sorted by location and spur. This allows me to verify, or re-set/pre-set, the cars on the layout for the Ops Session.

This may not be for the feint of heart though (says Phil as as he starts trying to explain his process and edits it about 32 times in an attempt to achieve the right balance of tech and novice steps).

1. In JMRI, in the Cars file, I use "Tools/Car Roster/Export to file". This creates a "csv" file (comma delimited text file) in a (new) subdirectory "operations" under my User File Location preference.
2. In Excel: I import the data then massage it.
a. Using "Data/Get External Data/Import Text File", I change the search to All Files (since Excel text import does not show csv files). I find and select the "ExportOperationsCarRoster.csv" file.
b. In the Text Import Wizard step 1 of 3, I change the radio button to "Delimited" in the "Original data type" box, then click Next.
c. In the Text Import Wizard step 2 of 3, I check "Comma" in the Delimiters box (which then shows, in the Data preview window, the fields all separated into columns)
d. In the Text Import Wizard step 3 of 3, I click the Finish button. Usually, I skip whatever columns which are not needed (but this is optional since Excel lets you delete those columns later if desired).
e. I select the location to import the data into (typically the top left cell). This creates a worksheet of all cars in the Cars file, sorted by number.

I then sort/arrange the data as needed (delete columns not needed) then I work the Page Setup (printing 1 wide by 2 or 3 tall), highlight the area to be printed then set the Print Area and format the cells with borders and interior lines; then I copy the data to another worksheet and sort/arrange that as needed (by location/spur).

I do this before building any trains to make and print what I call the "Starting Positions" reports (one by number, one by location/spur). I also subsequently import the cars data (to a column after the existing data) after building all my trains to compare the before and after. My 9 trains move an average of about 85 cars (out of an active roster of 111), change loads on about 45, and move about 11 on more than one train per session.

Hope this gives you ideas on possibilitys. I can answer any questions, and would invite comments too if other methods or ways can improve the results.

Phil in gorgeous Young Harris, Georgia, USA (aka pesky computer geek)

On 06/22/2017 07:26 AM, tventonukgateway@... [jmriusers] wrote:

Update, tried WiThrottle (Android), starts loco going, but loses it, no control at all.

Ok, so the question we need to answer with that problem is where are we loosing the connection.

It could be between the PC and the Z21, but it could also be between the PC and Engine Driver.

One thing I need to determine that is a Z21 message log from JMRI.

Paul

--
______________________________________________________________________________

"Quality is a Characteristic of thought and statement that
is recognized by a nonthinking process. Because
definitions are a product of rigid formal thinking,
quality cannot be defined."
Robert M. Pirsig
Zen and The Art of Motorcycle Maintenance

Phil

Is this the build report that works, or the one that fails?


Dan

Sudden memory:

Go to Preferences->Defaults and check that NCE is selected for everything, rather than Internal.
--
Dave in Australia