From: [email protected] <[email protected]> On Behalf Of Inobu One via Groups.Io
Sent: Friday, 3 January 2020 7:57 AM
To: [email protected]
Subject: Re: [jmriusers] NCE USB Issue with RPi4 #nce #rpi Power Cab

?

Roy, This is for you.

Now only Step 3 and Step 9 is being challenged by Dave.... I will explain what is happening......

??? Set up the RPi4
??? The jumpers on the NCE USB interface must be on 2, 3 and 4 or 3 and 4 this supports the Power Cab and its two sub types. 7.3.3 or 7.3.7 and 19200 baud.??
??? Connect the USB port on the RPi4 to the NCE USB interface with a USB AB cable. (Leave the Power Cab unconnected)?
??? Start JMRI Panel Pro. (It will try to configure itself and you will have to change some settings.)
??? Go into Preference:Default and make sure that all the the radio buttons are set got NCE.
??? Go into connections and set the baud rate to 19200 (click the advance check box)
??? Make sure the the ttyUSB0 is selected along with the Power Cab option.
??? save and restart. (make sure that it open NCE, sometimes it defaults to Digitrax)
??? When the Panel Pro windows comes up within a second or two connect the Power Cab to the NCE USB interface (coiled wire.)
??? The ttyUSB0 connection will flash red but go back to black.
??? Open NCE:Show Cab and refresh. You will see it connect to the NCE interface first. The it will find the Power Cab.


Step 3 states

Connect the USB port on the RPi4 to the NCE USB interface with a USB AB cable. (Leave the Power Cab unconnected)

When you make this connection the USB port to the Raspberry Pi 4's allows its processor to create TTYUSB0 .......This allows Panel Pro to access it on it's boot up.? The Raspberry Pi
is not as efficient in handling USB port configuration as Windows. This step just insures that ttyUSB0 becomes a selection in Panel Pro connection window.

Leaving the Power Cab coil unconnected to the NCE USB Interface prevents it from energizing and initiating its boot cycle. This seems to be a problem as the Power Cab will be isolated because
the NCE Interface LED's have gone RED.


Step 9

When the Panel Pro windows comes up within a second or two connect the Power Cab to the NCE USB interface (coiled wire.) Moot argument coil is a RJ connection

When you make this connect it applies power to the micro processor side of the NCE USB interface (Module side). This triggers the initialization
between the Power Cab and NCE USB Interface. They establish their connection. When you make this connection in time Panel Pro sends out the AA
and the Power Cab can send the response. This transaction can be seen with the RED text Blink. If you do not time this connection right the NCE USB Interface will
initiate the RED LED and you will have to start over.

Some may see me as argumentative and that's true. My arguments are based on experience and facts that I have seen myself. In this case I had a vested interest as I needed to use
the RPi4 for an up coming build.? I mocked up the RPi4 test case and did everything like Roy would have done and it failed. I verified that there was a problem as I recreated it consistently.
I posted my findings and you can see for yourself what happen and where we are now.

I fight and argue so people can just run their trains with minimal frustration.
Inobu