Short story. Micro screwdriver bit fell through hole on switch mount area. Any one have disassemble steps to access beneath this panel? I can’t even see the bit through the hole. Thanks in advance.!
Original Post
Replies sorted oldest to newest
No disassemble! I lucked out. After putting the engine on my padded workbench and rolling her gently on to the roof. Back and forth once or twice, the bit managed to fall out through a hole in the bottom of the firebox. 🙂🙃🙂.
Now to continue troubleshooting why crew and tower talk no longer works after getting my Legacy Controller back from warranty repairs. 🤔
Haha I bet it felt great to see that thing roll back out!!
Do you think the problem is controller side? Or engine side?
@BillYo414 posted:Haha I bet it felt great to see that thing roll back out!!
Do you think the problem is controller side? Or engine side?
It sure did feel good. I was actually trying to us a strong re magnet mounted to the switch plate near the hole in hopes that would hold the bit in place if it came close enough.
Right now I’m still leaning a bit towards the engine side for the crew talk absence. The controller base and remote was sent back under RMA for a defective CTC / On Off switch on the remote itself. There are a few odd things about the remote. But what I think may be engine sided is that while I had the controller out on RMA I used the LionCheif app a bit. When using it, I heard some light squeaking from either the engine or tender. I used the LC app to turn down all of the sound effects to zero. Heard the squeaking.. and said to myself OK. Needs a light oil job here. Let me come back after I put together a padded bench... I did not, the engine sat on the track until I got the controller and remote back just this past Thursday. All sounds work except crew and tower talk. Now to make it goofy and lean towards the Engine being a problem even more. I have on the BigBoy Train an aux water tender with crew talk. It works fine, uses same remote buttons. I reset the Bigboy according to the directions JIC. Still no crew talk.
I wish I had the engine myself so I knew how everything was arranged. Have you checked the tether connection between the engine and tender? That can affect the sound depending on where the boards and speakers are.
In this engine the crew talk sounds are in the locomotive. In the app I’d make sure all the volumes where all the way up and of still no dice I’d say there’s either something amiss with the RCMC or RS-lite board.
I would also try the sounds without the tender on the track to make sure the front speaker still has whistle, chuff, and bell
just as a FYI typically when help is asked for the first thing anyone is gonna need is a Lionel product number. We know what you talking about this time but just FYI 
Did you turn off those sounds when you used the Bluetooth App? You can adjust Bell, Horn/Whistle, Engine sounds, and dialog independently. Perhaps you accidentally lowered the dialog all the way down.
Attachments
@MartyE posted:Did you turn off those sounds when you used the Bluetooth App? You can adjust Bell, Horn/Whistle, Engine sounds, and dialog independently. Perhaps you accidentally lowered the dialog all the way down.
Crew Talk issue resolved. The ultimate culprit is two fold. (Maybe three)
1. Use the same Lion Chief app device to turn the volume back up as I did turn it down, ( iPad as opposed to my iPhone - I used the iPhone yesterday and the app was acting buggy, the mic volume slider was jumping around and not holding ).
2. Seems since there is no Crew Talk only volume specific settings for the Legacy Controller (IAFAIKT) using any volume settings or engine reset there has no result.
3. I’m a newb to the Legacy Remote Controller and this LC App mix-up mish mosh.
All is now better in my Lionel RR world. Thanks for the input and tips to all!!
Number 1 is a doozy if that's the case. There will be a lot of people cussing in poetic masterpieces over that.
@BillYo414 I agree. If you change a volume or setting on one device, iPad then later come back to run your set again. For instance using an iPad or Legacy set instead, what could it not be able to control or change that previous set state? 🤔
Maybe I missed a note in a manual?
I'm not sure. I currently only have the handset for my Lionel stuff or else I would run downstairs and try it now.
Hopefully that can be fixed/adjusted in a programming update if it is the case.
