At 5:59 PM -0400 7/5/02, Al Silverstein wrote: Bob,
I just tried the update and it appears to be working OK in general. I did have one small problem. It did not recognize my decoder. The decoder is a DN146A and is installed in a Atlas U25B.
The software recognized the decoder as belonging to Digitrax but could not determine the type. It reported the version as 106.
Where is the problem? I've never seen a DN146A that has a version (CV7 value) of 106. The definition file is coded to look for DN146A (and other members of that family) as versions 33 through 45 inclusive, which is why it didn't find yours. I can add the 106 value to the search list for the DN146A. Do you have other DN146A decoders? If so, what are their CV7 values? (They easiest way to look is probably with the single CV programmer from the menu bar) In the larger picture, the problem lies with the NMRA specifications. They're not specific enough in what CV7 means, so some manufacturers don't provide enough information in that CV to make exact identification possible. A couple of people are working on doing something about that, but it will take a while. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957) Am working off a huge email backlog, call if it's urgent.
|
Bob,
I just tried the update and it appears to be working OK in general. I did have one small problem. It did not recognize my decoder. The decoder is a DN146A and is installed in a Atlas U25B.
The software recognized the decoder as belonging to Digitrax but could not determine the type. It reported the version as 106.
Where is the problem?
Al
toggle quoted message
Show quoted text
----- Original Message -----
From: Bob Jacobsen
To: jmriusers@...
Sent: Friday, July 05, 2002 4:19 AM
Subject: [jmriusers] A new test upload
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:
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.
To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
|
I just installed V0.9.3.5 and everything seemed to go fine. I didn't do
any programming or other testing but everything opened as it should. I will
reserve comment about the current version until I have time to do testing
and programming but initial feeling are that it looks great. My machine is
a 233 Intel running Win98 Ver2.
It did do an interesting thing and came up with a password input if
desired. Probably part of the installer. It's not a problem and I made it
go away<G>.
Jon Miller
AT&SF
For me time has stopped in 1941
Digitrax DCC owner, Chief system
NMRA Life member #2623
Member SFRH&MS
|
Locked
Re: Serial port too slow? Can anything work.
I've just spent a long day trying to get the RXTX implementation to work at 16457 baud. My apologies for the length of this; if you're not interested in hardcore details, please skip the rest of the email. But if there's any chance you can help, I'd appreciate it. If its pretty straight forward and you have a build directory then I can try it on one of our development Linux boxes at work. Maybe tar-gzip it up and email it to me and I'll have a go. If not then I should be able to work through the install/build instructions next week and see if I can get it to at least build. Then if you could email me the proposed changes I'll try and get a build to try.. Now for the bad news. Despite 15 hours of effort (c.f. ) I still can't get the original program to compile! RXTX is a Linux project, so their instructions involve cross-compiling with gcc. It's a mess of Java-generated headers, headers copied from Windows to Linux, etc, all munged together by a 7k-line configure script. I like the GIF, very appropriate Cheers Alex
|
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:
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.
|
At 4:10 PM +0000 6/30/02, broman40de wrote: 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. Would it be OK if I made a German homepage using your text? I think that would be cool! Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957) Am working off a huge email backlog, call if it's urgent.
|
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: Would it be OK if I put this on the web so we'd have a German version of the homepage? That would be cool! Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957) Am working off a huge email backlog, call if it's urgent.
|
Locked
Re: MS100 connections from the PC
Bob,
Is it possible that when Decoder Pro initializes for the software to read the slots in the command station and store that information. If this could be accomplished then the slot information would be available at anytime.
Just a thought. Yes, that's what the active Slot Manager does. But that's a lot of LocoNet traffic, and it can cause problems if you start the program while the layout is running. I have to teach it to be a little smarter about which slots are interesting, so that when it sees one being used, only then does it request the contents. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957) Am working off a huge email backlog, call if it's urgent.
|
Locked
Re: MS100 connections from the PC
At 12:26 PM +0000 7/4/02, dale_gloer wrote: My guess is that the installer is a 32 bit program. So, I am trying
to figure out how to get W2K to give me a 32bit VDM to run the
installer in. Will update you if I find a solution. The installer _is_ a 32 bit program. I don't know much about Windows, so left most of the installer-builder settings as they were. It's got an option called "Generate a 32-bit setup" which is checked by default. The help text is "If checked, a 32 bit setup .exe will be generated. This file will only run on Windows 9.x, Windows NT or Windows 2000." That makes me think that it should be working for you, but it's clearly not. How does Windows decide whether a .exe file is 32-bit or not? Could something have been mis-set in the .exe that confuses it, either at my end or in transmission? Sourceforge has the file listed as "32-bit Windows", so should have used that Mime-type when downloading it. Is there another way to install this version?
Not today. As part of the deal for getting the piece of comm code I needed to talk at the MS100 baud rate on Windows, I had to agree to not allow separate downloading of the parts that make it up. That includes making a .zip file available for download. I can't push too hard, because he's already been quite flexible in letting us use his commercial product. He generously let me use the $50 "one-user" license instead of the $1500 "commercial distribution" license. Investing money for a component of something that's then freely available is interesting economics... I'm still hoping that we can get a non-commercial implementation of the comm code. But that's also a free-ware project, which means that it moves at its own rate. When it's done, I can make that available like the older versions of DecoderPro, where you copy some files into specific places. But it might be a couple weeks. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957) Am working off a huge email backlog, call if it's urgent.
|
Locked
Re: MS100 connections from the PC
My laptop is an IBM Thinkpad T20 with an Intel Pentium III processor running about 800mHz - don't know exactly. The error happens immediately that the Command Line window opens after selecting the installer. There is nothing displayed in the Command Line window. Another piece of information which I got from observing more carefully this morning. The error popup box has a title line that says: 16 Bit MS DOS Subsytem My guess is that the installer is a 32 bit program. So, I am trying to figure out how to get W2K to give me a 32bit VDM to run the installer in. Will update you if I find a solution. Is there another way to install this version? Dale. PS: I appreciate what you are doing with this program. It is the only thing that available that can give me what I want for decoder programming. Maybe I will just have to break down and buy a locobuffer. --- In jmriusers@y..., Bob Jacobsen <Bob_Jacobsen@l...> wrote: At 6:48 PM +0000 7/3/02, dale_gloer wrote:
I also have a laptop with W2K on it which doesn't work with the
prvious version of Decoder Pro. I downloaded the installer to it and when I try to start the installer I get a nasty message in a popup
box as follows:
The NTVDM CPU has encountered an illegal instruction,
CS:053c IP:02b7 OP:63 65 6e 74 65 Choose 'Close' to terminate the
application.
There is a Close and an Ignore button at the bottom of the box. That's not a good sign...
Does this happen _before_ the installer splash screen comes up?
And what type of laptop (e.g. what processor) is this?
I'll ask the Mindvision people if they've seen this before once I
get those details.
Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@l..., 510-486-7355, fax 510-495-2957)
Am working off a huge email backlog, call if it's urgent.
|
Locked
Re: MS100 connections from the PC
Bob,
Is it possible that when Decoder Pro initializes for the software to read the slots in the command station and store that information. If this could be accomplished then the slot information would be available at anytime.
Just a thought.
Al,
toggle quoted message
Show quoted text
----- Original Message -----
From: Bob Jacobsen
To: jmriusers@...
Sent: Wednesday, July 03, 2002 12:57 PM
Subject: Re: [jmriusers] MS100 connections from the PC
At 12:46 PM -0400 7/3/02, Al Silverstein wrote:
>Jon,
>
>I do not know how to express this very well so please try and follow
>my reasoning.
>
>Each time a locomotive speed message is sent from the throttle to
>the locomotive the packet includes the locomotives address.
>
>It is there for reasonable to assume that the locomotive address can
>be extracted from the packet by the Decoder Pro software and
>displayed in the LocoNet Debug window. I use long (extended)
>addressing. When I saw slot 1 in the LocoNet Debug window I was
>controlling a locomotive with address 8127.
>
>I hope that this answers your question.
Thanks, I think I understand.
The answer is "yes and no". The LocoNet message we're displaying
doesn't carry the locomotive address, just the slot number. But the
program does have a SlotManager, which in many cases knows the
locomotive number. It's a good idea to add that info to the monitor
display, I'll do that.
But it won't be 100% present without some work. In DecoderPro, the
slot monitor is passive; it just looks at the information it sees go
by on the LocoNet. The way it knows what's in a slot is to see the
contents go by in an acquire, dispatch or update operation. So the
monitor will only have the address available after it's been watching
for a little while. I'll have to see whether that's a real problem or
not; I'll do some tests later today.
The full JMRI library has an active slot monitor, which asks the
command station when it needs info. I'd left that out of DecoderPro
because it wasn't really needed, and because it causes some extra
LocoNet traffic. But I should look into whether it would be good to
add it.
Thanks for the suggestion!
Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
Am working off a huge email backlog, call if it's urgent.
Yahoo! Groups Sponsor
ADVERTISEMENT
To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
|
Locked
Re: MS100 connections from the PC
Hi Bob Just a note to say thanks for all the time you are spending Decoder-Pro Jerry Walker aka n1hat Sorry to have been so out of touch;------------ --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (). Version: 6.0.372 / Virus Database: 207 - Release Date: 6/20/2002
|
Locked
Re: MS100 connections from the PC
At 6:48 PM +0000 7/3/02, dale_gloer wrote: I also have a laptop with W2K on it which doesn't work with the
prvious version of Decoder Pro. I downloaded the installer to it and
when I try to start the installer I get a nasty message in a popup box
as follows:
The NTVDM CPU has encountered an illegal instruction,
CS:053c IP:02b7 OP:63 65 6e 74 65 Choose 'Close' to terminate the
application.
There is a Close and an Ignore button at the bottom of the box. That's not a good sign... Does this happen _before_ the installer splash screen comes up? And what type of laptop (e.g. what processor) is this? I'll ask the Mindvision people if they've seen this before once I get those details. Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957) Am working off a huge email backlog, call if it's urgent.
|
Locked
Re: MS100 connections from the PC
Bob, I downloaded the installer and it ran clean on my W95 machine. The new version appears to work OK. Unfortunately it is not near teh railroad and I have no loco net connection to it to try at the moment. I also have a laptop with W2K on it which doesn't work with the prvious version of Decoder Pro. I downloaded the installer to it and when I try to start the installer I get a nasty message in a popup box as follows: The NTVDM CPU has encountered an illegal instruction, CS:053c IP:02b7 OP:63 65 6e 74 65 Choose 'Close' to terminate the application. There is a Close and an Ignore button at the bottom of the box. Too bad because I really hoped that Decoder Pro wopuld run on this machine. Dale. --- In jmriusers@y..., Bob Jacobsen <Bob_Jacobsen@l...> wrote: 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:
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@l..., 510-486-7355, fax 510-495-2957)
Am working off a huge email backlog, call if it's urgent.
|
Locked
Re: MS100 connections from the PC
At 12:46 PM -0400 7/3/02, Al Silverstein wrote: Jon,
I do not know how to express this very well so please try and follow my reasoning.
Each time a locomotive speed message is sent from the throttle to the locomotive the packet includes the locomotives address.
It is there for reasonable to assume that the locomotive address can be extracted from the packet by the Decoder Pro software and displayed in the LocoNet Debug window. I use long (extended) addressing. When I saw slot 1 in the LocoNet Debug window I was controlling a locomotive with address 8127.
I hope that this answers your question. Thanks, I think I understand. The answer is "yes and no". The LocoNet message we're displaying doesn't carry the locomotive address, just the slot number. But the program does have a SlotManager, which in many cases knows the locomotive number. It's a good idea to add that info to the monitor display, I'll do that. But it won't be 100% present without some work. In DecoderPro, the slot monitor is passive; it just looks at the information it sees go by on the LocoNet. The way it knows what's in a slot is to see the contents go by in an acquire, dispatch or update operation. So the monitor will only have the address available after it's been watching for a little while. I'll have to see whether that's a real problem or not; I'll do some tests later today. The full JMRI library has an active slot monitor, which asks the command station when it needs info. I'd left that out of DecoderPro because it wasn't really needed, and because it causes some extra LocoNet traffic. But I should look into whether it would be good to add it. Thanks for the suggestion! Bob -- -------------- Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957) Am working off a huge email backlog, call if it's urgent.
|
Locked
Re: MS100 connections from the PC
Jon,
I do not know how to express this very well so please try and follow my reasoning.
Each time a locomotive speed message is sent from the throttle to the locomotive the packet includes the locomotives address.
It is there for reasonable to assume that the locomotive address can be extracted from the packet by the Decoder Pro software and displayed in the LocoNet Debug window. I use long (extended) addressing. When I saw slot 1 in the LocoNet Debug window I was controlling a locomotive with address 8127.
I hope that this answers your question.
Al
toggle quoted message
Show quoted text
----- Original Message -----
From: Jon Miller
To: jmriusers@...
Sent: Wednesday, July 03, 2002 12:21 PM
Subject: Re: [jmriusers] MS100 connections from the PC
>One quick suggestion. It would be nice to see the locomotive address in
the LocoNet Monitor screen<
Al,
Not sure this would be possible until we have a feedback scheme in
place, like the current Digitrax or what NMRA is looking at? Or do I
misunderstand this?
Jon Miller
AT&SF
For me time has stopped in 1941
Digitrax DCC owner, Chief system
NMRA Life member #2623
Member SFRH&MS
Yahoo! Groups Sponsor
To unsubscribe from this group, send an email to:
jmriusers-unsubscribe@...
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
|
Locked
Re: MS100 connections from the PC
One quick suggestion. It would be nice to see the locomotive address in the LocoNet Monitor screen< Al, Not sure this would be possible until we have a feedback scheme in place, like the current Digitrax or what NMRA is looking at? Or do I misunderstand this? Jon Miller AT&SF For me time has stopped in 1941 Digitrax DCC owner, Chief system NMRA Life member #2623 Member SFRH&MS
|
Locked
Re: MS100 connections from the PC
Bob,
I just tried the lastest version Decoder Pro (0.9.3.4) with Java package (1.4.0_01) real quickly on a Dell GX1, PIII 600 mhz, 256MB ram, Com1, and Windows 98SE.
This is a very quick test.
1) Installed then booted latest version of Decoder Pro
2) Set Layout Cnnection to LocoNet MS100
3) Set Serial Port to COM1.
4) Set Command Station to DSC100
5) Set GUI to Windows
6) Saved Preferences.
7) Restarted Decoder Pro.
8) Started Debug LocoNet Monitor.
9) Saw messages as I turned the knob of a throttle.
10) Messages indicated that slot 1 speed was changing. My engine with address 8127 changed speeds with the throttle.
The basic test indicates that Decoder Pro is communicating.
One quick suggestion. It would be nice to see the locomotive address in the LocoNet Monitor screen.
Al
toggle quoted message
Show quoted text
----- Original Message -----
From: Bob Jacobsen
To: jmriusers@...
Sent: Wednesday, July 03, 2002 11:20 AM
Subject: [jmriusers] MS100 connections from the PC
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:
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
|
Locked
MS100 connections from the PC
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:
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.
|
Dear bob,
with your install program I?ve installed the Decoder Pro
part of the J/MRI project. The JAVA version is 1.4.0_01.
Conected via(non selected)
On port (non selectet).
Begining the installation I?ve great problems to understand it
but in the morning it works.
It works on a Max-Data computer with WINDOWS 98. On the same
Computer works C/MRI Interface without 8255, with new input
and outputcards for Pentium. The 8255 works there not good.
I see you are also in the C/MRI group. Lets now begin to laborate
with DCC, I?ve never work before.
best regards
dieter
|
Bob Jacobsen