开云体育

from germany, many greetings to all and bob in post 101 I want to give an information: is here every boddy from Europe? I have translated the introduction to this Group: Modellbahnbetriebsysteme. Das J/MRI wurde gestartet um Modellbahnbetriebsysteme mit dem Computer einzusetzen. Wir wünschen uns dies, um für eine m?glichst gro?e Anzahl von Anwender es bereitstellen zu k?nnen. So haben wir die Plattform in JAVA geschrieben um es irgendwo auf einem beliebigen Computer einsetzen zu k?nnen. Es ist also die Plattform, um es unabh?ngig zu machen von einer spezifizierten Hardware und Software. Es geht um die Beseitigung der Flaschenh?lse, also um alle Systemfehler der früheren Generationen der Hardware von Rechner- und ?bertragungs- system (Motorola und DCC), die auszumerzen sind. Es ist der Ausgangspunkt für Amateure, welche ihre Modellbahn von einem Rechner steuern wollen, ohne selbst ein Baukasten-System aufbauen zu müssen. ?hnlich wie beim C/MRI zuvor, ohne Umbau von Lok und Wagen, soll es jetzt mit DCC Komponenten umgehen k?nnen und über Bussysteme oder UBS mit der zus?tzlich notwendigen Elektronik verbunden werden. Es soll die schnellere Installation und preiswerte Systemanpassung f?rdern. Durch offene Programme und Betriebssysteme wie LINUX ist dies m?glich und investitionssicher. Auch die Protokollsprachen des Internets und der Austausch über Client Server und UBS erm?glichen mit robusten BUS- Systemen wie LocoNet die ?bertragung an die Ger?te, die Modellbahnen steuern. Für Modulanlagen hat hier FREMO bereits Vorleistungen bereit gestellt. Um dieses zu verwirklichen haben wir die Probleme in zwei Teile aufge- teilt, die im dazwischen befindlichen Teil im Interface Protokoll liegen. In der unteren Schicht ist der Code für die Anschlüsse der spezifizierten Anlagen – Hardware. Darüber liegt das Interface Protokoll für die Programme die Anwender wünschen. Die langfristige angelegte Strategie ist die Konstruktion eines Sets von ?ffentlichen Programmen für jede Art von Typ der Anlage und Typ von Computer. Bob Jacobsen translate dieter

Well, I installed JMRI on my 1 year old laptop and it says that my COM port can only be set to 9600. I don't understand the reasons why. Anyway, if this is true for JMRI, what about other loconet apps? Will any software work on my laptop, such as pr1dos, ... with an MS100 or PR-1? If I get a Locobuffer, will that work either? Thanks, Greg

Hi Bob, I found the jars etc for SerialIO and could make it compile, however it still timed-out. I suspect that the SerialIO package is interfering with Sun's commapi serial port stuff that you use for everything but MS100. I had a quick look at the SerialIO site and I got the impression that we should be able to configure the commapi to use the SerialIO package and not the default Sun Win32Com package. However, when I deleted all the SerialIO jars and dll and put copies of the commapi files in various places (the docs must be wrong!!!) until DecoderPro found them, it all worked again. I think I quite like the tree view. Also when I tried to do an Ident of my loco with a DN149K2 decoder it came back with an error: Found mfg 129 version 241; no such manufacterer defined This was the same with both of my locos and both have DN149K2 Plug and Play decoders Cheers Alex

Sorry to have been so out of touch; I've been working on the PC <-> MS100 connections. To make a long story short, I've uploaded a test installer to: http://prdownloads.sourceforge.net/jmri/Setup.0.9.3.4.exe for a DecoderPro version that should be able to talk to an MS100 on most(?) PCs. I would greatly appreciate it if people could give it a try and let me know whether it works. I've tried it with an HP PC under Win95 and XP Personal Edition. I'm particularly interested to know if it installs properly and works on other windows versions, and if there's any particular hardware that it has trouble with. Thanks in advance. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957) Am working off a huge email backlog, call if it's urgent.

OK, started checking things out and this is what I found. As I said before I had a successful install. 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? The problem with the LocoBuffer is more serious! *LocoNet monitor works with the MS100 and not the LocoBuffer! ps, I like the tree form. Jon Miller AT&SF For me time has stopped in 1941 Digitrax DCC owner, Chief system NMRA Life member #2623 Member SFRH&MS

