¿ªÔÆÌåÓý

  1. Jmriusers
  2. Messages
Expanded Topics Messages Polls
Date
Locked Re: TCS WOW consist functions #tcs

 

Thanks Michael.? Greatly appreciated!

Jim Little, MMR

On Tue, Dec 17, 2019 at 5:51 AM Michael Mosher <mjmx1@...> wrote:
Fixed, should be in next test version.

Michael Mosher
Member SFRH&MS? ? ? ? ? ? ?
DCC Master PVSMR? ? ? ? ? ?

On 12/13/2019 1:55 PM, James Little wrote:
> Just downloaded and installed JMRI 4.17.7.? Last night on 4.17.6 I
> found a problem with the Consist pane of TCS WOW steam decoder page.?
> Today I tried it on 4.17.7 on both Steam and Diesel Consist panes.?
> When selecting which functions are Loco only or Consist enabled for
> functions F0(f) , F0(r), and F9 thru F12? (i.e. CV 22) they are either
> ALL Loco ONLY or ALL Consist.? CHecking the CV pane after a write
> shows a value of 252 in CV22.? Max value I calculate could be 33 by my
> calculation.
>
> Jim Little, MMR
>
Locked Re: Verify Initial Setup

[email protected]
 



This is the link to the XP drivers.

Marc
Locked Re: Signal mast logic #signalmasts

 

(I¡¯m assuming that the signals are visible to trains moving from right to left)

With B1 occupied, B2 unoccupied, and nothing else relevant happening, I¡¯d expect sm2 to be red and sm3 to be yellow.

sm3 should be protecting B2 _and_ sm2: it¡¯s appearance depends on both of them.

Is there any chance that you configured sm3 to protect both B1 and B2?

Bob

On Dec 17, 2019, at 8:21 AM, James Anderson <james_anderson_999@...> wrote:

Hi, not sure if I have a problem or just a complete lack of understanding of signal masts.

I have a very simple panel with 3 signal masts and two blocks

Sm1 sm2 sm3
#-------------------------------------#--------------------------------------#
B1 B2

The signal mast logic for SM2 is be green if B1 is unoccupied.
The signal mast logic for SM3 is be green if B2 is unoccupied.

If B1 is occupied and B2 is unoccupied SM2 and SM3 both go red. Is this correct (I was hoping that only SM2 would be red and SM3 would remain green).

Thanks
--
Bob Jacobsen
rgj1927@...
Locked Re: Signal mast logic #signalmasts

 

¿ªÔÆÌåÓý

Jim,

?

You have a single track so you have to protect against the train in B1 moving into B2.? To do what you want I think you¡¯d have to add directional logic.? Others may know better.

?

Robin

?

Robin Becker

San Diego, CA

?

?

From: [email protected] <[email protected]> On Behalf Of James Anderson
Sent: Tuesday, December 17, 2019 8:21 AM
To: [email protected]
Subject: [jmriusers] Signal mast logic

?

Hi, not sure if I have a problem or just a complete lack of understanding of signal masts.

?

I have a very simple panel with 3 signal masts and two blocks

?

Sm1?????????????????????????????????????? sm2???????????????????????????????????????? sm3

? #-------------------------------------#--------------------------------------#

???????????????????? ?B1???????????????????????????????????????? B2

?

The signal mast logic for SM2 is be green if B1 is unoccupied.

The signal mast logic for SM3 is be green if B2 is unoccupied.

?

If B1 is occupied and B2 is unoccupied? SM2 and SM3 both go red. Is this correct (I was hoping that only SM2 would be red and SM3 would remain green).

?

Thanks

?

Jim
Locked Re: Verify Initial Setup

 

¿ªÔÆÌåÓý

Hi Dave,

Just want to verify that these are the correct drivers, as I am using Windows XP, not Win 10.


Peace,

Mike G.


On 12/16/2019 7:12 PM, Dave Heap wrote:

