Problems with different motor board and communication with cabs

marioquartz May 11, 2017

  1. marioquartz

    marioquartz New Member

    2
    2
    1
    Im using this board with a arduino Mega
    [​IMG]
    I performed the diagnosis of wiki and all are OK. But, when connect the current feedback the board stop working correctly. The command <c> show <a0> as opposed to values from 60 to 70 when not connected.

    And when the current pins are not connected dont read and dont write. Using the default address dont move the cab.

    Connections:
    EA (bridge) -> pin 3 (mega)
    I2 (bridge) -> pin 12 (mega)
    I1 (bridge) -> pin 12 (mega)
    EB (bridge) -> pin 11 (mega)
    I4 (bridge) -> pin 2 (mega)
    I3 (bridge) -> pin 2 (mega) and pin 13 (mega)
     
    Scott Eric Catalano likes this.
  2. Jimbo20

    Jimbo20 TrainBoard Member

    274
    178
    11
    Hi,
    Looking at the information on your board, it looks to me as though you have to connect your own external current sensing resistors, but it doesn't explain how you do this on the board!

    https://www.seeedstudio.com/L298-Dual-H-Bridge-Motor-Driver-p-284.html

    On the arduino motor shield the sensing resistors are 0.15 ohms.
    I've shown where they are on this schematic...

    [​IMG]
     
    Scott Eric Catalano likes this.
  3. marioquartz

    marioquartz New Member

    2
    2
    1
    Thank you!

    And a question: the current sensor is required for comunication? Appears so.
     
    Scott Eric Catalano likes this.
  4. Jimbo20

    Jimbo20 TrainBoard Member

    274
    178
    11
    Current sensing is needed for reading data back from the loco; the only way the loco can send data to the dcc controller is by 'pulsing' the motor, and the current sensor reads these pulses.

    Jim
     
    Scott Eric Catalano likes this.
  5. Keith Ledbetter

    Keith Ledbetter TrainBoard Member

    279
    195
    12
    To be fair you don't necessarily have to read back from your loco if you don't want to use it for programming, you can just give commands but if current sensing is totally disabled or not sensed then my guess is the DCC++ software won't go due to thinking you are/could be shorted or over current limit.

    If you are brave and are certain there are no shorts or overcurrent issues anywhere you could just set the value in the current sense (instead of reading it from A0) and see if at least you get responses. That would at least narrow it down to the fact that it is indeed having to do with the current sensing piece and you have to find out where to attach the resistors.

    Also for trouble shooting if I were you (if you haven't already) I would by an original motor shield (well a clone anyway) for $3 off ebay and get everything working with that to eliminate issues except with the motor driver. It's not good for much current at all but they do work and I use them a bunch to make sure changes work first before introducing the additional issues any "non-standard" motor shield can potentially bring.
     
    Scott Eric Catalano likes this.

Share This Page