I've uploaded a new test 0.9.3.5 version of the Windows installer version. I hope that this is starting to converge ... This is meant to test a new GUI for selecting the decoder model. This one displays the decoders in a tree form. This seems to be the logical next step from the last set of changes, which were still somewhat confusing with Soundtraxx's complicated product line. This seems somewhat simpler. I would _very_ much like feedback on whether this is an improvement. I'd like to settle on one of the three (original selection boxes, the one with manufacturer and decoder lists, and this one with the tree) of these within the next week. Also new, hence needing testing: Digitrax FX3 decoders Additional older Lenz & Digitrax decoders Create decoder index automatically in case of mismatch New LocoTools application, which gathers in one place the various LocoNet tools in the JMRI libraries JMRI demo is now installed by default Users with an Empire Builder will have their "read" buttons disabled & labeled so its clear why they don't work. Two minor bugs in the Lenz LI100 fixed; now works well with the Atlas Commander The file is available in the usual place on SourceForge: http://prdownloads.sourceforge.net/jmri/Setup.0.9.3.5.exe This is just about the end of my high-priority list of changes. Nowhere near the end of the entire list, of course, but at least to the point where I won't be embarrassed handing it out to people. So, after fixing the inevitable bugs, the next step is to pull together some documentation and create a master CD. Help would be greatly appreciated. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957) Am working off a huge email backlog, call if it's urgent.

I have not yet been able to fix the LocoBuffer communications in the 0.9.3.5 test installer. The problem appears to be that the "RTS" lead, pin 4 in the 25 pin connector, is not being driven active. The LocoBuffer won't transmit until it see this. I hope to make progress on this today. As a minimum, I'll create a "LocoBuffer without MS100 installer" if I can't make them both work from the same installer. Sorry for the inconvenience. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

PC Magazine has a nice, free, icon editor: IconEdit32. I used it to add a 48x48, 16 color icon to go with the existing 16x16 and 32x32 icons if anybody cares to have it. (48x48 icons are used for the Desktop only if you have Use Large Icons checked in Display Properties, otherwise 32x32 icons are used on the Desktop. 32x32 icons are always used in Explorer's Large Icon view, and 16x16 icons are used in the Programs menu and Explorer's List, Details, and Small Icon views.) The updated icon file is at http://home.earthlink.net/~n3ix/dcc/decpro.ico To get this file, go to http://home.earthlink.net/~n3ix/dcc/ then Right-Click on decpro.ico, and select "Save Target As" to copy the file onto your machine. Unfortunately, IconEdit32 does not come with artistic ability so if we want to have nicer versions and/or 256 color icons someone with talent needs to step forward! Robin

At 1:47 PM +0000 7/9/02, rjs4005 wrote: >I would like to see if there is a way to detect and add new decoders >in to the listing you've created. There is. The decoders and programming screens are defined by text files. The beginnings of some documentation are at: http://jmri.sourceforge.net/PaneProg/ConfigFile.html The documentation needs work, of course, and we need some better tools to help editting. But its a place to start. There are a couple of people on this list who have written definition files, and can help. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

In one of those recurring moments of optimism, I've uploaded a new Windows installer. I hope that this one works well enough that I can spend some time updating the documentation, creating the versions for other machine types, and then burn some CDs labelled "version 1.0". Some of you may recall that back in April we were talking about doing that before the NMRA convention next week... Most importantly, it contains a fix for the LocoBuffer communications problems introduced in the last version (0.9.3.5). It should work with LocoNet via LocoBuffer and MS100, and with NCE, EasyDCC and Lenz command stations. The file is available at: http://prdownloads.sourceforge.net/jmri/Setup.0.9.4.exe and the usual mirror sites. Please, try it and let me know whether it works or not! The change log also contains: Lenz direct mode fixed. Improvements to decoder selection GUI tree: Better handling of small decoder families, Improved layout (still more to do!) Minor fix to Digitrax FX3 decoder definition. Fixed JmriDemo, LocoTools program items so they actually work. Added "Owner" item to roster entries, so you can keep track of which club member owns a particular loco. Improved start up time on machines with a small amount of memory. Known problems: Robin's new icons seem to only appear on the program files, not on the shortcuts to the program files. The shortcuts get the old icons on machines that have had previous versions installed. Several great suggestions for additional improvements to the GUI were not (yet) made due to lack of time. I've not forgotten them! Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