Mike,

On 17 Dec 2019, at 11:06 AM, emrldsky <azMikeG@...> wrote:

O.K. The the correct connections are:

Power cab plugged into the adapter panel in its usual socket and the USP adapter plugged into the socket right next to where the power cab is plugged in on the same adapter plate. Am I correct?


Good. I can now give you the correct instructions.

NCE USB Setup Windows

- The NCE USB uses the SiLabs CP2102 chipset. Download and install SiLabs CP210x drivers from?
<>
- There is a Universal ?driver for Windows 10.
- The downloaded file will be a ".zip"
- You open that file and then open the file called:
"CP210xVCPInstaller_x86.exe" or "CP210xVCPInstaller_x64.exe" depending on whether your Windows is 32 bit or 64 bit.
- After doing this you should get the SiLabs device appearing as a new COM port in Windows Device Manager when you plug it in.
- Sometimes you may need to install the driver again after plugging in the NCE USB to get rid of the error symbol in Windows Device Manager.
- If you still have questions marks, try removing driver in Device Manager and try again as above
- When you have it working properly, the COM port should appear/disappear as you plug/unplug the NCE USB.
- Do not try to set the baud rate in Windows Device Manager.
- Ignore all other documentation to the contrary (there is some incorrect information in places) and set up as below:
- It also explains how to read the version of your NCE USB (only the first digit counts, the last three report how your jumpers 2-4 are set and jumper 1 is ignored on all systems).

NCE USB JMRI Settings

Configuration Instructions
===================

Here are the best settings for JMRI and jumpers for Power Cab (and also SB5).

Make sure you always unplug/replug both cables on the NCE USB after changing jumpers.?

It also explains how to read the version of your NCE USB (only the first digit counts, the last three report how your jumpers 2-4 are set and jumper 1 is ignored on all systems).


Power Cab Instructions
=================
The correct settings for a Power Cab V1.65 or V1.28 (as shown when the Power Cab starts up) and an NCE USB V6 (or you are not sure of the USB version) ?are:
- All USB Jumpers off (or at least 2, 3 & 4. Jumper 1 is ignored).
- JMRI preferences are:
-- System manufacturer: NCE
-- System connection: ?NCE USB
-- Serial port: <whatever is appropriate for your system>
-- USB version: V6.x.x
-- System: PowerCab
-- Additional Connection Settings checkbox ON
--- Baud rate: 9600.

The JMRI console log should then report V6.3.0. If it reports V7.3.0 and your Power Cab is V1.65, use the settings below instead.
If you don't get a version number or the system does not work, Use Help->System Console...->Copy to clipboard and paste into a post for us to see.

The correct settings for a Power Cab V1.65 or V1.65b and an NCE USB V7 ?are:
- All USB Jumpers on (or at least 2, 3 & 4. Jumper 1 is ignored).
- JMRI preferences are:
-- System manufacturer: NCE
-- System connection: ?NCE USB
-- Serial port: <whatever is appropriate for your system>
-- USB version: V7.x.x
-- System: PowerCab
-- Additional Connection Settings checkbox ON
--- Baud rate: 19200.

The JMRI console log should then report V7.3.7.

SB5 Instructions
============
The correct settings for an SB5 and an NCE USB V7 ?are:
- USB Jumper 4 on. All others off (or at least 2 & 3. Jumper 1 is ignored).
- JMRI preferences are:
-- System manufacturer: NCE
-- System connection: ?NCE USB
-- Serial port: <whatever is appropriate for your system>
-- USB version: V7.x.x
-- System: SB5
-- Additional Connection Settings checkbox ON
--- Baud rate: 19200.

The JMRI console log should then report V7.3.1.

General Troubleshooting
==================

