I don't know if Gregg has had time to update the code for Polulo and Mega but if not read the post below post:
Got a very rough version of my DCC++ client working with Base Controller... all is working well -- very happy with Ardunio Mega AVR + Ardunio Motor Shield base controller. LCP_working by tz3p9v posted Jan 16, 2016 at 12:28 AM
Hello, I am using the same Pololu motor shield and I had to remap a pin to make it work with the Uno...what I did was I did not use the middle blue wire socket on the pololu motor shield I instead soldered wires directly to the shield....also make sure the traces are completely cut...of course I am using an UNO and not a MEGA Sidenote: I have not used the Programming track as I have one already that I use with my Digitrax system....however I have both red and green lights that are bot enabled on each motor terminals so I do know my assembly is correct.
I forgot about this - I had the same problem. I had to change SIGNAL_ENABLE_PIN_PROG to 10 as noted in post #338 that w8one referred to. First, check to make sure you have fully cut the trace for pin 12 on the underside of the Pololu board - check it with a multimeter. If that tests out OK, install a two-pin header and shunt to reconnect the pin 12 trace (I noted it in my photo on post 655) and install the Pololu demo program. That will exercise both outputs and their LEDs. You can check the outputs with a multimeter. (Note - you will need to remove your jumper wires to run this test.)
Yes.. written in C# ... by a long time VB6/VB.net developer. Needed to convert for work, but some loyalties dead hard Once I get the client running will post source -- but that will be a while as I want to support serial and Ethernet for DCC++Base Controller and CMRInet for layout status and control. LCC is just too raw, and complex for initial need. Paul.
Yes, I check the pin 12 with a multimeter. I change SIGNAL_ENABLE_PIN_PROG to 10. I test the Polulo Motor Shield with Polulo demo program. On serial monitor I got the message: Dual MC33926 Motor Shield fault And nothing more.
Yes C# ... also developing a DCC++ simulator so I can test software without actually talking to Base Controller.
I too am a long time VB/VB.net guy. C# made my head hurt. I'm a C guy on PIC microprocessors and that's enough!
That is what I saw when I first tried the demo and hadn't installed the shunt to reconnect the pin 12 trace, yet. I took another look at your photo - your Main output LEDs are lit and that is the side that wouldn't work for me until I changed SERIAL_ENABLE_PIN_PROG to 10. You probably could continue with getting a train working on the Main but you won't have a Programming Track output until you fix/replace the Pololu. (Looks like you will have to contact Pololu tech support and work with them to troubleshoot before they will consider replacing the board.)
Yes, I will send one email to Polulo support. For me will be very difficult to explain the problem with DCC++ project. But I will try.
Before you do that, check for a short across the Programming Track output connector (the side that doesn't light up). If that output has been shorted, the board will shut down that output and signal a fault. You will have to power-cycle the Pololu board or remove/replace the 'board enable' shunt to clear the fault and try again. This is the behavior I discovered when I tried the 'quarter test' (posts 620+623). If you don't find a short and have to contact Pololu support you don't need to talk about DCC++ specifics. You can simply tell them that M1 is working with your app but M2 is not. Their demo program reports a fault when you run it. You have the 'board enable' shunt installed. You have cut the link trace for pin 12 but have installed a header and shunt in order reconnect pin 12. It will be easier for them to help you diagnose the issue if you are using their app and not DCC++.
Mmm... 9V, eh? So the 5V power is still provided through the Arduino's little regulator? I'm not sure that's going to help with the WiFi shields... best I can tell the problems Im having are caused by a lack of 5V power and will require a heftier 5V regulator than what the Arduino's onboard can do. I'll test it out and see.
More on the Pololu short circuit test. I installed an NCE EB1 inline between the base station and my test track and then tried the quarter test - the Pololu shut down before the EB1 could kick in (by default the EB1 kicks in if the short lasts more than 16ms). Gregg - I got the current draw up to 200mA and issued the <c> command via the Send Packet window TwinDad built into the JMRI interface. The response in the DCC++ Traffic Monitor window was "11/1024". I tried the tail light protection method using an automotive circuit tester probe in series with the EB1. It lit up and neither the EB1 nor the Pololu protection kicked in (I tried it on both sides of the EB1). I don't have an 1156 tail light to test with right now. Will get one tomorrow.
TwinDad, Could you please describe the type of power supply problems you are having? What limitation would there be with a Pololu, Huzzah CC3000 WiFi and a Mega, with a 1 amp 5v power supply plugged into to the Mega? All the LEDs, servos and block detectors could use external power. If there is a Mega board limited power issue would it be possible to put the WiFi shield on a 2nd Mega connected to the i2c bus? Thanks, Dave
