Lionel Base3

@ToledoEd posted:

Marty, I followed your video using my iPhone. Update was painless, thanks for posting.  Question, can you also update the Cab3 App for use on an iPad so the new functions of the home page...as shown on the additional icons, arrows, engine, Base3?  I did open the Cab3 App on my iPad from the App store but it does not show the additional icons or functionality.

You should be able to.  If it's already on the iPad you may have to go back to the app store and press update for the Cab3 app.

Marty, it worked, after I updated to iOS 18. Didn't show up in the previous iOS on my iPad.  Thanks, again!

@MartyE posted:

You should be able to.  If it's already on the iPad you may have to go back to the app store and press update for the Cab3 app.

Hi Marty,

interesting quirk has appeared. After all updated, when you copy all engines to blank module. Then start the transfer to cab -3 one at a time. If you pick the engine to install it will always default to the information from the first one. The fix is to transfer the info then input engine type and cab number.

@ThatGuy posted:

Hi Marty,

interesting quirk has appeared. After all updated, when you copy all engines to blank module. Then start the transfer to cab -3 one at a time. If you pick the engine to install it will always default to the information from the first one. The fix is to transfer the info then input engine type and cab number.

I'm not sure what you are trying to explain.  I would definitely send it to TalktoUs@lionel.com.  I won't be able to try this until tomorrow.

@MartyE posted:

I'm not sure what you are trying to explain.  I would definitely send it to TalktoUs@lionel.com.  I won't be able to try this until tomorrow.

Sorry let me try again. On my apple tablet when I insert the black module and engine select to install one at a time as required. The first engine loads fine, select the next and it defaults to the information from the first on.

@ThatGuy posted:

Sorry let me try again. On my apple tablet when I insert the black module and engine select to install one at a time as required. The first engine loads fine, select the next and it defaults to the information from the first on.

OK.  I'll try this tonight and see what I find.

@MartyE posted:

OK.  I'll try this tonight and see what I find.

Thanks Marty

Anyone get their TPC to work with the new cab3 update?

@Kneissl posted:

Anyone get their TPC to work with the new cab3 update?

If you read the release notes that is still a work in progress.

New bug found (or maybe still leftover before the update) in the big red dial, when you increase speed the locomotive speeds up but the engine rev sound does not increase.

@gunrunnerjohn posted:

Which means it's hardly current!

I wonder why every section of the website has a "print" icon...hhhhmmm. 

Lots of frustration trying to run an ERR engine today after getting my original Base2 database transferred to the Base3 with the BS3U utility. The two 'usable' TMCC modes (CAB1 and TMCC) are very, very unstable. CAB2 TMCC modes still work as they should when used with the Base 3. Just give your engine lots of room if you are going to try any ERR stuff. I have yet to try OEM Odyssey (only have one left in the roster) or EOB.

I don't like either throttle option very much for TMCC, they are pretty vague feeling even if the control mode seems to be semi-responsive. It would be nice to have a 'tap' throttle for dialing in slow speeds when they get the TMCC modes to work like the CAB2.

Legacy engines don't seem to trigger the brake sounds when decelerating to zero speed with the CAB3 app. This still works normally with the CAB2/Base3.

@Norm Charbonneau posted:

Legacy engines don't seem to trigger the brake sounds when decelerating to zero speed with the CAB3 app. This still works normally with the CAB2/Base3.

This is true of the CAB-1L too. No brake sounds. I think the reason is that the CAB-2 offers an auto brake setting called V.T.A.B. - Velocity Throttle Auto-Brake.

I've experienced a speed control problem running ERR engines with the CAB3. Sometimes the engines do not stop when the CAB3 speed slider drops to 000. The problem occurs erratically whether in CAB1 or TMCC mode. The good news is that I don't have this issue using the CAB2 hand-held with the Base3. So the problem seems related to the CAB3 and not the Base3. I learned from the initial release of the CAB3/BASE3 combo that it is critical to operate near a track-power kill switch. 

Any details on the Cab 3 update 1.1.035 today? I see in a new version in the iOS APP store.

@DaddyChooChoo posted:

Any details on the Cab 3 update 1.1.035 today? I see in a new version in the iOS APP store.

Variable "Halt" delay has been added. Varies between 0.3 seconds and 3 seconds under Base3 configuration menu.  Not sure what else.  That should make some folks happy.

I suspect @Dave Olson will be putting up the change list when he gets a chance.

@MartyE posted:

You should be able to.  If it's already on the iPad you may have to go back to the app store and press update for the Cab3 app.

Marty,

By variable , what do U mean?  Is it automatically adjusted or is it controlled by someone who adjusts it!   The only thing I noticed about the “HALT” Button prior it was very slow to respond!!

Fredstrains

@MartyE posted:

Variable "Halt" delay has been added. Varies between 0.3 seconds and 3 seconds under Base3 configuration menu.  Not sure what else.  That should make some folks happy.

I suspect @Dave Olson will be putting up the change list when he gets a chance.

@Fredstrains posted:

Marty,

