LokPilot Fx Nano with 8 pin socket - question before doing something stupid

[RBrodzinsky]

I just received a few of the subject decoders to use for the cab car lighting controls in my CalTrains (see my sound install threads for MP36PH and F40PH).  But, the decoders come wired to a standard NEM652 8 plug pin (which, of course, gets cut off during install).  However, I do like to use the plugs during pre-install initial programming with the LokTester.

According to the files I can find, instead of motor connections, the Orange wire from the FX is for Aux3 and the grey is for Aux4.  However, these are wired into the 8-pin plug, which on the LokTester, would connect to the motor.   Is there any problem with having these outputs attached to the motor, or should I just disconnect them from the plug, prior to the programming (safer path, anyway, but thought I would ask)?

Are there any tricks required for ESU function only programming, since no motor pulse feedback? I plan to do all the programming on these with a LokProgrammer.

[peteski]

Good questions.

If you observe standard decoders during programming you will notice that the headlights flash along with the motor "twitching" (to maximize the current draw)

I have never dealt with LokPilot Fx decoders or LokTester but I suspect that the decoder either has a built-in load resistor for providing the programming feedback on the decoder, or it depends on large enough load to be placed on the function outputs.

I didn't think that leaving the AUX3/4 attached to the "motor" of the LokTester will cause any damage (since AUX outputs can only create path to the decoder's ground (when activated) and motor circuit is supposed to be separate (isolated) from any other voltages in the decoder.

To get enough current for the acknowledgement pulses I think you could attach some load between the other AUX outputs and the common positive.  Something like 220 ohm resistors should do the trick. Those will create about 45mA load on each AUX output (which should be high enough for the programmer to to see the acknowledgement pulse).

[RBrodzinsky]

Thanks. I went ahead and hooked one up to the LokTester-LokProgrammer, after clipping the Aux 3/4 leads. The LokProgrammer had no trouble handling the NanoFx, including updating the decoder firmware. I did learn a few things, though: 1) there is no corresponding JMRI decoder definition, yet, for the LokPilot Nano and NanoFx decoders; 2) the function mapping logic used in the other ESU Lok decoders is not used in the Nano line (less flexibility, no indexed CVs); 3) the Aux 3 and Aux 4 lights on my LokTester have something wrong in the circuit traces, such that there is no continuity from the decoder function outputs to the LEDs.

On the final item, I have used this tester for a few years, but, being N scale, never had a decoder with active Aux 3/4 wires, so never tried anything with them. No big deal, but I always love how starting one "quick test" can lead to troubleshooting a whole different issue!

This is the smallest decoder I have ever seen!

[jdcolombo]

Hi Rick.

Keep us updated on the Nano Fx.  I can see potential for using these.

I'm sure Dave Heap is working on a definition for the Nano decoders for JMRI.  He seems quite dedicated!

John C.

[RBrodzinsky]

Thought this might make an interesting comparison photo. Shows the new Nano compared to the LokPilot Micro, the LokSound Micro and a Lenz Silver Mini. Don't have any loose Zimo decoders available, but they have been similar to the Micro

[ Guests cannot view attachments ]

[RBrodzinsky]

Oh, and the ESU website posted an updated manual for the Nano and NanoFx just this past Sunday.

[peteski]

That is small!
I wonder how it compares to CT Elektronik DCX76zD/F which is a full function decoder (it has motor outputs too).  Size: 0.27 x 0.24 x 0.07 Inch (6.9 x 6.1 x 1.7 mm).

[RBrodzinsky]

The Nano and NanoFx are 8.0mm x 7.0mm x 2.4mm, so the CT is smaller. The Nano has motor control, but only 4 function outputs vs no motor and 6 functions on the Fx. The Z guys are going to have some fun with these. Still too big for T -- LOL

[peteski]

The Nano and NanoFx are 8.0mm x 7.0mm x 2.4mm, so the CT is smaller. The Nano has motor control, but only 4 function outputs vs no motor and 6 functions on the Fx. The Z guys are going to have some fun with these. Still too big for T -- LOL

6-functions? Nice!  Amazing how far the the US companies (TCS. Digitrax) are behind the ball with their function-only decoders.  I didn't even mention the other US decoder manufacturers because they don't make anything that is small enough to even compare.  The more I look a the DCC decoder field, the better the European decoders look.

[Mark W]

Still too big for T -- LOL

Wait just a minute there Rick... 

[RBrodzinsky]

OMG!

[peteski]

Wait just a minute there Rick... 

Wow!  DCX65 is designed for 3-8V DCC?  This is the first time I've heard of such a thing as low-voltage DCC. Makes sense for T gauge.  That is so cool! DCX65 is 6 x 5 x 1,8 mm
If the LokPilot decoder is called Nano, this one should be called Pico!

[RBrodzinsky]

Just a quick addendum on my initial post -- the LokPilot NanoFX (and Nano) are supported in JMRI.  I was looking under the V4 definitions, but these decoders follow the LokPilot V1 CV mapping.

[nstars]

Wow!  DCX65 is designed for 3-8V DCC?  This is the first time I've heard of such a thing as low-voltage DCC. Makes sense for T gauge.  That is so cool! DCX65 is 6 x 5 x 1,8 mm
If the LokPilot decoder is called Nano, this one should be called Pico!

I have been following the DCX65 for some time (the announcement is already more than 2 month old) and I have tried to order the decoders from CT Elektronik, but unfortunately they are not yet available.

I think it is good to clarify that it concerns a decoder for 3-8V motors running on regular DCC (with 7-21 V on the track). This would make a lot of small motors available for use in what ever want on regular N scale layouts. It is also important to notice that the DCX65 is only a little bit smaller than the DCX77z (6x5x1.8 vs 7.5x5x1.. And there is of course the DCX77L with a size of 9.5x4x1.8.

Btw, we use a lot of CT Elektronik, Zimo and Esu decoders and in my opinion the real development of decoders is happening in Europe.

Marc

[peteski]

I have been following the DCX65 for some time (the announcement is already more than 2 month old) and I have tried to order the decoders from CT Elektronik, but unfortunately they are not yet available.

I think it is good to clarify that it concerns a decoder for 3-8V motors running on regular DCC (with 7-21 V on the track). This would make a lot of small motors available for use in what ever want on regular N scale layouts. It is also important to notice that the DCX65 is only a little bit smaller than the DCX77z (6x5x1.8 vs 7.5x5x1.. And there is of course the DCX77L with a size of 9.5x4x1.8.

Btw, we use a lot of CT Elektronik, Zimo and Esu decoders and in my opinion the real development of decoders is happening in Europe.

Marc

I know it is off-topic but the DCX65 can operate with DCC voltages up to 21V and it will provide reduced voltage to the motor?  That is a very important development for N (and smaller scale) DCC!