I've uploaded a version 0.9.4 for those of you without Windows: MacOS X: http://prdownloads.sourceforge.net/jmri/JMRI-X.0.9.4.hqx MacOS 8/9: http://prdownloads.sourceforge.net/jmri/JMRI.0.9.4.hqx Linux: http://prdownloads.sourceforge.net/jmri/JMRI.0.9.4.tar.gz OS/2: http://prdownloads.sourceforge.net/jmri/JMRI.0.9.4.zip People didn't like the "one size fits all" distributions, mostly because they contain lots of irrelevant & confusing files on any given machine, so I've gone back to creating separate distributions. The tools to create these are new, however, so I'd appreciate it if people could try the download for their particular machine and let me know if it works. Having separate installers also lets us see how many people use each one. That will be interesting. Vote early and often... Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

At long last, the 1.0 version is available. There's still a long way to go, of course. The wish list keeps growing. But I think we've got something that basically works, and I wanted to have a specific version to build on. Hence the 1.0 downloads. The files are available at the usual download sites. I've also simplified the README file and split it into smaller chunks. I'd appreciate comments & suggestions on this: http://jmri.sf.net/README.html I also did some overhauls of the general web pages, updating some of the figures, etc. For those of you who have 0.9.4 installed, the differences are: New Lenz decoder Minor fixes to GUI (spacing, etc) Better handling of errors if client libraries are not properly installed Small improvements to startup time on Linux machines Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

(This might be of more general interest, so I'm cc'ing it to the list) You're using Windows 98 if I recall correctly. The versions of the program before the installer (e.g the ones where you unpack and move a bunch of files) put things in a different place. So when you run the installer from your CD it will properly install the new program, but it _won't_ remove the old one. Because of the different positioning of the files, you're preferences won't carry over from an old (pre-0.9.3 version without the installer) to the new one. This is a one-time problem. The installer is meant to prevent it from happening in the future, but I didn't see how to automate the switch-over. Setting the preferences for port, etc, is not such a big deal, but people with large roster's might be annoyed at losing them. There are really three choices for how to deal with this: a) Recreate the roster by re-reading each locomotive. That's slow, but reliable. b) If you're using a recent-enough version, you can "export" each locomotive to a file using the "Export" command in the "Roster" menu, then "import" it into the new version of the program. This is a hassle, and I suspect that you've probably got a version of the program before the Roster menu was added. c) You can move the old preferences to the new location. "Well, why didn't he suggest that earlier?" you're probably thinking. Because it's not as simple as I'd like, or as it sounds. The problem is that there are so many different ways for Windows machines to be set up that I can't give a specific directory name for the new preferences; Windows gets to decide where it goes, and Windows is quite schizophrenic about this. I _think_ the following steps will work: 1) Run the new installer. This won't hurt your current version of the program, which will continue to work fine. 2) Start DecoderPro from the desktop shortcut or program menu. (Make sure the 1.0 version starts, not the old one) 3) Set it's protocol and port preferences, save and quit. 4) Ask Windows to search for a file named "DecoderProConfig.xml" with that capitalization. 5) The search will find one in a "prefs" directory in each of your old program downloads. It should also find a brand-new file (check the date & time) in a "JMRI" directory. That "JMRI" directory is the new preferences directory. It might be under "Windows", "My Docs", "User Docs&#92;Owner", or something else. 6) Copy the following files from the old "prefs" directory to the new "JMRI" preferences directory: roster.xml The roster folder, and all it's contents I suggest copying instead of moving so that the old copy of the program will still be working, even if the new one has something go wrong. 7) Move the "DecoderProConfig.xml" file from the _new_ directory to the trash. 8) Start the new program, re-enter your protocol and port preferences, save. Before quitting, you might want to check that your roster of locomotives shows up; if so, just pop the programmer window and check the list at the top. 9) Quit and restart. My apologies for the length of this procedure. I didn't know how to automate finding those directories in the installer, so I didn't know how to get it to do that. If this doesn't work, please let me know so I can figure out why. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)

