¿ªÔÆÌåÓý

Date

Locked Re: Z21 Users Please test

 

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


Locked Re: Z21 Users Please test

 

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


Locked Re: Z21 Users Please test

 

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


Locked Re: help required to configure JMRI for DIY controller interface

 

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@...


Locked Re: Car Location Printout

 

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)


Locked Re: Z21 Users Please test

 

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


Locked Re: Operations: No space despite cars to be pulled

 

Phil

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


Dan


Locked Re: JMRI in edit only mode

 

Sudden memory:

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

On 22 Jun 2017, at 10:38 PM, Dave Heap <dgheap@...> wrote:

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).


Locked Re: Car Location Printout

 

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


Locked Re: JMRI in edit only mode

 

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

On 22 Jun 2017, at 10:05 AM, thirdgenfcarnut@... [jmriusers] <jmriusers@...> wrote:

All four jumpers on the USB Interface are in the off position. This configuration remains unchanged from before this PC was wiped and upgraded.


Here is a copy and paste of the Console Log


2017-06-21 19:49:07,328 util.Log4JUtil INFO - * JMRI log ** [main]
2017-06-21 19:49:07,375 util.Log4JUtil INFO - This log is appended to file: C:&#92;Users&#92;Steve&#92;JMRI&#92;log&#92;messages.log [main]
2017-06-21 19:49:07,390 util.Log4JUtil INFO - This log is stored in file: C:&#92;Users&#92;Steve&#92;JMRI&#92;log&#92;session.log [main]
2017-06-21 19:49:07,390 apps.AppsBase INFO - DecoderPro version 4.6-R81496dc starts under Java 1.8.0_131 on Windows 7 x86 v6.1 at Wed Jun 21 19:49:07 EDT 2017 [main]
2017-06-21 19:49:07,687 gui3.Apps3 INFO - Starting with profile My_JMRI_Railroad.3e514dad [main]
2017-06-21 19:49:07,921 node.NodeIdentity INFO - Using jmri-001D099D8DB6-3e514dad as the JMRI Node identity [main]
2017-06-21 19:49:09,151 usbdriver.UsbDriverAdapter INFO - NCE USB COM4 port opened at 9600 baud [main]
2017-06-21 19:49:09,354 nce.NceConnectionStatus INFO - NCE EPROM revision = 7.3.0 [AWT-EventQueue-0]
2017-06-21 19:49:15,004 util.FileUtilSupport INFO - File path program: is C:&#92;Program Files&#92;JMRI&#92; [main]
2017-06-21 19:49:15,004 util.FileUtilSupport INFO - File path preference: is C:&#92;Users&#92;Steve&#92;JMRI&#92;My_JMRI_Railroad&#92; [main]
2017-06-21 19:49:15,004 util.FileUtilSupport INFO - File path profile: is C:&#92;Users&#92;Steve&#92;JMRI&#92;My_JMRI_Railroad&#92; [main]
2017-06-21 19:49:15,004 util.FileUtilSupport INFO - File path settings: is C:&#92;Users&#92;Steve&#92;JMRI&#92; [main]
2017-06-21 19:49:15,004 util.FileUtilSupport INFO - File path home: is C:&#92;Users&#92;Steve&#92; [main]
2017-06-21 19:49:15,004 util.FileUtilSupport INFO - File path scripts: is C:&#92;Program Files&#92;JMRI&#92;jython&#92; [main]
2017-06-21 19:49:18,941 throttle.ThrottlesPreferences INFO - Did not find throttle preferences file. This is normal if you haven't save the preferences before [Thread-8]
2017-06-21 19:49:18,957 hrottle.AbstractWiThrottlePreferences INFO - Could not find WiThrottle preferences file. Normal if preferences have not been saved before. [Thread-8]


Locked Re: help required to configure JMRI for DIY controller interface

 

Geoff

CMRI communication is well defined in this document:



There are four special characters to be aware of:

STX (hex 0x02, decimal 2) ¨C Start of Text
ETX (hex 0x03, decimal 3) ¨C End of Text
DLE (hex 0x10, decimal 16) ¨C 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


Locked Re: Problem programming higher CVs

 

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

On 22 Jun 2017, at 11:41 AM, s.w.yount@... [jmriusers] <jmriusers@...> wrote:

I have 4.2.1. JMRI and am having problems programming CVs 200-500. I have a PowerPro system (not a Power Cab). How do I get these higher CVs programmed. I have the lastest EPROM on my system, which is 03/01/2007c.


