This gets curiouser and curiouser.

I put loco 1003 on the programming track, and asked DecoderPro to identify it. It found it correctly, highlighting the roster line for loco 1003. If the address works right there, would it be wrong on the main track? If it's right on the main track, and the rest of the packet looked normal for going forward and stopping, then why didn't the loco run?

I also can't get a loco set to address 32 to work, whether as a short or long address. But, DecoderPro identified it, too. I think I'll try making it address 132 temporarily, to see if that works.

It seems so close to working properly, yet it doesn't! Maybe I should make sure the checksum value at the end of the packet is correct. I haven't done that exercise.

Don Weigt
Connecticut, USA

I have merged a fix for layoutturnouts and layoutblocks, which is now included in the latest developer build, and will be in future test and production releases.

If additional elements are found generating similar WARN messages, please attach example panel(s) so we can investigate and address.

On Fri, Aug 16, 2019 at 01:36 PM, Steve Todd wrote:

He provided his panel as an example of the label rotation issue and the crossover appearance issue.
I have created Github issues and to investigate and address those.

These fixes have been merged and are included in the latest developer build, and will be in future test and production releases. Note that the double-crossover will need the same fix, but I don't have an example of one to work with.

The simple answer is "Don't". Just use the PanelPro icon and autostart already provided. If you want to see the Roster, just add "Open Roster" to your startup actions. Creating a separate icon for the same program is a recipe for confusion.
--SteveT

开云体育

Don

I have been using JMRI with Easydcc (both the CB2 and CB2B) for many years with no problems, I do a lot of installs for others - with many numbers in the 8000 and 9000 series. The locos get a good testing on the layout when done.

The only suggestion I can make - and you have probably done this - do a full reset of the command station. Hold the enter key down and turn the power on while holding the enter key down until the reset is complete.

Gerry

Well, I've confirmed JMRI is sending the right addresses to the EasyDCC. Now, I wonder why they don't result in the same packets going to the decoders as when controlled from the EasyDCC plug in throttles? Using the plug in throttles, I have control of locos with addresses above 1000. With WiThrottle though JMRI on the RPi, I don't.

JMRI to EasyDCC addresses from the raw data, following a prefix hex C. For example C1 5D 3F 80 23 is Speed = 0 to loco 349:

349:??? 15Dh
901:??? 385h
1003:? 3EBh
1477:? 5C5h

-- 
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder




NMRA Australasian Region
Contest & AP Chairman
Web Administrator

Don:

There was an issue some time ago where the CVP serial interface wasn't processing long addresses... short fine...

Let's see, CVP considers anything under 100 or is it 127 short with no option like NCE to use either...

Connecting a friends layout to a Win10 baby computer... Minix Z83-4 through a Keyspan USB it does handle long addresses with the very latest firmware in the command station... I'm not near the RR and my friend isn't around to double check all the version numbers...

Maybe a place to look?

Jim Albanowski

Well, I've confirmed JMRI is sending the right addresses to the EasyDCC. Now, I wonder why they don't result in the same packets going to the decoders as when controlled from the EasyDCC plug in throttles? Using the plug in throttles, I have control of locos with addresses above 1000. With WiThrottle though JMRI on the RPi, I don't.

JMRI to EasyDCC addresses from the raw data, following a prefix hex C. For example C1 5D 3F 80 23 is Speed = 0 to loco 349:

349:??? 15Dh
901:??? 385h
1003:? 3EBh
1477:? 5C5h

On Tue, Aug 27, 2019 at 06:36 AM, Robert Schworm wrote:

My 2 cents are forget windows and put jmri on a RPi.

Suggesting someone buy a new computer (no matter how cheap) using a different OS is not very helpful. Especially when the issue is probably a simple installation problem.. Two JMRI developers have offered solutions to this issue.

While the RPi has it's place not everyone is interested.

--
Peter Ulvestad

JMRI Users Group Moderator - ( )
Tam Valley Group Moderator - ( )
Sprog-DCC Group Moderator - ( )
Edmonton Model Railroad Association -

I can rotate the display but the touchscreen remains 90? out which means a horizontal move of the screen gives a vertical move of the mouse pointer.

Mike

Steve,

? ? I've downloaded two pics into the photos section under "Waveshare".? They show what I'm seeing on my display when you use the Waveshare driver.? Might order a better 3.5 LCD screen that plugs into the HDMI post next and use this pi for camera display.

? ?Manged to move and resize the last panel window for JMRI so I can shut down the pi now without the main monitor.? ?Tried to run Dispatcher ( which I did before using the monitor), but could not access the bottom section of the New Train window.? ?The WiFi throttle worked well, a bit slow though and the web server showed the panels in their proper resolution.

