Locked
Re: COM Port not communicating
Bob,
Be aware that COM port assignments _can_ vary under some circumstances, so it is always good to check the JMRI System Console log to look for errors at the beginning of the log. You can always check Windows "Device Manager" to determine the USB device's actual COM assignment as an alternative.
While I have not made much use of my DCS240 in more than 8 months due to personal issues, I have found its integrated USB interface to be less than 100% reliable with JMRI.
The DCS240 has been known to "lock-up" its USB interface on occasion. When that has happened to me, I have had to shut-down JMRI, disconnected the USB cable, power-cycle the DCS240, reinstall the USB cable, and restart JMRI. I've primarily experienced this when programming decoders on the DCS240 service-mode programming track, but I think I've occasionally had problems with JMRI communication via the DCS240 interface as a LocoNet interface.
I have found that updating the DCS240 firmware helped with some programming track programming "lock-up" issues with JMRI.
I have found that a LocoBuffer-USB or a PR3 device or PR4 device, rather than using the DCS240 integrated USB connection, has given better reliability. So that is what I have used since finding the communication unreliability with the integrated DCS240 USB interface. Remember that this is all based on 8+ month old recollections, so they may be less-than-accurate memories.
Regards,
Billybob
|
Locked
Re: COM Port not communicating
Hi Robert
This is not uncommon. Remove all power from the dcs240. This command station is very parasitic so you have to remove the dc power, usb connections, track connections and loconet connections. You may as well reboot the computer at the same time. Have a break, plug everything back in and try again. The root cause is the usb connection ceasing to accept incoming data, generally after a track or rail sync short, but that might be a coincidence.
Steve G.
toggle quoted message
Show quoted text
On September 7, 2019 5:07:55 PM EDT, "Robert Perry via Groups.Io" <rjpod@...> wrote:
It is showing that communications are coming into JMRI via a Digitrax throttle. It seems that the communication is only one way as there is nothing indicating that I can send any query to the DCS240 to check configurations, change turnouts, etc. Do you know of any way to test if the computer is communicating back to the DCS240?
The panel does not show turnout positions, signal colors, block occupancy, etc.?
The preferences are showing:
Digitrax
DCS240 USB Interface
COM3
DCS240 (Advanced Command Station)
L
Loconet
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Locked
Re: Virtual Sound Decoder - Clicks on looped sound files
I am still finding my way around this. Would someone please point me to information on creatng vsd files from my sound files?
Thank you,
Steve Bartlett
|
Apologies for the rudeness of using a terrible user name - taken me a while to figure out where to set my profile - Mack!
Thanks for all the help so far. I have now found the sprog setting Ross was referring to. That had switched to 14 step (not a window I've opened at all previously, so I assume a corruption somewhere). The sounds for the one unchanged loco?are now working, but it wasn't moving at all. I then re-read the first page of the programming page and it's back to normal!
Thanks ever so much for all the advice. I will also now go and do full CV reads as suggested by Dave.
One question Dave - the factory reset option - I have a sound programmed (Legomanbiffo) decoder. I've only changed the address. The factory reset option you mentioned from the program window sounds like a full factory reset, not the same as the CV8=8 reset. Just wanted to check what that do to do the decoder if I used that in future?
Thanks again!
Mack
|
Would have been
helpfull to know it was Umelec and not Melec.
CV8 says it's a Umelec Ing. Buero, however the
sticker on the chip says MELEC TL2054.? So I have no idea what
to say other than they forgot to put the U on the sticker!
??? I will try it again on JMRI using the 2054
setting.
--
Jon Miller
For me time stopped in 1941
Digitrax Chief/Zephyr systems,
SPROG, JMRI User
NMRA Life member #2623
Member SFRH&MS
|
Locked
Re: COM Port not communicating
It is showing that communications are coming into JMRI via a Digitrax throttle. It seems that the communication is only one way as there is nothing indicating that I can send any query to the DCS240 to check configurations, change turnouts, etc. Do you know of any way to test if the computer is communicating back to the DCS240?
The panel does not show turnout positions, signal colors, block occupancy, etc.?
The preferences are showing:
Digitrax
DCS240 USB Interface
COM3
DCS240 (Advanced Command Station)
L
Loconet
|
Locked
Re: Steve Todd's image - Buster Update?
Steve,
? ? Shouldn't there be a way to update Buster from the terminal window?
Roger
|
Locked
COM Port not communicating
Hi to all:
Today I was setting up some signals through JMRI and lost communication to my DCS240.? It had been working fine.? Loconet Monitor shows that buttons on the throttle are hit but there is no communication back from JMRI to the Loconet (cannot control turnouts, signals, or configure/read any Loconet device.
I am using a Lenovo laptop YOGA 730 running Windows 10.? The only COM port available is COM3 which has the driver from Digitrax: mchpcdc.inf
I tried reinstalling a generic Windows COM driver and then reinstalled the Digitrax one but no effect.? I had a similar issue several months ago and installing the COM port driver worked.? Today there is no effect.
Any ideas?
Bob
|
On 9/6/2019 10:15 PM, Paul Bender
wrote:
If it is old enough, it may not support anything but the standard NMRA registers.
??? Right you are.? It's even reads 14 step
mode.? CV7=19 and CV8=147 (Umelec Ing. Buero)!? Are they even in
business anymore?
--
Jon Miller
For me time stopped in 1941
Digitrax Chief/Zephyr systems,
SPROG, JMRI User
NMRA Life member #2623
Member SFRH&MS
|
Locked
Re: Steve Todd's image - Buster Update?
On a RPI 3B+ all you need is a 8 gb SC card and you will use about half of its space.
If you want a bit more room in case you add some other stuff, then go up to 16gb.
I use 8 GB and jmri sails along.
Oh, and by the way - - -back it up! ?back it up! ?back it up!? Perhaps a couple?of SD cards?? Cards do go bad - it has happened.
I use win32 disk imager to do it with.? Super simple.
Bob S
On Sat, Sep 7, 2019 at 2:26 PM Don Weigt < dweigt47@...> wrote: I'm confused. I thought Buster was only for the Pi 4, but now find online that maybe it can be used on my 3B+ if I put a big enough memory chip on it.
What models of RPI, with what memory chips would this be good for? I'd like to get to JMRI 4.17.3 on my RPi 3B+. to match what I have on my Dell Windows 8.1 PC.
Don Weigt Connecticut, USA
|
Locked
Re: Steve Todd's image - Buster Update?
I'm confused. I thought Buster was only for the Pi 4, but now find online that maybe it can be used on my 3B+ if I put a big enough memory chip on it.
What models of RPI, with what memory chips would this be good for? I'd like to get to JMRI 4.17.3 on my RPi 3B+. to match what I have on my Dell Windows 8.1 PC.
Don Weigt Connecticut, USA
|
Locked
Re: VSD Sound from ZIMO's Sound Library
Klaus,
SUCCESS!!!? ?A working ZIMO NW2 engine.? Flawless notches at 12,24,36,48,60,72 & 80.? Great start and shutdown sounds.? My thanks to Oliver Zoffi for the very nice sounds.? Definitely going to drive the wife crazy.
Once I got past my confusion with multiple named config files it's been clear sailing.? I copied the engine script from the 710G3B-16T 90MAC vsd folder's config file and pasted it into the NW2 config file.? then I renamed all the 710 wav files to Zimo's NW2 ones.? I of course, added the new wave files to the NW2 sound/engine folder.? It ran first time!? I still have to add more functions such as radio chatter, rail clack, richtung-zisch (pop off??), etc.? ?I also have to check that the notch increments are correct for the 567 diesel.
This is enough for now,? bleary eyed from the computer and a happy headache from the pounding 567 diesel.
Thanks for all your help, Klaus.
Conrad
|
Locked
Re: VSD Sound from ZIMO's Sound Library
Conrad,
That sounds good.
Good luck with the transition sounds!
Klaus
Am 07.09.2019 um 18:14 schrieb conrad:
toggle quoted message
Show quoted text
Klaus,
I'm back at it and making progress.? Tried system console and got a large error list.?Took a fresh approach.? My mistake was that I had too many NW2 config files and? was apparently copying them into the incorrect vsd folder.? A mess.? a side by side comparison in my xml editor show the difference.? With a fresh start - good news.
So far, ZIMO's wav files don't have clicks.? I have a NW2 vsd folder with ZIMO's bell, horn and compressor.? The engine part is very simple - just start, stop and 3 run wav files.? No clicks when notching.? As I remember the original vsd folder had this simple 3 step system also.? So now my task is to incorporate the transition steps that are provided by ZIMO's wave files, i.e. 0-1, 1-2, 2-1 and 1-0.? If that works I'll try adding the all 8 steps that ZIMO has.
Conrad
PS? With the click problem, the volume problem and ZIMO files I will, for now, stay far away from system console msgs:)
|
i have currently 9 Digitrax DS64 per there recemidations I created ID# 101 - 109. I also named each switch address 1 thru 36. In Panel Pro where does it see the address for the DS64? It’s seeing the switch address’s. Am I missing something? In panel Pro I saw there is a programming button for the DS64’s but I don’t understand what that does.
Wayne Snyder
|
Locked
Re: VSD Sound from ZIMO's Sound Library
Klaus,
I'm back at it and making progress.? Tried system console and got a large error list.?Took a fresh approach.? My mistake was that I had too many NW2 config files and? was apparently copying them into the incorrect vsd folder.? A mess.? a side by side comparison in my xml editor show the difference.? With a fresh start - good news.
So far, ZIMO's wav files don't have clicks.? I have a NW2 vsd folder with ZIMO's bell, horn and compressor.? The engine part is very simple - just start, stop and 3 run wav files.? No clicks when notching.? As I remember the original vsd folder had this simple 3 step system also.? So now my task is to incorporate the transition steps that are provided by ZIMO's wave files, i.e. 0-1, 1-2, 2-1 and 1-0.? If that works I'll try adding the all 8 steps that ZIMO has.
Conrad
PS? With the click problem, the volume problem and ZIMO files I will, for now, stay far away from system console msgs:)??
|
Locked
Re: Steve Todd's image - Buster Update?
Thanks, G
There's a new version here:?
It includes the latest Buster updates and JMRI 4.17.3.
--SteveT
|
mcdougle1979,
A long shot:
Take a look at the Advanced pane (Read Full Sheet first) and make sure "Automatic Speed Step Detection" is enabled.
I don't think it will help greatly but worth a try.
Dave in Australia
|
mcdougle1979 (Name please – we are ‘friends’ and generally converse on a first-name basis?
?)
?
The Sprog FAQ has a link to “”?
-- unfortunately the link isn’t working at the moment.
< >
?
The SPROG user guide addresses speed step selection on pages 46 (Control Panel) and page 47:
“Choose the speed step mode to be used by the SPROG throttle. The default is 128 step, which is recommended for all recent DCC decoders.”
?
You may want to check this setting ensuring it is set correctly.
< >
?
HTH
?
Ross
?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of
mcdougle1979
Sent: Saturday, September 7, 2019 7:30 AM
To: [email protected]
Subject: Re: [jmriusers] LokSound v5 issues
?
Have you possibly set your DCC system to send 14 2peed-step commands to this locomotive address?
?
What DCC system (and what throttle) are you using?
I'm using JMRI with Sprog. Same effect if using Engine Driver or just on-screen throttle. I've not changed the speed steps, but I had this once before and had to program the decoder to 14 (as it was reading as 128) and then re-program it
to 128 and that worked fine. I've tried this using JMRI screens and using CVs directly and nothing improving.
|
Have you possibly set your DCC system to send 14 2peed-step commands to this locomotive address?
We are talking about the SPROG Console menu item and the SPROG throttle Speed Step Mode setting there. You need to check that and make sure it isn't at 14.
That governs both Engine Driver and JMRI screen throttles.
?
What DCC system (and what throttle) are you using?
I'm using JMRI with Sprog. Same effect if using Engine Driver or just on-screen throttle.
See above. I've not changed the speed steps, but I had this once before and had to program the decoder to 14 (as it was reading as 128) and then re-program it to 128 and that worked fine. I've tried this using JMRI screens and using CVs directly and nothing improving. Never set ESU decoder speed steps to anything other than 28/128 with your SPROG DCC system. In that mode it accepts either 28 or 128 speed step commands.
Never try to use it when set to 14.
<>?
Dave in Australia
|
Thanks for the advice on reading the full CVs. I tend not to bother. Not got my layout up and running yet and all running on rolling road seems to be OK.
Good way to mess up your decoders... But a decoder reset should fix that.
Also tried another loco which I've not recently changed and it also stops responding over speed step 14.
Looks like you're doing something wrong (unrelated to ESU).?
Dave in Australia
|
Roger Merritt
conrad