If the system does not work after this:
- If your SB5/Power Cab is V1.65 rather than V1.65B, you may have been affected by a firmware issue (triggered by a System Reset).
- Your NCE USB may be set to a bad cab address (V7 only).
- There is a potential hardware issue with the NCE USB/Power Cab combination.
In either case, go through the following :
- Quit JMRI.
- Ensure neither LED on the NCE USB is stuck ON. If so, power cycle the USB by unplugging it from the cab bus cable.
- Ensure you have no other throttles connected.
- Restart JMRI and immediately go to Configure USB Interface under the NCE menu.
- Set the Cab ID to 3.
- Attempt a JMRI operation (use a throttle, Identify a decoder).
- The status line should stay green and it should work?
-If this does not work, do not fiddle with any other settings but instead:
-- Observe whether the Cab Bus LED on the NCE USB is stuck on and report back.
-- Use Help->System Console...->Copy to clipboard and paste into a post for us to see.

Dave in Australia
Locked Re: Decoder Pro not seeing Power Cab #nce #powercab

 

Hi Andrew,

It seems you passed the first hurdle - communication between command station and computer is now apparently there. The second hurdle may be a very small one: if you are trying to read a decoder while NOT in program track mode, then it is bound to fail. You can only read on the program track. And then only reliably if only one loco/decoder is there at any one time. I hope that's the simple solution you need. If not, we into the more murky problems of wiring, track cleaning, wheel cleaning at all that sort of thing.

Wouter


On Tue, 17 Dec 2019 at 16:35, andrew.woolman <apwool@...> wrote:
Have tried jumpers 2-4 both ways (all on-all off), and when I go to add a locomotive and read from, i get the error 301-no locomotive detected.
Stuck.?

Locked Re: Decoder Pro not seeing Power Cab #nce #powercab

 

Have tried jumpers 2-4 both ways (all on-all off), and when I go to add a locomotive and read from, i get the error 301-no locomotive detected.
Stuck.?
Locked Signal mast logic #signalmasts

 

Hi, not sure if I have a problem or just a complete lack of understanding of signal masts.

?

I have a very simple panel with 3 signal masts and two blocks

?

Sm1????? ???????????????? ? ? ? ? ? ? ? ??sm2? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?sm3

? #-------------------------------------#--------------------------------------#

????????????????????? B1???????????????????????????????????????? B2

?

The signal mast logic for SM2 is be green if B1 is unoccupied.

The signal mast logic for SM3 is be green if B2 is unoccupied.

?

If B1 is occupied and B2 is unoccupied ?SM2 and SM3 both go red. Is this correct (I was hoping that only SM2 would be red and SM3 would remain green).

?

Thanks

?

Jim
Locked Re: Decoder Pro not seeing Power Cab #nce #powercab

 

Did now find a cable and/or driver that seems to be working, though still having troubles (red light coming on, etc). ?Can someone Mac¡¯y please confirm the jumper positions? I¡¯ve gotten two different answers from NCE. ?With that info in hand Inwill try rostering a different loco and report what happens. ?Thank you!
Locked Decoder Pro not seeing Power Cab #nce #powercab

 

Total newbie, am having lots of trouble getting JMRI to work with my NCE PowerCab/USB Interface. ?I am hoping that if I give you all my specs, someone will be able, from experience to pinpoint the problem. ?Basically, the driver doesn't seem to be working: When I go into DecoderPro connection preferences, I see only "unspecified" and a Bluetooth Driver. ?No Silab USB. ?Not sure if the nobleman is hardware or software related, so here's my list of bits and pieces.

MacBook Pro running OSX.14.16
PowerCab running v1.65
NCE USB Interface v7.x.x (currently with all jumpers off, but have tried all on as well)
? SilabsUSBDriver.kext installed
??SilabsUSBDriver64.kext installed
Ativa USB2.0 A/B cable and a USB B/C adapter at computer
DecoderPro JMRI v4.16+R6f9aced