Roger

Mike,

? ? Can you fix the problem by running the following command to put back into correct position?

? ? sudo ./LCD35-show 0

Roger

The LCD is the correct way up using LCD35-show, but the touch screen is 90? out. I think the problem is there more than one location where the data can be held, I've found two so far, altering the co-ordinates has no effect, so I think I haven't found them yet. I find using the wifi keyboard/touchpad is better anyway, so haven't looked further.

Mike

开云体育

Bob,

Thanks so much for the reply! You probably hit the nail on the head about the lights. I had in previous sessions run that loco on a plug in throttle. I keep power on to the EasyDCC command station, so the information from that previous session would still have been stored in it. I know the lights come on when I power up the track if I didn't switch them off before I power down the railroad.

I have a mouse and monitor available, but not a keyboard for the Pi. I have been using my laptop and VPN to see what the Pi is doing and change its operation. I have viewed commands being sent to the EasyDCC and the replies, but am just starting to do that.

If I can get the info you want via VPN (I don't know why I couldn't), then I'll try to post it. Meanwhile, I'll look at the commands myself, and try to see what's happening. I don't know if EasyDCC is doing something unexpected with the addresses above 999(?), or JMRI. I expected both to handle them the same way, given DCC's address range is 9,999 decimal.

Will report more later. Thanks again for the suggestions. I see a little light through the crack in the doorway now!

Don Weigt
Connecticut, USA

I don’t know much about EasyDCC, but I can make general comments.

On some (other) systems, you can have _both_ JMRI and a hardware throttle trying to control the same train. In that case, you’ll see the speed changing as first one then the other commands it. Same for functions. So perhaps that’s happening here.

Taking a quick look at the code, I don’t see anything that knows about addresses above or below 1000. It’s certainly not related to hexadecimal coding; 1000 doesn’t mean anything there.

I haven’t been following all the details of your RPi setup. Do you have a screen and keyboard connected to it? Or can you screen share to it? If you can talk to JMRI natively (not through the webserver), please open the EasyDCC monitor, check “Show raw data” and record some throttle traffic with addresses above and below 1000. That might give a clue. You can also narrow things down a bit by using a JMRI screen throttle and seeing how that works.

Bob

On Aug 26, 2019, at 6:11 PM, Don Weigt <dweigt47@...> wrote:

For the first time, my Raspberry Pi 3B+ with Steve Todd's JMRI image is connected to my railroad's EasyDCC Command Station! Big step: the USB to serial cable I bought plus the DB-9 to modular phone 6 wire cable was wired correctly. I identified the USB port it plugged into, and had control. Well, sort of...

At first, nothing worked. Then after I cycled the layout power on the tablet running the JMRI throttle, it worked, but may have begun for some other reason. After a few false starts, which I can't fully explain, I had control of loco #349, with the same DCC address. Also could control loco #901. But, not locos numbered higher: 1003, 1477, 2501, or Daylight 4437.

So, I must ask: is there a problem with how JMRI handles decoder addresses higher than 1000 decimal? These locos work fine with the wired EasyDCC throttles, but not when I enter the same addresses on my tablet running JMRI WiThrottle. I wonder if it's a hex vs decimal issue? I sure want the loco number to be the same on JMRI wireless throttles as on EasyDCC wired ones! I looked at the EasyDCC documentation for using its serial port, but it's pretty confusing. Hence, I'm hoping someone here can help me through this.

Also, for a time, when I turned off the lights on loco 349, they turned back on after about two seconds. Any idea why that would happen? I thought there might be a menu selection to make F0 momentary instead of on-off, but couldn't find anything. Then the problem mysteriously went away...

Also, when I used the stop button to slow the loco to a stop from a low speed, it would pause a half second or so, then move in the other direction a little bit. Has anyone seen that before?

There were times when the delay was quite perceptible between pressing the stop button and the loco responding, even running only one loco. That concerns me, too.

I have V629 firmware on my EasyDCC, and whatever Steve Todd's recent image's version of Java and JMRI.

Don Weigt
Connecticut, USA

--
Bob Jacobsen
rgj1927@...

Waddy,

? ? The waveshare driver did the trick!? ?It shows the JMRI panels on the LCD display and on the monitor.? Great work!

? ? Notice the mouse pointer runs a little slow now.? Will have to do test to see what effect it has on running JMRI.

? ? We need to contact Steve next to tell others that have the white screen issue.

Roger