Today I turned the railroad on and found out the LocoBuffer can't talk
to the DCS100 anymore. This is what it said;
Stopping due to error: Timeout talking to command station.
I tried both 19,200 and 57,600 and the report was the same for both*. Next
step was to setup for the MS100. Success as the MS100 now works fine.
Tried one engine and although it identified the decoder wrong it was
progress. Copied my roster from the old file to the new location and it
doesn't show up when I try to identify a loco. I know this has got to be a
cockpit problem so what am I doing wrong with the roster?
Oops - hadn't thought people would want to do that.
In addition to copying the .xml file for the individual loco, there's an index that needs to be copied in the "roster.xml" file itself. Could you move a copy of that over and try again?
The problem with the LocoBuffer is more serious!
*LocoNet monitor works with the MS100 and not the LocoBuffer!
Could you check something for me?
The installer should have removed the old communications port files:
<JAVAHOME>\lib\javax.comm.properties
<JAVAHOME>\bin\win32com.dll
and replaced them with:
<JAVAHOME>\lib\ext\jspComm.jar
<JAVAHOME>\lib\ext\Serialio.jar
<JAVAHOME>\bin\jspWin.dll
where "<JAVAHOME>" is the Java install directory, something like:
C:\Program Files\Java\j2re1.4.0
or
C:\Program Files\JavaSoft\JRE\1.3.1
depending on which version is there.
Could you check that the old files are gone, and new ones are present? Thanks.
Alex is having a similar problem, which I've not yet been able to recreate and track down.
ps, I like the tree form.
Should I keep that one?
Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
Bob Jacobsen