When I first fired it all up, it seemed that I could communicate with a loco on the track, but not well. ?There were issues with the loco # reverting to some five digit #, and also the program did not read the decoder mfr. correctly. ?I have since fiddled with the connection settings and now the program will not connect at all. ?As I mentioned before, the USB driver is not showing up at all, but neither is much else at this point.

Hoping its a simple routine to run down the likely problem(s). ?Many thanks in advance for your help!
PS: I tried reading old threads related to this topic, but many seem to wander into the weeds a little too deep for me to follow; I am not a programmer. ?If there is a simple fix already documented here, please do point me to it. ?Thanks!
Andrew Woolman

?
Locked Re: TCS WOW consist functions #tcs

 

Fixed, should be in next test version.

Michael Mosher
Member SFRH&MS
DCC Master PVSMR

On 12/13/2019 1:55 PM, James Little wrote:
Just downloaded and installed JMRI 4.17.7.? Last night on 4.17.6 I found a problem with the Consist pane of TCS WOW steam decoder page.? Today I tried it on 4.17.7 on both Steam and Diesel Consist panes.? When selecting which functions are Loco only or Consist enabled for functions F0(f) , F0(r), and F9 thru F12? (i.e. CV 22) they are either ALL Loco ONLY or ALL Consist.? CHecking the CV pane after a write shows a value of 252 in CV22.? Max value I calculate could be 33 by my calculation.

Jim Little, MMR
Locked Re: Verify Initial Setup

 

Dave,

What changed about 410 seconds after you started JMRI that allowed JMRI to
see the command station? It does 10 second cycles to try to talk to the
command station. It times out at 10 seconds. After all that, it finally
worked. So something changed.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org
Locked Re: Verify Initial Setup

 

Marc,


On 17 Dec 2019, at 3:27 PM, forfoum@... wrote:

Dave,

Does this not mean the driver is ok and loaded : Last 5 lines of his log

458429 jmrix.AbstractMRTrafficController WARN - timeout flushes receive buffer: [Receive]
458440 nce.NceConnectionStatus INFO - NCE EPROM revision = 7.3.0 [AWT-EventQueue-0]
Good spotting. I probably didn't scroll to the end of the log after seeing so many timeouts.

However, the fact that it took so long to reasons is concerning. It should have responded immediately.

Possible causes:
- Driver issues.
- He's using JMRI V3.4, which was using the old RXTX libraries rather than PureJavaComm.
- Bad 12V Power connection between the NCE USB and the Power Cab Panel (via Cab Bus wires 2 & 5). The 12V is needed for the microprocessor, which responds to the AA commands. (The opto-isolated USB part is powered by 5V from the computer and is obviously talking to some extent.)


