Lionel Base3

@gunrunnerjohn posted:

The CAB1L is a worthwhile investment, that gives you one physical remote that you can use with the BASE3.

I bought one. Very much important to have. Use your phone to setup locomotives, trains, acc in the base3. Use the 1L controller after that.

For those that are not aware, Base3 reserves a range of ENG ID's for Bluetooth and RF control. If you have anything in the 20-40 range, might want to change that.

@Stone Rhino posted:

I bought one. Very much important to have. Use your phone to setup locomotives, trains, acc in the base3. Use the 1L controller after that.

For those that are not aware, Base3 reserves a range of ENG ID's for Bluetooth and RF control. If you have anything in the 20-40 range, might want to change that.

2-29 range.  2-9 are for RF LC engines and 10-29 are for BlueTooth LC engines.

If you have no BT or RF engines in any of the address's in 2-29 it is not a problem.  You can use the address for anything.   Those address's just have extra value.

@Reading RR posted:

If you have no BT or RF engines in any of the address's in 2-29 it is not a problem.  You can use the address for anything.   Those address's just have extra value.

That is correct.  There are some challenges with setting a stall voltage on those addresses if need be for older Pullmor motors since the "SET" button clears out the information stored in the Base3 but Lionel posted a work around they are effectively available to all types of engines.

Just FYI from the Power and Control site...

TMCC Engine Disclaimer

Since IDs 2 through 29 are potentially Legacy, TMCC, RF, or Bluetooth, clearing engine information (name/number) can give slightly different results than with IDs 30 and up.

If the ID is set as Legacy, then the entry is not cleared with SET, as RF or BLE are not controlled as Legacy locos.

If the ID is set as non-Legacy (I.E. TMCC); AND the RF or BLE switch is in RUN; then the entry is CLEARED and the loco is UNPAIRED.

A TMCC engine’s name/number is lost if you press “SET” when setting the ID. Just enter the relevant info once you set the loco ID.

Lastly, older PULMOR equipped TMCC engines used “SET” to set the stall speed step in the loco. In this case, the “SET” will erase the name/number. The only fix for this is to move the TMCC ID out of the 2-29 range OR re-enter the info once you set the TMCC ID and set the STALL.

@Kneissl posted:

I think this latest update fixes my major gripes. I can turn on my track power now. The halt button is better and I didn’t get any runways. 🤞

Morning,

What was your procedure you used to turn TRACK POWER on?  Please give me the sequence of Buttons you used!  I can’t get it to work properly ‘.   Am I missing something?

FREDSTRAINS

This is where the B3SU comes in handy.  You can quickly enter all the missing data using a full keyboard ten times as fast as doing it with a remote.

I have my TPU programmed to TR #1

so just hit TR 01 and then the “boost” button

@Fredstrains posted:

Morning,

What was your procedure you used to turn TRACK POWER on?  Please give me the sequence of Buttons you used!  I can’t get it to work properly ‘.   Am I missing something?

FREDSTRAINS

Normally I hit TR1 (with my CAB2) and Spin the Speed Dial to 18v on my ZWL!  

I will try your Procedure with the CAB3 on my ZWL.

FREDSTRAINS

This is probably a stupid question, but how do you program a legacy engine with bluetooth into the Base 3 using the IOS Base 3 app?  I've looked at the online Lionel instructions, my Legacy engine with bluetooth programming page.  Bluetooth legacy engines have both the program/run switch and the bluetooth on/off switches.  Anything I try doesn't work.  So frustrating.

@Fredstrains posted:

Normally I hit TR1 (with my CAB2) and Spin the Speed Dial to 18v on my ZWL!  

I will try your Procedure with the CAB3 on my ZWL.

FREDSTRAINS

It does not work for me.  I have my ZWL  Programed for TRACK 1, 2, 3 & 4.  I hit TR 01 and push "BOAST".   It pulsates and the best I can get is 10Volts when it stops pulsating  !!??   Normally I use the procedure described above with my CAB1, or CAB2.   I dont think the BUG is "Fixed" yet.

