NCE USB Adapter

The NCE USB uses the SiLabs CP2102 chipset.

1) Download and install SiLabs CP210x drivers from

<https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers>

- There is a Universal driver for Windows 10.

- The downloaded file will be a ".zip"

2) 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.

3) 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

4) When you have it working properly, the COM port should appear/disappear as you plug/unplug the NCE USB.

Notes

- 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:

- Users have reported Windows 10 updates have messed up the SiLabs drivers the NCE USB needs. Reinstall them as per below.

- A Stuck-On Cab Bus LED on the NCE USB is due to a communications failure between the NCE USB and the Power Cab. Once the Cab Bus LED is on, the NCE USB is hung up and needs resetting by unplugging both cables and replugging them back in. AKA Reboot the USB board.

Power Cab JMRI Settings

The best beginner-level settings for a Power Cab (any version) and an NCE USB (any 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: (The COM port number you saw appearing/disappearing)

-- System: PowerCab

-- Additional Connection Settings checkbox ON

-- Baud rate: 9600.

The JMRI system console log should then report V6.3.0 or V7.3.0.

If you don't get a version number in the log or the system does not work, Use Help->System Console...->Copy to clipboard and paste into a post for us to see on NCE-DCC@ groups.io

USB Board notes:

-The only benefit of going to jumpers all-on and 19200 baud setting is that it allows you to change the Cab address of the NCE USB from 3 to 8,9 or 10 to free up address 3 for another throttle. But you've got to have Power Cab firmware V1.65B and you have to use the Configure USB command. That's why we've stopped recommending it for general use.

- You will not see any speed improvement because after it passes through the USB board at 19200 it hits the NCE cab bus's fixed 9600 baud rate. But even that is not the data rate bottle neck. The DCC commands protocol to the track run even slower.

- When reading the version of your NCE USB, only the first digit counts as the version number. The last three digits report how your jumpers 2-4 are set with jumper 1 being ignored on all systems.

LED Indications and Diagnosis.

1) USB Board: There are two LEDs (marked USB and CAB BUS). Normal behavior is both to flicker briefly when processing commands. IF either or both are stuck on, it denotes a problem and needs resetting by unplugging both cables and replugging them back in. AKA Reboot the USB board.

2) PCP Panel: Normally the LED is on. It will turn off when there ia a short. It will briefly flicker when JMRI switches it into or out of programming mode.