By variable , what do U mean?  Is it automatically adjusted or is it controlled by someone who adjusts it!   The only thing I noticed about the “HALT” Button prior it was very slow to respond!!

Fredstrains

You set how long you need to hold it for it to activate. From a .3 seconds to 3 seconds. It’s up to you.

@MartyE posted:

You set how long you need to hold it for it to activate. From a .3 seconds to 3 seconds. It’s up to you.

MARTY,

Didn't realize it was under that Screen. It’s under CAB3 Settings, but under BASE3 Configurations.  Didn’t know that screen was even there !!’  O well : LIVE  & LEARN !!

FREDSTRAINS

Fred

@Fredstrains posted:

MARTY,

Didn't realize it was under that Screen. It’s under CAB3 Settings, but under BASE3 Configurations.  Didn’t know that screen was even there !!’  O well : LIVE  & LEARN !!

FREDSTRAINS

Fred

It's new with this update.  Come on Fred follow along!  LOL!  Just kidding!

@MartyE posted:

It's new with this update.  Come on Fred follow along!  LOL!  Just kidding!

No wonder I’ve never seen it before!!

IT WAS NEVER THERE !!

I’ll tell you:  About the time I start to understand this BASE3, CAB3,  B3SU System,  someone throws in a “RINGER”!!……..LOL

AND, there not done yet……..There is still the “Brake, PM & ZWL, etc Issues to go !!’

FREDSTRAINS

This is the only locomotive I have that does not like the Base 3. I mentioned this one, many pages back, and I thought software / firmware updates might solve my problem but no luck so far.  I have a TMCC k-Line by Lionel SD75 model # 2-11559. I programmed it into the base 3 at ID 03 and the sounds all connected and I originally thought it would not move since I only moved the throttle on the CAB 3 a small amount.  after I updated the base 3 I thought I would try it again and I pushed the throttle all the way up on the cab 3 - bingo, the loco does move- at a crawl.  Do I have a reprogramming issue?  Here is the documentation I have and a picture of the locomotive.   I have not been inside this but perhaps I need to? Suggestions welcome.

New updated app for iPhone was released tonight.  Version is now 1.1.35.  Said it was for bug fixes.

Neal Jeter

@hokie71 posted:

This is the only locomotive I have that does not like the Base 3. I mentioned this one, many pages back, and I thought software / firmware updates might solve my problem but no luck so far.  I have a TMCC k-Line by Lionel SD75 model # 2-11559. I programmed it into the base 3 at ID 03 and the sounds all connected and I originally thought it would not move since I only moved the throttle on the CAB 3 a small amount.  after I updated the base 3 I thought I would try it again and I pushed the throttle all the way up on the cab 3 - bingo, the loco does move- at a crawl.  Do I have a reprogramming issue?  Here is the documentation I have and a picture of the locomotive.   I have not been inside this but perhaps I need to? Suggestions welcome.

Do you know how many speed steps it is programmed for - 32,128, or 256? Try setting it for 32 speed steps.

Ken

@Lionlman posted:

New updated app for iPhone was released tonight.  Version is now 1.1.35.  Said it was for bug fixes.

Neal Jeter

It's discussed a bit above.  Also adds a variable delay for the HALT command.  You can make HALT instant, .3 second hold of the button to a 3 second hold of the button before it triggers a HALT and everywhere in between.

@kanawha posted:

Do you know how many speed steps it is programmed for - 32,128, or 256? Try setting it for 32 speed steps.

Ken

Thanks Ken, i don't know what speed steps it is and was thinking I may need to hook up the CAB 1 again to do this. I don't think the base 3 can accomplish speed step changes in TMCC? That K-line / tmcc pdf in the first post contains the instructions I have used over the years with the Cab  1

As you can guess, it ran fine with the cab 1 at whatever speed it is now set for. 

@hokie71 posted:

Thanks Ken, i don't know what speed steps it is and was thinking I may need to hook up the CAB 1 again to do this. I don't think the base 3 can accomplish speed step changes in TMCC? That K-line / tmcc pdf in the first post contains the instructions I have used over the years with the Cab  1

The response to speed steps are determined by the receiving locomotive.  As for the BASE3, it's the same as the Legacy command base as far as handling speed steps.  The actual format of the speed commands sent are determined by the remote, not the command base.

@gunrunnerjohn posted:

The response to speed steps are determined by the receiving locomotive.  As for the BASE3, it's the same as the Legacy command base as far as handling speed steps.  The actual format of the speed commands sent are determined by the remote, not the command base.

Let's see if this gives any clue, here is what I did to go to 32 steps and here is what I accomplished:

1) Starting point: The loco speed responds correctly to the red dial on the cab 1 when base 1 is connected.

2) I could not find any way to use the cab 3 / base 3 to change TMCC speed steps so I reconnected the old cab 1/ base 1 system.

3) With base 1 connected, used the cab 1 to change speed steps to 32.  Using the cab 1, good speed range using the cab 1.

