Could anyone give me some insite why I would be getting a error message “timed out talking to command station” (or something VERY close) and not connecting to the Loconet? I’ve used the Locobuffer II and JMRI DecoderPro in the past without a problem. Yesterday, I downloaded the newest version (1.6.?) of Panel Pro, set everything up the exact way I had decoder-pro set, and no dice. I rebooted the laptop (100 times), checked all the cables, re-read the directions, cleaned the programming track, tried different engines, etc. Anyone have any ideas what I’m missing or doing wrong??
There was an issue with one version of JMRI not working either after installign it over an older one, or installign it without an older one having been installed first. Dunno if they fixed that on the latest release or not. You mght want to check on the Yahoo group for JMRI.
Also check your port settings in device manager - be sure to run on hardware handshake there, and simply setting it in the JMRI preferences is not enough, the Java comm libraries apparantly do not implement setting the port parameters correctly (yay for ‘runs on all platforms’ yeah, it does, in a mediocre fashion. While I really like JMRI, as a programmer I HATE Java). Anyway, check that all out, and then verify the settings in JMRI. Also check the activity lights - with the Locobuffer up and running, any time you move the throttle or press an F key or so anything, you should see the loconet activity indicator blink. If it doesn’t - you have a problem with the cable between the Locobuffer and the command station.
–Randy
JMRI has a Yahoo group JMRIUsers they should be able to help you with in depth assistance. Their site also mentioned about that install problem that Randy mentioned.
Good Luck
Jesse
Randy,
should have mentioned that the activity light flickers when I make a throttle change, so I assume the Loconet is at least talking to the locobuffer II. I also get both green lights on the Locobuffer as well. I’ve checked the settings against what I had with the old version and they are the same. I’m thinking of deleting the entire program off the laptop and starting over.
Jessee,
Thanks for the users group info, I’ll try that after work tonite!
That message means that JMRI can’t talk to your DCC system. It usually happens because of a reconfiguration of either the hardware or the JMRI settings. Double-check those and if you don’t find it, post in the JMRI Yahoo! group as Jesse suggested.
Be sure to include a complete description of all the hardware/cables/etc, as well as your JMRI version and settings, operating system, etc. *** Bronson (builder of the LocoBuffer II) also has a “Basic LocoBuffer II Sanity Test” that might be helpful.
JMRI Users Group:
http://groups.yahoo.com/group/jmriusers/
*** Bronson’s LocoBuffer II:
http://www.rr-cirkits.com/LocoBuffer-II/locobuffer-II.html
HTH,
Steve
For destktop development Java leaves a little to be desired. However, given the cross platform alternatives,…wait, there are no alternatives… 
Having tried everything X, to VB, to C, to Java, Java is the lesser of all evils IMHO. I smell a market opportunity here…
-Tom
Fncota, I had the same problem that you are having and Randy’s suggestion on the Port setting fixed the problem for me. For some reason my windows XP was not setting the port parameters correctly so I had to set it for them.
Hey everyone,
First, thank you all for the suggestions. What I ended up doing last night was just deleting the update (panelpro) and running the older version (decoder pro). Now everything works fine. I will go to the JMRI site later and see what they say. Thanks again!
Fred