675301 jmrix.AbstractMRTrafficController WARN - Timeout on reply to message: A1 00 08 consecutive timeouts = 0 [Transmit]
677374 jmrix.AbstractMRTrafficController WARN - timeout flushes receive buffer: 30 [Receive]
712425 jmrit.AbstractIdentify WARN - Stopping due to error: Timeout talking to command station (306) [AWT-EventQueue-0]
Things have gone bad when attempting to read CV8. Possible causes:
- Dodgy 12 Power connection (as above).
- Bad data connection between the NCE USB and the Power Cab (via Cab Bus wires 3 & 4).
- Other more obscure issues that have various troubleshooting paths (one of which is observing the two LEDs on the NCE USB and reporting exactly what happens when - normal operation is both flickering briefly as data is sent/received. Some more details in my previous email.

Dave in Australia
Locked Re: Layout editor

 

If you want to be able to gang switch to the opposite states also¡­ then yes.
Locked Re: Verify Initial Setup

[email protected]
 

Dave,

Does this not mean the driver is ok and loaded :? Last 5 lines of his log

458429 jmrix.AbstractMRTrafficController???? WARN? - timeout flushes receive buffer:? [Receive]
458440 nce.NceConnectionStatus?????????????? INFO? - NCE EPROM revision = 7.3.0 [AWT-EventQueue-0]
675301 jmrix.AbstractMRTrafficController???? WARN? - Timeout on reply to message: A1 00 08 consecutive timeouts = 0 [Transmit]
677374 jmrix.AbstractMRTrafficController???? WARN? - timeout flushes receive buffer: 30 [Receive]
712425 jmrit.AbstractIdentify??????????????? WARN? - Stopping due to error: Timeout talking to command station (306) [AWT-EventQueue-0]

Marc
Locked Re: Trouble loading PanelPro panels

 

Yeah...
I figured I needed to retrieve as much debug information as possible. It is a bit bothersome gathering that sort of data as we run trains for the public.? I will be on site Thursday and will gather as much data as possible.? Let me add to the list of glitches that we have seen.? They do not seem to be fatal because we can get everything up and running and it runs quite nicely.? I fear what we are seeing is left over schmutz for the way the panels were developed (kind of like microwave radiation left over from the big bang?)..? Let me repeat and add to what we are seeing:
1. When we load panels? as part of the configuration booting we never get to the console screen.? We have to kill java, remove the panel load from the config, start JMRI and load the panels from the Panel menu. Everything is then cool...
2. When we realized we had made errors in developing the panels and associated tool tables, we moved all data entry to the JMRI computer (Windows 10) running the layout.? The turnout tables and sensor tables were built using the OpenLCB menu selection Configure Nodes. We used the Make Turnouts and Make sensors tool in the LCC CDI..? The block tables were built using the add button associated with the Block Table tool.? The original panels were stripped of any connections that had been preconfigured.? The panels were graphics only.? The panels were reconnected to the various tool tables within JMRI on the computer running the layout.? When all that stew got simmered we noticed that there were turnouts and sensors added to their respective? tables.? If we deleted?? them when we restarted? PanelPro, they came back.? One frustrating aspect of how the various tables are built is the under the hood connections between objects is somewhat opaque.? The is noticeable when, for example, you delete a turnout...? You get a message something like "this object is used by the table manager and? 4 other objects".? How do you find out what those other objects are?? (I know those objects related to NCE because they have the "N" prefix).? My guess our clumsy development process has left some things hanging and JMRI is being polite and reconnects them.
3. One last oddity...? Our DCC command station is an NCE PH-PRO 5 amp system..? We know the command station is the latest and greatest.? It came back from the shop in October? and we run the part of the layout that is operational just fine.? We have not been able to get that command station to talk to our JMRI computer..The Serial set up is correct.? The cable is correct. When i fire up the system console I see stuffing going down the line to the NCE DCC command station but never get anything back..? I have not had the opportunity to check the set up with a PROCAB .? I called NCE tech support and all they would suggest is double check the serial parameters. Any ideas?? System console log to follow...

But in closing, let me say we are more than comfortable with the design decisions we made.? LCC is all that and a box of chocolate and DCC is a fine way to power an engine...?

Dan Kubarych
ARHS
Locked Re: Verify Initial Setup

 

¿ªÔÆÌåÓý

Mike,

On 17 Dec 2019, at 11:06 AM, emrldsky <azMikeG@...> wrote:

O.K. The the correct connections are:

Power cab plugged into the adapter panel in its usual socket and the USP adapter plugged into the socket right next to where the power cab is plugged in on the same adapter plate. Am I correct?


Good. I can now give you the correct instructions.

NCE USB Setup Windows

- The NCE USB uses the SiLabs CP2102 chipset. Download and install SiLabs CP210x drivers from?
<>
- There is a Universal ?driver for Windows 10.
- The downloaded file will be a ".zip"
- You open that file and then open the file called:
"CP210xVCPInstaller_x86.exe" or "CP210xVCPInstaller_x64.exe" depending on whether your Windows is 32 bit or 64 bit.
- After doing this you should get the SiLabs device appearing as a new COM port in Windows Device Manager when you plug it in.
- Sometimes you may need to install the driver again after plugging in the NCE USB to get rid of the error symbol in Windows Device Manager.
- If you still have questions marks, try removing driver in Device Manager and try again as above
- When you have it working properly, the COM port should appear/disappear as you plug/unplug the NCE USB.
- Do not try to set the baud rate in Windows Device Manager.
- Ignore all other documentation to the contrary (there is some incorrect information in places) and set up as below:
- It also explains how to read the version of your NCE USB (only the first digit counts, the last three report how your jumpers 2-4 are set and jumper 1 is ignored on all systems).

NCE USB JMRI Settings

Configuration Instructions
===================

Here are the best settings for JMRI and jumpers for Power Cab (and also SB5).

Make sure you always unplug/replug both cables on the NCE USB after changing jumpers.?

It also explains how to read the version of your NCE USB (only the first digit counts, the last three report how your jumpers 2-4 are set and jumper 1 is ignored on all systems).


Power Cab Instructions
=================
The correct settings for a Power Cab V1.65 or V1.28 (as shown when the Power Cab starts up) and an NCE USB V6 (or you are not sure of the USB version) ?are:
- All USB Jumpers off (or at least 2, 3 & 4. Jumper 1 is ignored).
- JMRI preferences are:
-- System manufacturer: NCE
-- System connection: ?NCE USB
-- Serial port: <whatever is appropriate for your system>
-- USB version: V6.x.x
-- System: PowerCab
-- Additional Connection Settings checkbox ON
--- Baud rate: 9600.

The JMRI console log should then report V6.3.0. If it reports V7.3.0 and your Power Cab is V1.65, use the settings below instead.
If you don't get a version number or the system does not work, Use Help->System Console...->Copy to clipboard and paste into a post for us to see.

The correct settings for a Power Cab V1.65 or V1.65b and an NCE USB V7 ?are:
- All USB Jumpers on (or at least 2, 3 & 4. Jumper 1 is ignored).
- JMRI preferences are:
-- System manufacturer: NCE
-- System connection: ?NCE USB
-- Serial port: <whatever is appropriate for your system>
-- USB version: V7.x.x
-- System: PowerCab
-- Additional Connection Settings checkbox ON
--- Baud rate: 19200.

The JMRI console log should then report V7.3.7.

SB5 Instructions
============
The correct settings for an SB5 and an NCE USB V7 ?are:
- USB Jumper 4 on. All others off (or at least 2 & 3. Jumper 1 is ignored).
- JMRI preferences are:
-- System manufacturer: NCE
-- System connection: ?NCE USB
-- Serial port: <whatever is appropriate for your system>
-- USB version: V7.x.x
-- System: SB5
-- Additional Connection Settings checkbox ON
--- Baud rate: 19200.

The JMRI console log should then report V7.3.1.

General Troubleshooting
==================

If the system does not work after this:
- If your SB5/Power Cab is V1.65 rather than V1.65B, you may have been affected by a firmware issue (triggered by a System Reset).
- Your NCE USB may be set to a bad cab address (V7 only).
- There is a potential hardware issue with the NCE USB/Power Cab combination.
In either case, go through the following :
- Quit JMRI.
- Ensure neither LED on the NCE USB is stuck ON. If so, power cycle the USB by unplugging it from the cab bus cable.
- Ensure you have no other throttles connected.
- Restart JMRI and immediately go to Configure USB Interface under the NCE menu.
- Set the Cab ID to 3.
- Attempt a JMRI operation (use a throttle, Identify a decoder).
- The status line should stay green and it should work?
-If this does not work, do not fiddle with any other settings but instead:
-- Observe whether the Cab Bus LED on the NCE USB is stuck on and report back.
-- Use Help->System Console...->Copy to clipboard and paste into a post for us to see.

Dave in Australia
Locked Re: Trouble loading PanelPro panels

 

Dan K,

One useful trick is to have the console open, it may show errors related to
loading the panel. Now depending on what is happening, you may be able to
click Help->System Console, do that in any window, it may show what is
happening during the panel load.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org
Locked Re: Verify Initial Setup

 

¿ªÔÆÌåÓý

Why don't I think of things like that!!

On 12/16/2019 5:15 PM, John wrote:

Go to the NCE site, there you can download the USB manual and get the info from
"the horse's mouth" so to speak.

John


---------- Original Message ----------
From: emrldsky <azMikeG@...>
Date: December 16, 2019 at 6:06 PM


O.K. The the correct connections are:

Power cab plugged into the adapter panel in its usual socket and the USP 
adapter plugged into the socket right next to where the power cab is 
plugged in on the same adapter plate. Am I correct?

The reference  
is not clear on that.


Peace,

Mike G.


On 12/16/2019 4:29 PM, John wrote:

Yes, that is what it was designed for.

John


---------- Original Message ----------
From: emrldsky <azMikeG@...>
Date: December 16, 2019 at 5:22 PM


Is the NCE USB board usable with the Power Cab?

What I do not understand it that a couple of years ago, I was reading
the parameters from the decoder and modifying speed steps using this
adapter. What it was plugged into, I am not sure now if you say I can't
do that.


Anyway, I will pursue other adapters.


Peace,

Mike G.


On 12/16/2019 3:35 PM, Dave Heap wrote:

Mike,


On 17 Dec 2019, at 4:49 AM, emrldsky <azMikeG@...> wrote:

The OS is Windows XP, and the usb is the NCE adapter. This all worked a
couple of years ago. Maybe dust overload?  :-)

