gmpullman Stevert Note that the author of that Web page really likes Dropbox; I have since used the Dropbox backup and auto-save. The great advantage to me is that I have several computers running Decoder Pro and any change I make to a roster file is immediately seen on the other computers.
Stevert
Note that the author of that Web page really likes Dropbox;
I have since used the Dropbox backup and auto-save. The great advantage to me is that I have several computers running Decoder Pro and any change I make to a roster file is immediately seen on the other computers.
Placing my roster file on a network share gives me the same advantage, even if my Internet service is down. I'm not dependent on an Internet connection to the "cloud" to keep my files in sync across computers.
StevertNote that the author of that Web page really likes Dropbox;
Some years ago I also wiped out my JMRI roster after a hard drive failure. No problem, though, everything was backed up on a 3½" floppy*. Except that I couldn't find it! At least back then it was only about 50 entries.
*that will give you an idea of how long ago.
This is handy when I make changes at the test track using the Sprogg or modifications at the layout. I just use the free, basic Dropbox.
Even a backup onto a cheap flash-drive can prevent hours of aggravation...
Thank You, Ed
willy6 I have been learning and using JMRI for about 6 months and think it's great. I have made mistakes using it and my biggest one was when I deleted my entire roster of 21 locomotives cannot figure out how I did it and don't know if I can recover it.
I have been learning and using JMRI for about 6 months and think it's great. I have made mistakes using it and my biggest one was when I deleted my entire roster of 21 locomotives cannot figure out how I did it and don't know if I can recover it.
I'm a long-time JMRI user (15+ years), and I keep my roster of about 90 locos, a DCS100, a PM42, and 10 DS64's, as well as some other JMRI files, on a shared network drive that's backed up twice daily.
There is a JMRI Web page for setting this up with Dropbox, however, pretty much the same thing can be set up with any kind of network share. You can also use the information there to set up a backup of your "critical" JMRI files to an external drive, etc.
Note that the author of that Web page really likes Dropbox; In my case at least, not having any of what they call Dropbox's "advantages" hasn't impacted me in any way at all - I don't have multiple platforms, my network latency is nil, my server is up 24x7, etc. So you don't HAVE to use Dropbox to gain some benefit.
Congratulations! Get those trains rolling!
Old Fat Robert
You're right Randy. Now that I think about it, the JMRI throtte was sporatic in it's working. I suspect it worked when JMRI wasn't connected to the MRC, perhaps it happened when the Decoder Pro wasn't loaded. I was in various states throughout the problem, so that could have easily happened. That would explain why the JMRI throttle worked sometimes and not others.
I don't see how the JMRI on screen throttles would have worked if the COM port for the interface was wrong though. It all goes out via the same computer interface to the DCC system regardless of which component of JMRI you are using.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
VICTORY AT LAST!
I changed from Com Port 1 to Com Port 3 and it started working for the first time. I didn't focus on that possible conflict since there is nothing else connected to the PC.
I found it by pouring through the JMRI documentation and discovered an "Install Test" feature buried in the Windows Program file. Ran it and it Errored on Com Port and every test after that Errored. I switched Ports and reran the intall test and all the Errors went away. I then recycled the connection to the server and nerviously eased the throttle ahead. My steam engine began to chug forward with boisterous sound.
I'm looking forward to doing a lot with JMRI as the layout construction continues.
Thanks for the suggestions, I followed each one through while looking for the solution. As it turns out, if the problem had been a rattlesnake, I'd be dead now it was so close to me.
Deane: I am afraid that I have been thinking. Dangerous for me! Seems that I remember having to enter the port number on the tablet(s) whenever I operated using those devices. Have you had the opportunity to check that?
I can confirm that the addresses were entered correct, and that the function keys track each other when both the JMRI throttle and the iPad have acquired the same address.
I should mention that I have merely been putting the address into the Keypad box and "Setting" it, getting a green entry. The locos are not listed in any charts or on any lists in JMRI. I doubt that means anything, but I don't want to leave anything out.
I've spent literally hours on this today, trying all sorts of things, and nothing has changed the basic problem. The iPad throttle appears to function as if everything was golden, there is just no response from the engine. I have tried it with several engines. WiThrottle indicates the connection is good between WiThrottle and the targeted Decoder.
At least I've developed a lot of familiarity with JMRI in a hurry during my first day at it. I really like JMRI.
Make sure that your address put into the ipad for the locomotive is correct. Another thing you could do is aquire the same locomotive on JMRI and WIthrottle to see if when you trigger a functon on one, the same function button on the other automatically indents to register that the function is toggled
I'm beginning to realize that Windows 10 and sound decoders have a lot in common. There are so many things you have to change in order to get them to work the way you want.
I don't believe that is the case with MRC. I've been using Cab 1 with the RF handheld controller. However, your post will trigger me trying Cab 3 just to see what happens.
Thanks
Deane: Now I have a question for you. I use NCE (love it!). I am kind of under the impression (on NCE) that "cab 1" is the power supply and "cab 2" is the hammerhead throttle, leaving the additional cab #s to be 3, 5, 7 etc. I always assigned my Kindle to cab 4 and had no trouble. I assume that this is not the case in MRC (and probably not in NCE either) - just curious.
Thanks Robert. I believe the location of the Cab selection may have moved from where you remember it, but I found it and it was properly assigned to Cab 1. All other Cabs are unassigned and disconnected.
The Panel Pro shows the iPad, and shows which Loco it's connected to. That's what's baffling me. All of the chain appears to be humming along like it should, it's just that no instructions are being sent to the Decoder, even though JMRI shows the iPad connected to the Engine Decoder.
JMRI appears to be a really neat system, and one I want to master, but it's certainly not for the timid.
Deane
Deane: I believe your problem is caused by the lack of a cab number for your Ipad throttle. Going off memory (always interesting in my case) when you open JMRI the "main" ops panel in the center of your computer screen has a drop down for throttles and a debug selection. One of the options is "configure cab". That should open a small box in the upper left of your screen that allows you to put a cab number to your Ipad. I think that will do it for you. Good luck.
Just getting started with JMRI and learning.
Setup:
JMRI on dedicated PC connected to MRC Prodigy Advanced 2 with MRC USB cord
Engines operate normally using JMRI internal Throttles.
iPad connects properly to JMRI Web Server.
WiThrottle on iPad shows green connection light indicating proper connection with selected decoder number (engine number).
Here's the problem: iPad throttle then does nothing. No throttle response, no function button response. The engine just sits there at idle.
I tried two different engines with the same result. I must have something set wrong so that the controls of the WiThrottle aren't doing anything. But, where to look????
Thanks for any ideas,