FREDSTRAINS

Oh sorry I’m using a TPC. Never used a ZWL.

https://www.lionel.com/product...ler-tpc-400-6-14179/

@Fredstrains posted:

It does not work for me.  I have my ZWL  Programed for TRACK 1, 2, 3 & 4.  I hit TR 01 and push "BOAST".   It pulsates and the best I can get is 10Volts when it stops pulsating  !!??   Normally I use the procedure described above with my CAB1, or CAB2.   I dont think the BUG is "Fixed" yet.

FREDSTRAINS

@Jim Duke posted:

This is probably a stupid question, but how do you program a legacy engine with bluetooth into the Base 3 using the IOS Base 3 app?  I've looked at the online Lionel instructions, my Legacy engine with bluetooth programming page.  Bluetooth legacy engines have both the program/run switch and the bluetooth on/off switches.  Anything I try doesn't work.  So frustrating.

A Legacy w/ Bluetooth engine should be entered into a Base3 using a TMCC ID and the RUN/PGM procedure.

Put the PGM/RUN switch in PGM.  Power up the track and using the APP push ENG# XX (being the ID you are assigning it) SET.  The horn will sound.  Move switch back to RUN.

Using the app address the ENG using the # you assigned and push enter.  Go into the ENG config screen and add the pertinent information such as name, road number control type (Legacy) and Railsounds type (Legacy).

Appears that the most recent CAB3 update enables the user to run TMCC trains. I created a train to test between two of my LC 2.0 locomotives. Each locomotive is programmed as TMCC. When I create the train, the settings screen shows the train control type as Legacy. I am unable to address the train using the Cab3.

Does anyone have any suggestions, or perhaps running/creating TMCC trains is still an issue?

Bradley

@BAM Railroad posted:

Appears that the most recent CAB3 update enables the user to run TMCC trains. I created a train to test between two of my LC 2.0 locomotives. Each locomotive is programmed as TMCC. When I create the train, the settings screen shows the train control type as Legacy. I am unable to address the train using the Cab3.

Does anyone have any suggestions, or perhaps running/creating TMCC trains is still an issue?

Bradley

TMCC trains can only be IDs 1-9

Legacy trains can be 1-99

@BAM Railroad posted:

Appears that the most recent CAB3 update enables the user to run TMCC trains. I created a train to test between two of my LC 2.0 locomotives. Each locomotive is programmed as TMCC. When I create the train, the settings screen shows the train control type as Legacy. I am unable to address the train using the Cab3.

You were always able to run TMCC trains with the Legacy command system and even the old CAB1/BASE1.  You could never create a TMCC train with an ID greater than 9 from day one.  From Dave's comment, it looks like that functionality didn't change with the BASE3.

For what it's worth here is the latest enhancements and fixes. These can be found on the Lionel Power and Control site under Cab3.

V1.1.035

Release date: 9/27/24

New features!

• Cab3 settings menu accessed via Base Details menu
• User settable timer for HALT button (0.3 to 3 seconds)
• TMCC trains can now be built and operated

This release fixes the following:

• TMCC engines not stopping
• ACC throttle commands
• TMCC blowdown/water reversed
• Various momentum fixes for TMCC engines
• 4-Digit brakes

Bugs still to be worked on (high-level only):

• Using TR for transformers
• Multiple throttle position errors
• Train Brake issues
• Various Cab1 control type issues
• R100 control type
• Maintain Wi-Fi connection when phone screen times out

Future features:

• VSR (Bluetooth tab)
• Hotspot mode (Bluetooth tab)
• Database backup and restore (local)
• Record
• Bar graph for EFX
• Real-time metrics for 4-Digit engines
• Audible button tap
• Storing/Transferring custom engine images
• Option for selecting default tab when first opening APP

@Dave Olson posted:

TMCC trains can only be IDs 1-9

Legacy trains can be 1-99