If you are using the NCE USB board with your NCE Power Pro (plugged into
the
cab bus), you'll never be able to program locos.

You need a third-party USB-Serial cable (such as the one ESU sells as a
spare for its LokProgrammer hardware, or the similar FDTI-chipset based
one
from RRCirKits), plugged into the 9-pin serial port on the metal Power Pro
box.

No point further logs or speculation until that's resolved.

Dave in Australia

Locked Re: Verify Initial Setup

 

Go to the NCE site, there you can download the USB manual and get the info from
"the horse's mouth" so to speak.

John

---------- Original Message ----------
From: emrldsky <azMikeG@...>
Date: December 16, 2019 at 6:06 PM


O.K. The the correct connections are:

Power cab plugged into the adapter panel in its usual socket and the USP
adapter plugged into the socket right next to where the power cab is
plugged in on the same adapter plate. Am I correct?

The reference
is not clear on that.


Peace,

Mike G.


On 12/16/2019 4:29 PM, John wrote:
Yes, that is what it was designed for.

John

---------- Original Message ----------
From: emrldsky <azMikeG@...>
Date: December 16, 2019 at 5:22 PM


Is the NCE USB board usable with the Power Cab?

What I do not understand it that a couple of years ago, I was reading
the parameters from the decoder and modifying speed steps using this
adapter. What it was plugged into, I am not sure now if you say I can't
do that.


Anyway, I will pursue other adapters.


Peace,

Mike G.


On 12/16/2019 3:35 PM, Dave Heap wrote:
Mike,

On 17 Dec 2019, at 4:49 AM, emrldsky <azMikeG@...> wrote:

The OS is Windows XP, and the usb is the NCE adapter. This all worked a
couple of years ago. Maybe dust overload? :-)
If you are using the NCE USB board with your NCE Power Pro (plugged into
the
cab bus), you'll never be able to program locos.

You need a third-party USB-Serial cable (such as the one ESU sells as a
spare for its LokProgrammer hardware, or the similar FDTI-chipset based
one
from RRCirKits), plugged into the 9-pin serial port on the metal Power Pro
box.

No point further logs or speculation until that's resolved.

Dave in Australia
73321 - 73340 of 239659