Some time ago I downloaded version 0.9.3 of DecoderPro, only to find it wouldn't work with a Digitrax MS100 PC interface. I must admit that although it didn't work with my system, I found them programs functionality very appealing. Anticipating improved (hardware) support and recognizing the potential of the program, I decided to lurk around this news group and monitor program development. Last Friday I downloaded the latest Java Plug-ins (Version 1.4) and the Windows version of DecoderPro 0.9.4. I've been busy testing it out since then. The developers of DecoderPro are to be commended on its recent release. The install went very smooth with setup immediately detecting a recently installed LocoBuffer device. Over the weekend I spent considerable time using the program, establishing speed tables in two Lenz LE077XF decoders. Having done so I would like to offer the following for consideration; A CV value display should be added above each slide bar utilized in the setting of the twenty-eight speed steps. This would help users visualize the CV value each slider is set to without flipping to the CV window. Perhaps I'm the only one that does this, but I use a spread sheet to calculate my speed steps then input those calculated values into each of the twenty-eight speed table CV's. For example; the CV's of one of the Lenz Decoders where calculated as 22, 24, 26, 28, 30, 33, 36, 38, 42, 45, 49, 53, 57, 62, 67, 73, 79, 85, 93, 100, 109, 118, 127, 138, 150, 162, 175 and 190. Setting these values was difficult as I found it necessary to toggle back and forth between the Speed Table and CV window in order to set each value. I tried inputting the data directly into the CV table (CV 67 to 94) but found the desired values where not transmitted to the decoder and subsequently all speed step values were set to that of CV 67, in this case 22. Also, I'm sure I read a message within this NG that indicated the Read Buttons of DecoderPro would be greyed out if the application was interfaced with a Digitrax DB150 Command station. I've such a station and found the buttons are still active. Keep up the great work. Bob Blackwell O/O AFTICARR

Everyone, What do you think about an information pane? [Info] One pulldown where we could just put text as to what we know about that decoder and what versions might do what. That way the programmer could look at that pane and determine or at least help him with what that decoder might do. This would help until we can get the 3rd CV! We could also note there to program a number into CV105 or 106 (if those are available for the given decoder) to further define the decoder he's using. Those 2 CV's then would further identify the decoder only after it was programmed the first time. Is this a difficult task? I am finding out creating these "text only" programming items are not easy<VBG>. Comments? Jon Miller AT&SF For me time has stopped in 1941 Digitrax DCC owner, Chief system NMRA Life member #2623 Member SFRH&MS

A friend would like to use DecoderPro on his Macintosh laptop running MacOS 9.1 to program decoders on his Digitrax system. I use Linux and EasyDCC so am not able to be very helpful. Anything he should be concerned about? Secondly, the web page for DecoderPro lists something called 'LocoBuffer' as a bit of hardware that a Macintosh user with a Digitrax system needs. I looked on the Digitrax site and didn't see such a device. Would someone point me in the right direction? Thanks, Mike

Can anyone tell me please if DecoderPro works under XP Pro? It seems to load and run well but I have been unable to get it to talk to the interface. I get Program error: talking to command station. I have tried all combinations of speed and flow control both for the Com port and inside the LI100F. Is there something simple I am missing or is it just XP? Thanks Alex

bob,I was interested to see that I was not the only one having problems downloading the other programs used with the decoder pro.we(my friend and I) have installed decoder pro and find i very easy to run and itworks good on the system (NCE) that we have.But now that all the power units had been identified we are lost as to the next step of running them.Any help you can give would be great.Thank pete smith(trainman2543@... --- Bob Jacobsen <Bob_Jacobsen@...> wrote: > At 2:59 PM +0000 7/22/02, sotars wrote: > >Further to my last post, I have been trying to > download the other > >tools but have been unable to find out how to!!!!!! > > __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com

Can anyone please tell me if DecoderPro works with XP Pro? I took delivery of the LI100F on saturday and have it connected to a Set02. The software loads and appears to work correctly however I have been unable to get it to talk to the interface. The message (Programme error: timeout talking to the command station) appears, I have changed the baud rate for com1 and in the LI100F also the flow control in all its combinations but it is still timing out. Is there something simple I am missing or do I have to partition my drive and install 98SE/Me (YUK!!!!!!) Grateful for any help Alex Thomson

Based on predefined first and last speed steps, which are picked through trial and error, the spreadsheet calcuates CV values for the 26 remaininig speed steps. These values are based on a logrithmic curve that, when set-up in the speed table, result in a gradual increase in speed from low to high end. To obtain a copy of the file, see Files section on Yahoo's Digitrax NG - http://groups.yahoo.com/group/digitrax/files/PR1/ Bob