Locked Re: Z21 Users Please test

 

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

Tim


Locked Re: Z21 Users Please test

 

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


Locked JMRI 4.7.6 and apologies

 

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


Locked Re: Contributing to the Engine Driver code on GitHub?

 

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


Locked Re: help required to configure JMRI for DIY controller interface

 

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


Locked Re: help required to configure JMRI for DIY controller interface

 

P.S. here is a screen shot of 4 Lights sequentially swicthed to ON

[41 54 01 00 00 00 00 00] Transmit ua=0 OB=1 0 0 0 0 0
[41 54 10 03 00 00 00 00 00] Transmit ua=0 OB=10 3 0 0 0 0 0
[41 54 07 00 00 00 00 00] Transmit ua=0 OB=7 0 0 0 0 0
[41 54 0F 00 00 00 00 00] Transmit ua=0 OB=f 0 0 0 0 0

I also don't know why there is extra 10 in the second line


Locked Re: Error Message in the System Console

 

Sorry, but neither of those is right.

It sounds like the LI100¡¯s USB connection isn¡¯t being properly being seen by your Mac. Perhaps there¡¯s a driver that has to be loaded?

Bob


On Jun 17, 2017, at 4:18 PM, wmseapc@... [jmriusers] <jmriusers@...> wrote:

Bob; my only 2 options were

/dev/tty.Bluetooth-Incoming-Port; &



/dev/cu.Bluetooth-Incoming-Port


I switched to the 2nd one & it appears to be rectified in the System Console


2017-06-17 19:14:29,981 util.Log4JUtil INFO - * JMRI log ** [main]
2017-06-17 19:14:30,979 util.Log4JUtil INFO - This log is appended to file: /Users/williamseabrooke/Library/Preferences/JMRI/log/messages.log [main]
2017-06-17 19:14:30,980 util.Log4JUtil INFO - This log is stored in file: /Users/williamseabrooke/Library/Preferences/JMRI/log/session.log [main]
2017-06-17 19:14:30,986 apps.AppsBase INFO - DecoderPro version 4.6-R81496dc starts under Java 1.8.0_131 on Mac OS X x86_64 v10.12.5 at Sat Jun 17 19:14:30 EDT 2017 [main]
2017-06-17 19:14:33,451 gui3.Apps3 INFO - Starting with profile wmseamac.3f48e951 [main]
2017-06-17 19:14:33,648 node.NodeIdentity INFO - Using jmri-28F0761979C8-3f48e951 as the JMRI Node identity [main]
2017-06-17 19:14:33,785 li100.LI100Adapter INFO - /dev/cu.Bluetooth-Incoming-Port port opened at 9600 baud with DTR: true RTS: true DSR: false CTS: false CD: false [main]
2017-06-17 19:15:03,807 li100.LI100XNetInitializationManager WARN - Command Station disconnected, or powered down assuming LZ100/LZV100 V3.x [main]
2017-06-17 19:15:03,877 jmri.InstanceManager ERROR - Should not set default of type jmri.CommandStation to null value [main]
2017-06-17 19:15:03,878 managers.ManagerDefaultSelector WARN - SystemConnectionMemo for XPressnet (class jmri.jmrix.lenz.XNetSystemConnectionMemo) provides a null interface jmri.CommandStation instance [main]
2017-06-17 19:15:03,878 plementation.JmriConfigurationManager ERROR - Exception initializing jmri.managers.ManagerDefaultSelector: System connection XPressnet provides a null manager for interface jmri.CommandStation [main]
2017-06-17 19:15:08,809 jmrix.AbstractMRTrafficController WARN - Timeout on reply to message: 21 21 00 consecutive timeouts = 0 [Transmit]
2017-06-17 19:15:38,912 util.FileUtilSupport INFO - File path program: is /Applications/JMRI/ [main]
2017-06-17 19:15:38,912 util.FileUtilSupport INFO - File path preference: is /Users/williamseabrooke/Library/Preferences/JMRI/wmseamac/ [main]
2017-06-17 19:15:38,913 util.FileUtilSupport INFO - File path profile: is /Users/williamseabrooke/Library/Preferences/JMRI/wmseamac/ [main]
2017-06-17 19:15:38,913 util.FileUtilSupport INFO - File path settings: is /Users/williamseabrooke/Library/Preferences/JMRI/ [main]
2017-06-17 19:15:38,913 util.FileUtilSupport INFO - File path home: is /Users/williamseabrooke/ [main]
2017-06-17 19:15:38,913 util.FileUtilSupport INFO - File path scripts: is /Applications/JMRI/jython/ [main]
2017-06-17 19:15:39,210 swing.RosterFrame ERROR - Unable to get the double click speed, Using JMRI default of half a secondjava.lang.NullPointerException [main]
2017-06-17 19:15:39,568 gui3.TabbedPreferencesAction INFO - We are already waiting for the preferences to be displayed [main]
2017-06-17 19:15:43,838 jmrix.AbstractMRTrafficController WARN - Timeout on reply to message: 21 24 05 consecutive timeouts = 1 [Transmit]