4) reconnected the base 3 and using the cab 3 app, the locomotive runs about 5 scale miles per hour tops and the throttle registers 32 steps at max on the numerical read out on the app. This is an improvement over the crawl I started with. I should have paid attention, but it must have originally been at 256 when I first tried to run this loco a few weeks ago when the base 3 had just arrived. It barely crawls at that speed setting with the base 3/ cab 3.

Per GRJ's comment, the speed step response is in the locomotive, but it must be receiving something different from the cab 1 versus the cab 3/ base 3? Am I missing a setting in the cab 3/ base 3?

@hokie71 posted:

Per GRJ's comment, the speed step response is in the locomotive, but it must be receiving something different from the cab 1 versus the cab 3/ base 3? Am I missing a setting in the cab 3/ base 3?

How do you have the locomotive configured in the Cab3 app?  If not set this way already, try CAB1 mode.

@hokie71 posted:

Per GRJ's comment, the speed step response is in the locomotive, but it must be receiving something different from the cab 1 versus the cab 3/ base 3? Am I missing a setting in the cab 3/ base 3?

That's how it works for stuff like the ERR Cruise products and TAS EOB boards.  However, Legacy automatically switches based on what it receives, there is no locomotive configuration in that case.  In the Legacy case, the remote configures the command base for the step size and operating mode.  Since I've personally run with the BASE3 using the CAB1L and CAB2 without issues related to speed control, I'd have to say the issues you have are probably related to operating with the CAB3.

@rplst8 posted:

How do you have the locomotive configured in the Cab3 app?  If not set this way already, try CAB1 mode.

I had it in TMCC mode and just tried CAB 1- I forgot that choice was there. Sadly, no joy, it would not move in CAB 1 mode at all which is surprising.  Perhaps related to what GRJ mentioned, maybe a CAB 3 programming issue related to old technology?

@hokie71 posted:

I had it in TMCC mode and just tried CAB 1- I forgot that choice was there. Sadly, no joy, it would not move in CAB 1 mode at all which is surprising.  Perhaps related to what GRJ mentioned, maybe a CAB 3 programming issue related to old technology?

Sounds like the CAB1 mode of the Cab3 or Base3 isn't properly sending relative speed increment commands.

One way to know which is the problem would be to use a CAB-1L or CAB-2 in CAB-1 mode to see if that works. If it does, then it's a Cab3 app problem.  If it doesn't it's a Base3 problem.

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. 🤞

@hokie71 posted:

I had it in TMCC mode and just tried CAB 1- I forgot that choice was there. Sadly, no joy, it would not move in CAB 1 mode at all which is surprising.  Perhaps related to what GRJ mentioned, maybe a CAB 3 programming issue related to old technology?

Known problem, the CAB1 is not sending relative speed steps, so CAB1 mode won't work.  I suspect Dave fixed that in the latest release, did you get that?

@rplst8 posted:

Sounds like the CAB1 mode of the Cab3 or Base3 isn't properly sending relative speed increment commands.

One way to know which is the problem would be to use a CAB-1L or CAB-2 in CAB-1 mode to see if that works. If it does, then it's a Cab3 app problem.  If it doesn't it's a Base3 problem.

The CAB1L works fine with the BASE3, so I'm pretty sure it's the CAB3 that is the issue.

@gunrunnerjohn posted:

The CAB1L works fine with the BASE3, so I'm pretty sure it's the CAB3 that is the issue.

Isn't ERR supposed to use R100 control type?

REL 100 MODE
100 Relative speed commands
Electric RR or EOB speed control
Lionel OEM’s (with Electric RR cruise

From the Power and Control site...

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

• Using TR for transformers
• Multiple momentum fixes
• Multiple throttle position errors
• Train Brake issues
• 4-Digit engine brake
• TMCC Trains
• Database backup and restore (local)
• R100 control type
• Maintain Wi-Fi connection when phone screen times out

@MartyE posted:

Isn't ERR supposed to use R100 control type?

Marty, R100 sends relative step commands, the only difference between it and CAB1 is they changed the keyboard to the TMCC icons and added the throttle graph.  However, if you've used R100 at all, you'll find that the throttle graph can easily get out of sync with the actual locomotive speed.  This is because if you spin the knob too fast (pretty slow is too fast), it loses track of the actual speed.  ERR cruise, K-Line cruise, and TAS EOB all run fine using their fine step settings with CAB1 control from a real remote.

I'm not sure what about R100 mode doesn't work on the CAB3, but I previously read here that the CAB3 was not sending relative step commands, that's the major issue.

@gunrunnerjohn posted:

Known problem, the CAB1 is not sending relative speed steps, so CAB1 mode won't work.  I suspect Dave fixed that in the latest release, did you get that?

I have CAB3 version 1.1.035 - i did try Cab 1 mode and no luck.  I need to borrow a cab 1L since I only have a cab 1

@hokie71 posted:

I have CAB3 version 1.1.035 - i did try Cab 1 mode and no luck.  I need to borrow a cab 1L since I only have a cab 1

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

Well, Got an app update on the phone. Came to see if anything fixed, but I see there is some progress according to the patch notes.