Skip to main content

Replies sorted oldest to newest

I’m intrigued by this.  It supposedly can be run on “any” power source, But I am unsure if that includes AC. They mention straight DC, DCC or battery power in their presentation.  You can run it with a DCC system or the app.
Itll be interesting for sure if you can run it off 3 rail AC and the BT connection.
I would wait for the 4400 release for anything with dual motors.  I don’t think the 2200 has enough margin of error to handle it.  

Last edited by Boilermaker1

Beats the heck out of Decoder Pro.  But currently, the app is only available for Apple Devices.  It is up to Blue Rail to develop one for Android.

The Model 2200 will handle battery powered O Scale up to a stall current of 2A max.  It is too small for most battery powered O Scale locomotives.  The model 2200 is only the first so I would wait.

Watch the video.

John

Last edited by Craftech

I’m intrigued by this.  It supposedly can be run on “any” power source, But I am unsure if that includes AC. They mention straight DC, DCC or battery power in their presentation.  You can run it with a DCC system or the app.
Itll be interesting for sure if you can run it off 3 rail AC and the BT connection.
I would wait for the 4400 release for anything with dual motors.  I don’t think the 2200 has enough margin of error to handle it.  

All you need to do is install a full wave bridge in the engine or a battery.

Pete

Here is an article that discusses why BlueRail develops on iOS, then ports to Android:

http://bluerailtrains.com/why-...ions-before-android/

There are 50,000 types of Android devices to support (many of them old and buggy) as opposed to 2 iOS devices (iPhone and iPad). When you make a bluetooth app for iOS you can develop all of your energy on getting the app functionality right.  Once you release to Android, people expect it to run on 50,000 different types of devices, so you better be prepared to release lots of updates over the course of months to work around all the problems that arise on obscure poorly supported old devices.

@3RaylFan posted:

Here is an article that discusses why BlueRail develops on iOS, then ports to Android:

http://bluerailtrains.com/why-...ions-before-android/

There are 50,000 types of Android devices to support (many of them old and buggy) as opposed to 2 iOS devices (iPhone and iPad). When you make a bluetooth app for iOS you can develop all of your energy on getting the app functionality right.  Once you release to Android, people expect it to run on 50,000 different types of devices, so you better be prepared to release lots of updates over the course of months to work around all the problems that arise on obscure poorly supported old devices.

@3RaylFan,

You must be an Apple enthusiast.  There's a whole lot of 'facts' based on here-say in your analysis.  Have you built any apps yourself?  Your argument reads like an emotional one, not a technical one.

It's true that it was once the case that builders started with the iOS but in today's world it's no longer typical to start there and then add Android later.  Now, there's only one set of functionality, i.e., one set of functional code.  Interface code is different as you would expect, but the core is not.

For most app builders it's too expensive, and much more time consuming, to do it the old way.

BlueRail apparently doesn't believe so however.

I wish them luck but I believe that most people in our hobby have Android phones.  Maybe not all of us but most.  We may not prefer them but they are more affordable, and on a budget in seriously bad inflationary times money is very, very important.

Generally we spend our big bucks instead on locomotives, and maybe rolling stock, a little track, and a power source, but not on anything else, especially phones.

Mike

Add Reply

Post

OGR Publishing, Inc., 1310 Eastside Centre Ct, Suite 6, Mountain Home, AR 72653
800-980-OGRR (6477)
www.ogaugerr.com

×
×
×
×
Link copied to your clipboard.
×
×