But I still see 2 different errors.


Like I stated earlier I am a newbie to Wifi & JMRI


Thanks to all!





--
Bob Jacobsen
rgj1927@...


Locked Operations: No space despite cars to be pulled

 

I have missed something, and cannot see what.

In one spur (IGA Dr 1), I have a reefer that is scheduled to be picked up (which would make room for a new car), and I have a reefer in a yard that is supposed to be delivered there. The build report initially fails to assign the new car due to no room. Then further down, the build report assigns the P/U from the spur but it is too late for the delivery. I mistakenly had thought that aggressive mode with 2 passes would solve that.

I have worked around that by making the route for that train go to that town twice, once from the yard, then again after returning to the yard. The build report therefore assigns the car to be picked up in the 1st visit, then assigns the car to be delivered in the 2nd visit (to an empty spur).


I had wanted to make the train take the new car with and merely swap the P/U with the S/O (as I suspect the prototype did).



Here are portions of the build report:

"1- Build Report for train (#322) built on 6/18/17 10:35 PM
1- JMRI version 4.7.6+R570b2bc
3- Build report detail level: Normal
5- Build report detail level: Detailed
7- Build report detail level: Very Detailed
7- Router build report level: Very Detailed
1-
5- Train Build Options:
5- Build option is set to aggressive
5- Perform 2 passes
5- Car routing via yards is enabled
5- Allow local moves if car has a custom load or FD
5- Allow cars to travel from origin to terminal
1-
3- Train (#322) route (322-Marietta Local):
3- Location (Elizabeth) requests 9 pick ups, maximum train length 500 feet
3- Location (Marietta) requests 9 moves, maximum train length 500 feet
3- Location (Elizabeth) requests 9 moves, maximum train length 500 feet
3- Location (Eliz-Support) requests 9 moves, maximum train length 500 feet
3- Location (Elizabeth) requests 10 moves, maximum train length 600 feet
3- Location (Marietta) requests 10 moves, maximum train length 400 feet
3- Location (Elizabeth) requests 10 set outs
1- Route (322-Marietta Local) requests 33 cars and 66 moves
...
7- Car (WFEX 68249) type (ReeferIce) at (Elizabeth, Liz Yard Trks) 1 moves
...
7- Car (PFE 95829) type (ReeferIce) at (Marietta, IGA Dr 1) 1 moves
...
5- Car (WFEX 68249) type (ReeferIce) load (Peaches) at (Elizabeth, Liz Yard
5- Trks) has final destination (Marietta, IGA Dr 1) routing begins
7- Train (#322) can pull car (WFEX 68249) from (Elizabeth, Liz Yard Trks)
7- route id (18r1)
7- Train (#322) can transport car (WFEX 68249) from C/I (Elizabeth, Liz Yard
7- Trks) to (Marietta, IGA Dr 1)
7- Route for car (WFEX 68249): (Elizabeth, Liz Yard
7- Trks)->(#322)->(Marietta, IGA Dr 1)
7- Can't use spur (Marietta, IGA Dr 1) for (WFEX 68249) due to rolling stock
7- length 44 feet, available track space 1 feet
7- Track (IGA Dr 1) full, searching for a yard at destination (Marietta)
7- Could not find a yard at (Marietta) for car (WFEX 68249)
5- Did not assign a destination for car (WFEX 68249)
...
5- Find spur for car (PFE 95829) type (ReeferIce) custom load (MT-Reefer) at
5- (Marietta, IGA Dr 1)
7- Try destination (Atlanta Interchange, ATL Trk 2) for car (PFE 95829) with
7- load (MT-Reefer)
7- Train (#322) doesn't service location (Atlanta Interchange)
7-
7- Find train for car (PFE 95829) from (Marietta, IGA Dr 1) to (Atlanta
7- Interchange, ATL Trk 2)
7- Train (#120) doesn't service location (Marietta)
7- Train (#261) doesn't service location (Marietta)
7- Train (#290) doesn't service location (Marietta)
7- Train (#44) doesn't service location (Marietta)
7- Train (#49) doesn't service location (Marietta)
7- Train (#121) doesn't service location (Marietta)
7- Train (#45) doesn't service location (Marietta)
7- Train (#50) doesn't service location (Marietta)
7-
7- Router could not find a train able to transport car (PFE 95829) directly
7- from (Marietta) to (Atlanta Interchange) begin two train routing
7-
7- Router find C/I track for car (PFE 95829) final destination (Atlanta
7- Interchange, ATL Trk 2)
7-
7- Can't use C/I (Murphy, MU C/I Trk) for (PFE 95829) due to type (ReeferIce)
7-
7- Can't use C/I (Murphy, MU C/I Trk (50)) for (PFE 95829) due to type
7- (ReeferIce)
7-
7- Can't use C/I (Elizabeth, LIZ Trk 3 (322)) for (PFE 95829) due to car's
7- final destination (Atlanta Interchange) is not allowed by track (LIZ Trk
7- 3 (322))
7-
7- Can't use C/I (Copperhill, CH Trk 2 (120)) for (PFE 95829) due to car's
7- final destination (Atlanta Interchange) is not allowed by track (CH Trk 2
7- (120))
7-
7- Can't use C/I (Mineral Bluff, MB Siding) for (PFE 95829) due to type
7- (ReeferIce)
7-
7- Router found C/I track (Elizabeth, LIZ Trk7 (ATL)) for car (PFE 95829)
7-
7- Find train for car (PFE 95829) from (Elizabeth, LIZ Trk7 (ATL)) to
7- (Atlanta Interchange, ATL Trk 2)
7- Train (#120) doesn't service location (Atlanta Interchange)
7- Train (#261) can pull car (PFE 95829) from (Elizabeth, LIZ Trk7 (ATL))
7- route id (14r1)
7- Train (#261) can transport car (PFE 95829) from C/I (Elizabeth, LIZ Trk7
7- (ATL)) to (Atlanta Interchange, ATL Trk 2)
7- Route for car (PFE 95829): (Marietta, IGA Dr 1)->(#322)->(Elizabeth, LIZ
7- Trk7 (ATL))->(#261)->(Atlanta Interchange, ATL Trk 2)
7- Train (#322) can service car (PFE 95829) from (Marietta, IGA Dr 1) to C/I
7- (Elizabeth, LIZ Trk7 (ATL))
7- Car (PFE 95829) has assigned destination (Elizabeth, LIZ Trk7 (ATL))
3- Car (PFE 95829) assigned to train, destination (Elizabeth, LIZ Trk7 (ATL))

...
5- Car (WFEX 68249) type (ReeferIce) load (Peaches) at (Elizabeth, Liz Yard
5- Trks) has final destination (Marietta, IGA Dr 1) routing begins
7- Train (#322) can pull car (WFEX 68249) from (Elizabeth, Liz Yard Trks)
7- route id (18r1)
7- Train (#322) can transport car (WFEX 68249) from C/I (Elizabeth, Liz Yard
7- Trks) to (Marietta, IGA Dr 1)
7- Route for car (WFEX 68249): (Elizabeth, Liz Yard
7- Trks)->(#322)->(Marietta, IGA Dr 1)
7- Car (WFEX 68249) has assigned destination (Marietta, IGA Dr 1)
7- Car (WFEX 68249) can be serviced later from location (Elizabeth) route id
7- (18r3)
5- Destination (Marietta) not reachable from location (Elizabeth) route id
5- (18r5)
5- Did not assign a destination for car (WFEX 68249)

...
5- Car (WFEX 68249) type (ReeferIce) load (Peaches) at (Elizabeth, Liz Yard
5- Trks) has final destination (Marietta, IGA Dr 1) routing begins
7- Train (#322) can pull car (WFEX 68249) from (Elizabeth, Liz Yard Trks)
7- route id (18r1)
7- Train (#322) can transport car (WFEX 68249) from C/I (Elizabeth, Liz Yard
7- Trks) to (Marietta, IGA Dr 1)
7- Route for car (WFEX 68249): (Elizabeth, Liz Yard
7- Trks)->(#322)->(Marietta, IGA Dr 1)
7- Car (WFEX 68249) has assigned destination (Marietta, IGA Dr 1)
3- Car (WFEX 68249) assigned to train, destination (Marietta, IGA Dr 1)

..."



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