Thanks Dave . . . I should have known that. Still a first time Legacy user, so still getting used to the system.

I do seem to be having a lot of issues with addressing engines and trains in general. Cab3 seems a little finicky, sometimes I press the start up and shutdown buttons and the engines respond as they should. Many other times, the engines sit idle and do not respond to either command. This is the case for Legacy and TMCC locos and trains. Not sure if anyone else is experiencing this? Also, I feel like the momentum settings changed in one of the last updates. Have all locos set to lowest momentum setting, yet trains take a while to slow to a hault vs. the prior Cab3 version.

Bradley

So I am successfully running TMCC trains via the CAB3. Appears that Legacy Trains and TMCC trains do not start up and shut down in the same manner? Legacy trains use the power on and off switch where you can hold down the button for extended start up/shut down or tap once for quick start up/shut down.

TMCC trains do not seem to respond to these buttons, even though the locomotives do in ENG mode. Appears you have to use the railsounds button to turn off/on?

Going by trial and error. Do I have everything correct?

@BAM Railroad posted:

So I am successfully running TMCC trains via the CAB3. Appears that Legacy Trains and TMCC trains do not start up and shut down in the same manner? Legacy trains use the power on and off switch where you can hold down the button for extended start up/shut down or tap once for quick start up/shut down.

TMCC trains do not seem to respond to these buttons, even though the locomotives do in ENG mode. Appears you have to use the railsounds button to turn off/on?

Going by trial and error. Do I have everything correct?

I found that if the RPMs haven't ramped down on diesels they will not shut down until I manually lower them or they eventually lower themselves.  Been this way forever.  Maybe that's what you are encountering?

We had another run session tonight with the latest version of the app.  Everything ran okay but we are cautious with our finger ready on the master power switch.

One bug popped up,as we switched between two different legacy engines, the direction control didn't change. Engine A was moving forward and the direction button was pressed. The engine stopped and the direction button on the APP changed from FWD to REV. We then switched to a different engine. Engine B was in Forward but the APP still indicated the REV direction.  Moving the slider, the Engine did move forward but we had to cycle the direction button a few times to get the engine direction and the direction button to get in sync.

One app enhancement came up with the Bell function. While Lionel is trying to cram the entire operating interface of the CAB2 into a single screen of the app, mimicking the physical motion of the Bell button makes it hard to use.  Instead of the swipe & hold they have now, how about a single quick tap to ring the bell once and then hold the button for 2 seconds to cycle the continuous ring on or off.

@H1000 posted:

One app enhancement came up with the Bell function. While Lionel is trying to cram the entire operating interface of the CAB2 into a single screen of the app, mimicking the physical motion of the Bell button makes it hard to use.  Instead of the swipe & hold they have now, how about a single quick tap to ring the bell once and then hold the button for 2 seconds to cycle the continuous ring on or off.

The only problem with this is that the bell can also be a weak "ding or a strong "ding" when doing a one strike.  On a Cab2 depending on how far you push the slider determines the strength of the "ding".  Right now the Cab3 App has a hard time replicating it but I believe that's what they are going for.  Maybe a better scenario than replicating the slider is a tap is a soft bell, a longer hold up to say 3 seconds gets you the other variations.  and then a 4 second hold gets always on and off.

@MartyE posted:

The only problem with this is that the bell can also be a weak "ding or a strong "ding" when doing a one strike.  On a Cab2 depending on how far you push the slider determines the strength of the "ding".  Right now the Cab3 App has a hard time replicating it but I believe that's what they are going for.  Maybe a better scenario than replicating the slider is a tap is a soft bell, a longer hold up to say 3 seconds gets you the other variations.  and then a 4 second hold gets always on and off.

Trying to hold for 3 seconds vs 4 seconds correctly is probably harder than you think.

@gunrunnerjohn posted:

Trying to hold for 3 seconds vs 4 seconds correctly is probably harder than you think.

I bet you’ll figure out the timing soon enough.