I've had for quite some time an Arduino Uno board and a motor shield sitting doing nothing I finally decided to give DCC++ a try. Well, it went flawless. Yesterday, I did the 1st test with an Atlas engine (N scale) equipped with a NCE decoder (purchased used for $50, but looks like new to me - never used) Right away, I could turn on and off the lights, depending on the selected direction (address is #3) However, the loco was not moving (forward or reverse) - I thought I had a problem somewhere and was ready to post in the forum But then I tried to increase the throttle up to 50%, and this is where the loco started to move So it works, but i find the speed to be quite slow, with not much happening before at least 35/40% Is this normal? Could it be the quality of the decoder? My power supply is a 12V /1.7A wall wart Is there a specific CV I should check? Thanks
No...................Just put the engine on the track, and tried with address 3, and I saw the lights working right away Haven't tried any programming. Should I? How do I do a factory reset?
Do you have another engine you know it works fine and see if it works OK on the DCC+++ command station?
Yes, I can try with another engine I can also try the Atlas engine that seems slow on my NCE PowerCab and compare
I've just tried this morning with another engine on the DCC++......Well, this one is even worst: nothing happens under 55% !!!! I will have to check the voltage on the tracks, and also make some tests with my NCE PowerCab.....!!! For you guys using DCC++ with the Arduino motor shield (NOT the Pololu)....at what throttle level your engines start to move?
I was not happy with my DCC++ setup (Arduino Mega + Motor Shield + 12v laptop supply) for the same reason. some locos wouldn't move until up to about 25 % throttle and some were just slow all around. I switched to a 15v supply and am much happier with it. I run JMRI on a Raspberry Pi connected to the Arduino via usb. I run the locos via either my phone or from my main computer via remote desktop to the Pi
