<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word"> <div class="WordSection1"> We have an update regarding DC operation for this year’s Fair.<o:p></o:p> <o:p> </o:p> This past Wednesday, we operated in DC / Analog mode for the first time in several years. We had a mix of good operation along with some very peculiar and frustrating problems.<o:p></o:p> <o:p> </o:p> On the plus side, Cab 1 and Cab 2 performed normally throughout the session. It’s surprising that these two older consumer throttles can still supply adequate power for most equipment throughout our layout. They are showing signs of age and don’t output like they did when new, but are still quite functional. I operated Cab 2 during the whole session and only ran into one “overload” issue caused by a strange shorting issue on one of the turnouts.<o:p></o:p> <o:p> </o:p> The MRC power packs operating Cabs 3 and 4 were a different story. Without going into all the long, boring details, we had several intermittent and annoying problems that seemed to come and go unexplainably. All the MRC Cabs tested fine prior to Fair with no issues. In a couple instances, the problems seemed to be related to shorts caused when turnouts were switched. Cycling the turnouts from the Dispatch panel sometime cleared the issues, but not always. Cab 3 was giving us a lot of frustration. Gary Lewis and I were working the issues as they came up.<o:p></o:p> <o:p> </o:p> <div> At this point, I’d have to troubleshoot DC after Fair hours and that’s not really a good idea. The problems seem to be intermittent and clear themselves for no understandable reason. This doesn’t make for a stable operation. Gary and I discussed the situation with Jorg and we’ve determined that we will address the DC / Analog situation after the Fair.<o:p></o:p> <o:p> </o:p> That said…<o:p></o:p> <o:p> </o:p> We will be returning to DCC operation for the 1st shift on Wednesday for this year’s Fair. <o:p></o:p> <o:p> </o:p> For the folks who are scheduled for the 1st shift on Wednesday, please be sure you have DCC equipment to run.<o:p></o:p> <o:p> </o:p> Please leave the MRC handheld controllers plugged in to Cab 4 and 5. And please, do not make any further changes to any analog equipment; I need to troubleshoot exactly what happened with the exact configuration we used.<o:p></o:p> <o:p> </o:p> Let me know if you have any questions.<o:p></o:p> <o:p> </o:p> -Wayne<o:p></o:p> <o:p> </o:p> </div> <o:p></o:p> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: Wayne Toigo Sent: Thursday, June 15, 2023 7:27 PM To: <a href="mailto:HOscale@accrs.groups.io">HOscale@accrs.groups.io</a>; ACCRS HO Scale <<a href="mailto:accrs-ho@mail.accrs.org">accrs-ho@mail.accrs.org</a>>; <a href="mailto:kjwil209@gmail.com">kjwil209@gmail.com</a>; <a href="mailto:dylanrolson1@gmail.com"> dylanrolson1@gmail.com</a>; <a href="mailto:indigo.mcclellan@gmail.com">indigo.mcclellan@gmail.com</a>; <a href="mailto:burtonfamily101@gmail.com">burtonfamily101@gmail.com</a>; <a href="mailto:mrgaronm@aol.com"> mrgaronm@aol.com</a>; <a href="mailto:leiko.vaher@gmail.com">leiko.vaher@gmail.com</a>; <a href="mailto:masonbaker98@gmail.com">masonbaker98@gmail.com</a>; <a href="mailto:cb835924@gmail.com"> cb835924@gmail.com</a>; Joel Clark <<a href="mailto:clark.joel.a@gmail.com">clark.joel.a@gmail.com</a>>; <a href="mailto:zunigafregoso2105@gmail.com">zunigafregoso2105@gmail.com</a> Subject: HO Analog/DC operation for Fair<o:p></o:p> </div> </div> <o:p> </o:p> Folks,<o:p></o:p> <o:p> </o:p> Here are a few notes for Analog / DC operation for Fair (1st shift on Wednesdays).<o:p></o:p> <o:p> </o:p> Here is the current analog operating Cab state:<o:p></o:p> <o:p> </o:p> Cab 1 (left side of Dispatch panel) – Operational.<o:p></o:p> Cab 2 (right side of Dispatch panel) – Operational.<o:p></o:p> Cab 3 (Passenger yard panel, handheld mobile controller) – Operational.<o:p></o:p> Cab 4 (handheld mobile controller) – Operational.<o:p></o:p> Cab 5 (handheld mobile controller) – Operational.<o:p></o:p> Cab 6 (handheld mobile controller) – Inoperative.<o:p></o:p> <o:p> </o:p> There is one working handheld controller currently plugged into the connection ports for Cab 3, 4, and 5. It is very important that each controller remain with it’s assigned cab. You may move the handheld controller to another connection port of the same number, but do not connect the controller to a different cab. In other words, always keep the Cab 3 handheld with a Cab 3 port, the Cab 4 handheld with a Cab 4 port, and the Cab 5 handheld with a Cab 5 port.<o:p></o:p> <o:p> </o:p> The reason for this is that some years ago, MRC changed the wiring for the handheld controllers. If you plug in a new-style controller into an old-style power pack (or and vice versa), the rotating speed control knob will behave backwards (full clockwise produces 0 speed and full counter-clockwise will be full speed). Unfortunately, the handheld controllers themselves look identical. We have a mix of old-style and new-style power packs. I’ve sorted out the controllers to work with their specific Cabs. <o:p></o:p> <o:p> </o:p> So the easiest thing is to keep each controller with their current assigned cab.<o:p></o:p> <o:p> </o:p> Sorry if this is a bit complicated. Let me know if you have any questions. I plan to be attending all analog shifts.<o:p></o:p> <o:p> </o:p> <div> <o:p> </o:p> -Wayne<o:p></o:p> </div> <o:p> </o:p> </div> </body> </html>