I have been using JMRI version 4.6 quite successfully, operating throttles and turnouts using my Windows XP PC and wirelessly with Engine Driver. ?I am running Java v8. ?Recently I have made several changes to my track layout and yesterday, before upgrading to version 4.8 of JMRI, I decided to make the changes in JMRI Layout editor. ?The changes were to insert a LH point, a single slip and two curved points. ?The Throttle Table would not accept my additional elements (I am using Power Cab and adding NT61, 62 and 63, and IT61 and 63). ?When I click OK to complete the set up of NT61, I get the message "Unable to covert NT61 to a valid Hardware Address". ?If instead, I enter the details in Layout Editor, I get the error message "Cannot assign turnout because there is no turnout defined for NT61. ?Please enter turnout via tournout table and try again" If I then close the message, hold shift and click in the layout, the turnout appears and I can alter the plan - but of course the turnout does not work.
After discovering this problem (which may have existed for some time as i have not needed to amend the layout until now) I installed JMRI v 4.8. ?It operates in exactly the same way.
Can someone please advise me what the problem is and how I can overcome it?
MAny thanks,Harold.
[Non-text portions of this message have been removed]
|
Locked
Re: System Console Warning Message
Bill, On 08/13/2017 02:55 PM, wmseapc@... [jmriusers] wrote: I am using a LZV100 3.6 version command station with software version 3.6 & an LV102 properly hooked up with 2 separate sMg AC-AC power packs supporting the LVZ100 & LV102 for more power the layout & my LIUSB-Ethernet being the only thing plugged into my command station &my software version is macOS High Sierra; version 10.13 Beta (17A330h); I was wondering if this Beta version was maybe a cause for the problems!
You are actually getting communication now, so you are not seeing a problem between the computer and the LIUSB-Ethernet. I don't see anything from the logs you have sent that explain why you're seeing the repeated "01 08 09" messages (which is the error message being reported that JMRI is trying to recover from.) What that message says is we tried to send a command while the command station is not providing a timeslot to the device. It's actually an error generated by the LIUSB-Ethernet. So what can cause that to occur: 1) Another device could have put the command station in service mode 2) The command station is busy processing some other request (which is typically a programming request) 3) there could be a bad connection on either the A or B line on the XpressNet And this is happening when you first start JMRI, so my guess would be the XpressNet connection has an issue. Does your LIUSB-Ethernet plug into the command station directly, or is it plugged in away from the command station? If it's plugged into the command station, is it plugged in via the XpressNet terminal blocks or via the DIN socket? If it's plugged into the XpressNet terminal block, verify all the connections are tight. If it's plugged in using a the DIN socket, try a different cable. If the LIUSB-Ethernet is plugged in away from the command station, do you have other XpressNet devices? Do they work correctly? If one of them has a removable cord (like the LH90) could you try it's cord to plug in the XpressNet on your LIUSB-Ethernet? If that doesn't work, or isn't possible, try a different XpressNet connection (either the ones on the back of the LZV100 or a closer throttle panel). Paul
|
See below: On 18 Aug 2017, at 7:39 PM, sd90mach@... [jmriusers] <jmriusers@...> wrote:
I have just installed Linux Mint onto an old laptop running Windows XP and making it dual boot. That was the easy bit. Installed JMRI OK and now I have a couple of minor issues.
As I am using a Sprog for programming will Linux go off and find software to suit or do I use the disc supplied with the Sprog I think Mint should have the required generic drivers for the SPROG. The following procedure will determine if this is the case and also explain necessary setup procedures: Open a Terminal window and put in this command EXACTLY (except for the double quotes): "while : ;do clear;ls -lt /dev|head;i=$((i+1));echo $i;sleep 1;done" Press ENTER and watch the screen as you slowly plug/unplug the USB device, watching what device appears/disappears and record the name. If nothing appears/disappears your device is not loading a driver. You will also need to enter the following command EXACTLY (except for the double quotes): "sudo adduser ${USER} dialout" (This assumes "dialout" is the group shown beside your device in the list above.) Do not: * Try to bypass group membership by running as root. That will create further problems. * Try to change permissions of the serial port you see. They will be lost every time you plug/unplug/logout/reboot. Then logout and back in again so the group membership takes effect. Then go to JMRI Preferences->Connections and the device name you saw earlier should be in the dropdown list once you select a serial connection. If you are still having problems, you need to check the /var/lock directory and remove any stale lock files for the device. This can particularly be a problem if you have ever run JMRI as root. At the same time I saved my Roster files but have not found a way to get it into JMRI under Linux.
Any ideas would be appreciated. I suggest you take a look at these documents. They explain where to find relevant JMRI files, using Dropbox as an example. You won't actually be able to start Dropbox on Windows XP (no longer works with XP), but the principles of what needs to be found where and what to move apply anyway. <> <> Someone else should be able to suggest a suitable interchange file format usable by both Windows and Linux. There's probably a way to read a FAT32 format USB stick in Linux. I'm no Linux expert, but I do use it for testing new JMRI code (I sync files via Dropbox). Dave in Australia
|
I have just installed Linux Mint onto an old laptop running Windows XP and making it dual boot. That was the easy bit. Installed JMRI OK and now I have a couple of minor issues.
As I am using a Sprog for programming will Linux go off and find software to suit or do I use the disc supplied with the Sprog
At the same time I saved my Roster files but have not found a way to get it into JMRI under Linux.
Any ideas would be appreciated.
Thanks
Douglas
|
Locked
Re: Slot monitor is blank
The cable wasn't broken it was just loose where it slides into the body of the loco buffer
I found it by accident when I turned it to get a better look at the green lights to be sure they were both on
When I turned it the cable fell out so I put it back in and all was fixed
They are a slide in fit but have no locking device so they can come loose if they are moved
Mine lays on the floor and can get bumped around
by my feet so I found a spot back out of the way so it is protected and won't get bumped again
Terry
toggle quoted message
Show quoted text
On Aug 18, 2017, at 12:40 AM, walter.stanley.thompson.3@... [jmriusers] <jmriusers@...> wrote:
I assume its s a loconet cable that is 'Broken", how about you trouble shooting friend Tom fixing or building a new cable for you?
[Non-text portions of this message have been removed]
|
Locked
Re: Slot monitor is blank
I assume its s a loconet cable that is 'Broken", how about you trouble shooting friend Tom fixing or building a new cable for you?
|
Circuitron aldo has a DCC Tortoise, called the Smail Leo P On Aug 17, 2017 7:24 PM, "jceiermann@... [jmriusers]" < jmriusers@...> wrote:
Check out Tam Valley Depot's item called Turtle. It is a decoder to drive
a Tortoise machine. I believe the retail is 13.95 ea. Buy 5 or more and the
price drops to 12.95 each.
www.tamvalleydepot.com
Jack Eiermann
[Non-text portions of this message have been removed]
|
Locked
Gamepads & Engine Driver
----------------------------------------
Looking for guinea pigs!
----------------------------------------
Engine Driver has recently added support for using small bluetooth gamepads to control trains. These gamepads provide a simple and inexpensive way to add physical controls to Engine Driver (ED) and therefore JMRI. Just use your phone to connect and select your loco(s), then put your phone away and use the one-handed gamepad on a lanyard to operate your train.
Short video of a gamepad in use with Engine Driver:
So far we have tested this functionality with a few gamepad types in a limited number of situations. We are keen to have other people try with their own devices and give us feedback, so that we can improve the support inside ED.
The gamepads we have used so far are intended for phones rather than full-on gaming and can be used for taking selfies. All cost less than $10 (including delivery) and either have a built in Li-Po battery or work with AA batteries, so they are very affordable.
If you have a gamepad of any sort (or happen to pick one up) we would appreciate you trying it in Engine Driver and giving us some feedback.
------------------------------
Sample gamepads
-------------------------------
-Tested gamepads-
These we have had the most success with¡
They are available from a variety of different sellers on ebay and elsewhere.
These we have had some success with...
-Not Recommended gamepads-
These work, but have issues which make them not recommended.
--------------------
Instructions
--------------------
The following instructions work for the devices first above. Other devices require similar steps, but the mechanism to change the ¡®mode¡¯ may be different.
-Connecting your device-
- On the gamepad, the small button is Start/Power. Press for a couple seconds until LED comes on.
- On your Android device go to the settings, then Bluetooth, and make sure Bluetooth is turned ON.
- Now click ¡®More Settings¡¯. Within a few seconds a new device should appear in the ¡®Available devices¡¯ section. (The name of the device may make it apparent that it is the gamepad, but it may just be a string of hexadecimal numbers.)
- Select the new device. Many devices will be paired at this point, but if it asks for a pairing code try ¡®0000¡¯ or ¡®1234¡¯ (check the instructions that came with the gamepad.)
- After pairing you should see an item in the Notifications regarding the gamepad. Click that item and make sure that ¡°Show virtual keyboard¡± is ON.
- Configuring the gamepad for MTK mode
- Turn your gamepad OFF by holding the Start/Power button for about 5 seconds until the LED goes out and stays out.
- Move the slide switch on the side to the ¡°GAME¡± position (towards the joystick).
- Hold down the button specified in your gamepad instructions for MTK mode. Typically this is the ¡°Y¡± button. While still holding that button down, press the Start/Power button until the LED turns on. Release the buttons as soon as the LED turns on.
This configuration procedure should only be required once. In the future your gamepad should be in MTK mode when you turn it on.
We have found that some gamepads work well in iCade mode as well. Feel free to experiment. To use iCade mode, follow the steps above but use the button your instructions specify for iCade (typically ¡°X¡±).
-Setting up Engine Driver
- Start Engine Driver
- In the Gamepad section of Engine Driver¡¯s Throttle Preferences, select a gamepad corresponding to the gamepad mode you configured on the device (above). We recommend ¡°MTK-rotate¡± for MKT mode, and ¡°iCade+DPAD-rotate¡± for iCade mode.
- You can also change the other gamepad Preference, which sets the action for a short press on the Start/Power button.
-Running Engine Driver-
- In Engine Driver, select a loco as normal and return to the Throttle page.
- The DPAD (joystick) on the gamepad will control throttle up, down and direction.
- The four individual Buttons on the gamepad will control functions F0, F1, F2 and STOP for the selected throttle.
- If you have engines assigned to more than one Engine Driver throttle, by default a short press of the Start Button will move the gamepad to the next assigned throttle. If you changed the Preferences for the Start Button Action to ESTOP, then a short press will set the speed for all your Engine Driver throttles to zero.
- If the Select Button is present on your gamepad, pressing it will move the gamepad to the next assigned throttle.
- Engine Driver¡¯s on-screen buttons continue to function as before. Use them to add or drop locos, and to access any additional function buttons.
---------------
Feedback
---------------
If you do try it, please provide any feedback (good or bad) here on the Forum.
Thanks
Steve Todd, Robin Becker, Peter Akers
|
Check out Tam Valley Depot's item called Turtle. It is a decoder to drive a Tortoise machine. I believe the retail is 13.95 ea. Buy 5 or more and the price drops to 12.95 each.
www.tamvalleydepot.com
Jack Eiermann
|
Locked
Partial Resets with WOW decoders.
Gentlemen & Others,
I put this post on the TCS group, and it was suggested I put it here as
well.
- - - - - - - - - - - - - - - - - - - - - - - -
Terry,
I will put this post here as it may help others who are having problems.
You say that Decoder Pro reset of a WOW decoder does not work - you are
partially correct. Going back a few versions of DP, Michael added the
CV8 = 2 to the reset table - I think about ver 4.8. Well, this partially
works and before someone says "Use Audio Assist" - that works the same
way - does not do a full reset.
I will explain - I do a lot of installs and from time to time I have to
do a full reset. On one of my own locos I lost the chuff - everything
else worked except the chuff. It was as though the chuff cam had been
turned on, but it hadn't been turned on! Did three resets from the
command station - CV8 = 2, then three resets with Decoder Pro, then
three resets with Audio Assist with 10-20 secs of no power between each
reset - still no chuff.
I then did something with Decoder Pro that you cannot do any other way -
after a reset I did a read of each page to see what changed from the
"original, out of box" settings. On the Motor page the values for CV3
and CV4 had gone from 32 / 96 to 5 / 5 - no big deal, I expected that.
Then on the Sound page, the loco type came back as "Reserve Value 2xx" -
very odd. I went through all the pages and checked each one, no other
strange settings.
I went back and programmed the loco type to 'medium' and ran a test -
everything worked as it should. Strange that CV8=2 did not set that back
to default.
In Decoder Pro it says that CV8=2 does NOT reset the speed table - I
never use the speed tables in WOWs - no need - just use CV5 and CV6.
This happened to be a rare occasion that my brain was in gear and
working. I had another WOW in a rarely used loco that gave a slight kick
on start, it had a poor mechanism so I did not worry about it. So, on
the program track, Decoder Pro read the speed table, it was up and down
like a dogs dinner! The table was not being used but I set to 'straight
line' anyway and programmed. This fixed the start problem, so there was
some corruption internally in the memory - much like my memory.
I had two other "strange" happenings (no full moon) that have been
"fixed" in the same way in other decoders. I thank the people at JMRI -
especially Michael for all the work on Decoder Pro.
I currently have Ver 4.9.3 installed which has all the updates - DO NOT
use V4.9.2 wait for Ver 4.9.3 or use Ver 4.8.
Just my weekly ramble
Gerry
--
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder
NMRA Australasian Region
Contest & AP Chairman
Web Administrator
|
You can get Tortoise with onboard "drivers" or without and then use an external driver. There are several options for external drivers. JMRI can then be used to control them.
My display will allow me to click on a button and control the switch state as well as display the state it's in.
toggle quoted message
Show quoted text
On Aug 17, 2017, at 4:03 PM, Richard Bell katmedia@... [jmriusers] <jmriusers@...> wrote:
Hello Fick. Is the Tortise driver part of jmri or is it part of the Tortise mschines? I use Tortise machineson my layout but I have never used jmri to vontrol my layout. It sounds like something I may delve into in the future.
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------
From: "Dick Bronson dick@... [jmriusers]" <jmriusers@...>
Date: 8/16/17 8:49 PM (GMT-07:00)
To: jmriusers@...
Subject: Re: [jmriusers] Tortoise wiring
Richard,
JMRI only sends the commands to change positions. The Tortoise driver
remembers the last command and supplies power continuously to keep the
Tortoise from drifting.
Dick :)
On 08/16/2017 04:12 PM, Richard Bell katmedia@... [jmriusers] wrote:
Sorry, I didn't think that jmri was giving a continuos signal to the Tortise.
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------
From: "'Jim Duncan' jdbandman@... [jmriusers]" <jmriusers@...>
Date: 8/16/17 12:25 PM (GMT-07:00)
To: jmriusers@...
Subject: RE: [jmriusers] Tortoise wiring
Ya, but if they accidentally let it go while moving over the switch it's
going to return to whatever position the DS had it set to originally... Can
you say "break out the Dixie cups!"????
JD
-----Original Message-----
From: jmriusers@... [mailto:jmriusers@...]
Sent: Wednesday, August 16, 2017 11:25 AM
To: jmriusers@...
Subject: Re: [jmriusers] Tortoise wiring
I would add if you can locate spring loaded dpdt switch, the local crew can
hold the switch in the "Hand" position while they operate the toggle for the
switch motor. When they are done, releasing the spring loaded switch will
return the control to JMRI automatically. Dispatcher then has control again
without relying on the crew to return control. Cheers!
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------
From: "'Jim Duncan' jdbandman@... [jmriusers]"
<jmriusers@...>
Date: 8/16/17 10:05 AM (GMT-07:00)
To: jmriusers@...
Subject: RE: [jmriusers] Tortoise wiring
Put a second DPDT toggle in. The 2 center pins to the switch motor. Top pair
to JMRI connection. Bottom pair to local control toggle. Label above
selector as follows: Above "HAND" Below "POWER".
Now the DS can give your crews permission to take switch on hand! Just
remember to remind them that they need to tell the DS when they are
returning control of the switch back to him!!! It DOES tend to annoy
dispatchers when they can't throw a controlled switch and the local crew is
now several miles on down the line and there's mobody around to restore the
switch to the power position! <G>
Jim Duncan
-----Original Message-----
From: jmriusers@... [mailto:jmriusers@...]
Sent: Wednesday, August 16, 2017 10:31 AM
To: jmriusers@...
Subject: [jmriusers] Tortoise wiring
I have my tortoise machines wired to dpdt switches on the facia. a common
installation.
I now want to wire the to RR-Cirkits Signalman boards for use through JMRI
panel pro.
Can anyone tell me how I would wire the so as to still retain control on the
facia when I am not using JMRI.
Thank you
JZ
[Non-text portions of this message have been removed]
------------------------------------
Posted by: mt813@...
------------------------------------
------------------------------------
Yahoo Groups Links
[Non-text portions of this message have been removed]
------------------------------------
------------------------------------
------------------------------------
Yahoo Groups Links
[Non-text portions of this message have been removed]
------------------------------------
------------------------------------
------------------------------------
Yahoo Groups Links
------------------------------------
------------------------------------
------------------------------------
Yahoo Groups Links
|
You need something like a
Digitrax DS64 Stationary Decoder, It controls 4 Turnouts
The JMRI software would send commends to a DSS Command Station.
The DSS command station would send signals to a stationary decoder.
The stationary decoder would then change the turnout position.
Brian K
|
Hello Fick. Is the Tortise driver part of jmri or is it part of the Tortise mschines? I use Tortise machineson my layout but I have never used jmri to vontrol my layout. It sounds like something I may delve into in the future.
Sent from my Verizon, Samsung Galaxy smartphone
toggle quoted message
Show quoted text
-------- Original message -------- From: "Dick Bronson dick@... [jmriusers]" <jmriusers@...> Date: 8/16/17 8:49 PM (GMT-07:00) To: jmriusers@... Subject: Re: [jmriusers] Tortoise wiring Richard, JMRI only sends the commands to change positions. The Tortoise driver remembers the last command and supplies power continuously to keep the Tortoise from drifting. Dick :) On 08/16/2017 04:12 PM, Richard Bell katmedia@... [jmriusers] wrote: Sorry, I didn't think that jmri was giving a continuos signal to the Tortise.
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------
From: "'Jim Duncan' jdbandman@... [jmriusers]" <jmriusers@...>
Date: 8/16/17 12:25 PM (GMT-07:00)
To: jmriusers@...
Subject: RE: [jmriusers] Tortoise wiring
Ya, but if they accidentally let it go while moving over the switch it's
going to return to whatever position the DS had it set to originally... Can
you say "break out the Dixie cups!"????
JD
-----Original Message-----
From: jmriusers@... [mailto:jmriusers@...]
Sent: Wednesday, August 16, 2017 11:25 AM
To: jmriusers@...
Subject: Re: [jmriusers] Tortoise wiring
I would add if you can locate spring loaded dpdt switch, the local crew can
hold the switch in the "Hand" position while they operate the toggle for the
switch motor. When they are done, releasing the spring loaded switch will
return the control to JMRI automatically. Dispatcher then has control again
without relying on the crew to return control. Cheers!
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------
From: "'Jim Duncan' jdbandman@... [jmriusers]"
<jmriusers@...>
Date: 8/16/17 10:05 AM (GMT-07:00)
To: jmriusers@...
Subject: RE: [jmriusers] Tortoise wiring
Put a second DPDT toggle in. The 2 center pins to the switch motor. Top pair
to JMRI connection. Bottom pair to local control toggle. Label above
selector as follows: Above "HAND" Below "POWER".
Now the DS can give your crews permission to take switch on hand! Just
remember to remind them that they need to tell the DS when they are
returning control of the switch back to him!!! It DOES tend to annoy
dispatchers when they can't throw a controlled switch and the local crew is
now several miles on down the line and there's mobody around to restore the
switch to the power position! <G>
Jim Duncan
-----Original Message-----
From: jmriusers@... [mailto:jmriusers@...]
Sent: Wednesday, August 16, 2017 10:31 AM
To: jmriusers@...
Subject: [jmriusers] Tortoise wiring
I have my tortoise machines wired to dpdt switches on the facia. a common
installation.
I now want to wire the to RR-Cirkits Signalman boards for use through JMRI
panel pro.
Can anyone tell me how I would wire the so as to still retain control on the
facia when I am not using JMRI.
Thank you
JZ
------------------------------------
Posted by: mt813@...
------------------------------------
------------------------------------
Yahoo Groups Links
------------------------------------
------------------------------------
------------------------------------
Yahoo Groups Links
------------------------------------
------------------------------------
------------------------------------
Yahoo Groups Links
[Non-text portions of this message have been removed]
|
Locked
Re: Engine Drive dispaly
Thank you, This worked great.
Brian K
|
Locked
Re: Engine Drive dispaly
Brian,
There is also a menu option, "Clear Recent List", that will clear all but my demo server.
HTH,
SteveT
|
Locked
Re: Engine Drive dispaly
Thank you for your reply. No, it is not your test server. I will do what you suggested.
Thank you
Brian K
|
Locked
Re: Engine Drive dispaly
Hi Brian,
I'm assuming you are referring to the "jmri.mstevetodd.com:44444" entry? If so, that is my demo site and can't be removed from the list.
Note that if you're always connecting to the same server, you should enable the Preference "Connect to First WiThrottle Server" and you'll bypass that screen altogether.
HTH,
SteveT
|
I am running ¡°Engine Driver¡± on an Android. It is working great.
However, under ¡°Recent Connections¡± there are two entries.
Only one is correct, how do I delete the one that is not correct or is it OK to leave it displayed?
Brian K
|
Locked
Re: Test version 4.9.2 of JMRI/DecoderPro is available for download
Bob,
The same error occurs if I try to "accidentally on purpose" create a bad SSL entry. The bad entry will be saved in the panel xml file.
Since most people don't run with the console log displayed, they will not know they created an error. This should probably be a dialog and prevent the retention of the bad entry.
Dave Sand
|
Locked
Message from Simple Signal Logic (Re: Test version 4.9.2 of JMRI/DecoderPro is available for download
Sorry to come to this late, day job delays due to school starting. That error message is a new one in 4.9.2. Before that, because of the way that Simple Signal Logic worked was somewhat complicated, an individual piece of logic couldn¡¯t really notice that it wasn¡¯t controlling a signal. That¡¯s fixed now, an SSL unit can notice, and it emits that message automatically. That seems reasonable: Why should it exist if it¡¯s not actually changing anything? But the message is pretty obscure. I¡¯ll try to improve it. Bob On Aug 17, 2017, at 4:48 AM, Craig Goodyear cjhs22a@... [jmriusers] <jmriusers@...> wrote:
On 08/16/2017 10:20 PM, dave@... [jmriusers] wrote:
Craig,
The error appears to be caused by a SSL entry that was created for T5TD with the "On Single Block" option, but no "Protects" sensor or signal was supplied.
Dave Sand
Thanks to everyone for the replies.
Dave, correcting the T5TD entry, eliminated the error message. Problem
solved.
Craig
-- Bob Jacobsen jacobsen@... +1-510-708-5988 AIM, Skype JacobsenRG
|
Peter Akers
RickyB
Bob Jacobsen