*OS-DBTC* The 2nd Generation Open-Source-DBTC Thread

RT_Coker Feb 26, 2016

  1. RT_Coker

    RT_Coker TrainBoard Supporter

    516
    32
    13
    I made a second attempt to wire the BlueTrain test locomotive. It didn’t survive my not-so-good-eyes and shaky-hands. It functions but without any motor-drive. So after I mope around for awhile and eventually re-motivate myself, I hope to get back to working on the BlueTrain steam locomotive.

    Here are some pictures.
    BlueTrain TestLoco A.JPG BlueTrain TestLoco B.JPG BlueTrain TestLoco C.JPG

    Bob
     
  2. RT_Coker

    RT_Coker TrainBoard Supporter

    516
    32
    13
    I decided to create OS-DBTC “boards” that are basically like an HO-DCC-decoder-boards only without a direct DCC-power-connection. Here is the first one. The red-connector will be replaced by a smaller one in the 4 “production-boards” that are planned. The first board installation will hopefully be in a lipo-battery-power FTA soon, followed by a DCC-power steam engine. Each OS-DBTC installation will cost about $30 to $35 in parts not including the lipo-batteries.
    [​IMG]

    [​IMG]
    Bob
     
  3. RT_Coker

    RT_Coker TrainBoard Supporter

    516
    32
    13
    IMG_4287.JPG Here is an HO flat car carrying two removable 7.4 volt, 2.5 ampere-hour batteries and they are an excellent match for HO and some of the existing low-cost robotic hardware. The three wires are ground, 7.4 volts for the control-board and 14.8 volts for motor-control-board.

    Even though I am a so-so modeler this battery-car should be good enough to show the potential of an installation done by an experienced modeler.

    Bob
     
    Simon Mitchell likes this.
  4. RT_Coker

    RT_Coker TrainBoard Supporter

    516
    32
    13
    BT3Asm-5.JPG
    Pictured are 4 “production” OS-DBTC “boards” that are basically like 4-function HO-DCC-decoder-boards only without a direct DCC-power-connection. One 2-pin-connector is for tachometer-input and mark-input, and the other 2-pin-connector is for F2 and F3 function-outputs. All 4 “boards” work as tested on the breadboard “loco” despite being assembled by my shaky hands and not-so-good eye sight.

    Next up will be an android app that will let me wirelessly control the “boards” Bluetooth settings. It takes a long time for one person to create all the different hardware/firmware/software items and then get them working together.

    This will be followed by rewiring the lipo-battery-power FTA for a “production” OS-DBTC “board”.

    Bob
     
  5. RT_Coker

    RT_Coker TrainBoard Supporter

    516
    32
    13
    IMG_4321.JPG A picture of the BlueRail/Bachmann HO-FTA board. Had an opportunity to buy a new one for $46-shipped to check out. The App installation had a resolvable glitch and that probably explains the low price.

    Not an expert, but the low speed didn’t seem very smooth to me and had the sound of an audible motor-drive frequency.

    Bob
     
  6. RT_Coker

    RT_Coker TrainBoard Supporter

    516
    32
    13
    The un-updated Loco-firmware 3.21 apparently has a ~400 Hz motor drive that is fixed in the updated Loco-firmware 3.45. The problem is getting the Loco-firmware updated.

    Getting a “Connection failed” error after a brief “firmware downloaded and ready” message when trying to load new Loco-firmware version 3.45 over 3.21. Loco is a new Bachmann FTA and everything else appears to be working. Error occurs in both the latest downloads of the Bachmann and BlueRail Train Apps on two different Android devices. The internet connect is good. The apps downloaded and the updated Loco-firmware downloaded according to the app message “firmware downloaded and ready”.

    It appears that a “Secure Over-the-Air Bootloader” (Bluetooth name RigDFU) is being used. Reference: https://www.rigado.com/deviceops-platform/. The process appears to require a connection to an internet site that does the actual Loco-firmware update as opposed to having the app do the Loco-firmware update directly. This site connection appears to be what is causing the “Connection failed” error.

    Not much help from the B’man forum so far, and apparently no “service” option on the BlueRail Trains site. Looks like I will have to wait, until I can see my grandkid and can use his iThing.

    Bob
     
  7. RT_Coker

    RT_Coker TrainBoard Supporter

    516
    32
    13
    I browed an ios device, downloaded the BlueRail ios app, and successfully updated the loco-firmware to 3.45. The loco ran fine with the ios device. The loco is now much smoother and quieter at slow speed.

    Now the problem is that the loco will not run with either android Bachmann or BlueRail app.

    Bob
     
  8. RT_Coker

    RT_Coker TrainBoard Supporter

    516
    32
    13
    The android apps on both my android devices would run the loco with loco-firmware 3.21. But my apps on my android (4.4.4) phone would not work with loco-firmware 3.45. But, finally some good news, the BlueRail app on my android (5.1.1) tablet works with loco-firmware 3.45. So I finally have a working android/3.45 setup, and can “play”.

    Bob
     
  9. RT_Coker

    RT_Coker TrainBoard Supporter

    516
    32
    13
    This uncompleted open-source Direct-Bluetooth-Train-Control project is ended! It is beyond my diminished abilities to complete.

    I will be selling my remaining train things on eBay.

    So long and thanks for the help and support.

    Bob
     
    Simon Mitchell likes this.

Share This Page