开云体育

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

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

The "nce.NceConnectionStatus INFO - NCE EPROM revision = 7.3.0" in the log below indicates your drivers, jumpers, baud rate and JMRI settings are correct and that JMRI can communicate with your NCE USB.

We now need to see a log (and a report on what the NCE USB LEDs do) when you attempt to drive a loco, program a decoder).
--
Dave in Australia

Geoff

CMRI communication is well defined in this document:



There are four special characters to be aware of:

STX (hex 0x02, decimal 2) – Start of Text
ETX (hex 0x03, decimal 3) – End of Text
DLE (hex 0x10, decimal 16) – Data Link Escape
SYN (hex 0xFF, decimal 255) ! Synchronization

The use of DLE is outlined on page 5, line 162 in the document linked above.

For other questions about CMRI specifically, you might want to join the CMRI yahoo group - look for "CMRI_Users".

Regards
Blair Smith

Due to a firmware problem, the NCE Power Pro is incapable of correctly programming CVs>256 in Program Track mode (a CV<256 will be reprogrammed instead of the correct one). However you can program CVs>256 of ESU decoders in Program Track mode provided you use a current version of JMRI (ESU has provided a workaround in their decoder firmware and JMRI uses this behind-the-scenes).

If you are using any ESU, Econami or Tsunami decoders, you MUST NOT use JMRI V4.2.1. You should always use the latest JMRI version with these decoders as it will prevent you mis-programming your decoders and will also have the latest fixes, updates for these decoders.
--
Dave in Australia

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

Tim

OK thanks Paul. Throttle works, as I would expect it too.

I am unable to test any programming as I don't use the Z21 for that purpose.

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. Plus the thrown/closed indicator on the Multimaus is reversed to that showing in JMRI, and using the Invert command does not correct it.

Tim

First apologies for my tirade about the new version. I could have been more
tactful.

As for 4.7.6, after about a day of testing and tries, I have given up on
it, and gone back to 4.6.0, and all is well, but only after a scratch
install.

The only thing I found is that when in simulation, the java error does not
occur, but when JMRI is connected to live networks (LCC for turnouts and
switches, NCE for throttles and Loconet for sensors and signals), then
warrants crashes with a java error at the run click.

I was about to test which network was possibly contributing to the error,
but reset for the coming session was higher priority, and I needed a
functioning system.

Thank you for the few that have replied (on list and off). Suggestions were
appreciated.

Leo P

Thanks, I will see how I go.


(It may prove easier for me to wait till you have moved ED to AndroidStudio.)


Peter


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

Thanks, Peter.

Those changes looked good and were easy to pull into my copy. I've committed them to JMRI/EngineDriver. You'll want to update your repo from there (or refork) before adding other changes.


Please proceed with the other changes the same way. then, when we've got JMRI/EngineDriver all caught up, I'm going to proceed to:
1) update all source files to match latest JMRI standard (Linux line endings, spaces instead of tabs). I'll push in this change with no functional changes mixed in.
2) move ED into Android Studio, and push this change in. Again, no functional changes mixed.


Thanks!
SteveT

Billybob,

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.

Rgds
Geoff