Every so often a request comes around asking for a book like Barry's DCS guide to be written for TMCC.
So the question is asked, what would you like in the book?
One subject that will not be discussed is how to get TMCC/Legacy/DCS to all work together. Barry more than covers that in his book, and if you are a DCS user you should be buying that book anyway.
Replies sorted oldest to newest
Boy that's a big question.
Installation - Show the instructions for all the different modules, their uses, and problems and fixes. They need to be in one place. Please try to destroy the myth of the transmitting outside rail and explain the proper use of earth ground.
Operation - Try and explain in simple terms that TMCC and Legacy are the same system with Legacy having more features. There are still people out there that seem to have the idea that they are different systems. Explain in detail the differences in operation of Legacy engines under TMCC and Legacy control.
There are many more but by the time I would have listed them all I would have written the book.
Al
I think a better explanation not so much Legacy but how all the various components all go together, yhe programming of them, and some basic gotchas.
I would never say more information isn't needed but there is a fair amount of information and experience available here to help folks get it right.
Along with the new videos from Lionel these questions are being covered.
Along with the new videos from Lionel these questions are being covered.
The one thing about a complete book is it would be all in one place. I've started reading Barry's DCS book from cover to cover to see in total what's there, because a number of times I've wanted to know something, and it's there. The one thing I'd like to see in that book as well as any Legacy book is a very comprehensive index.
The advantage of a book, of course, is that if it's properly done it serves as a comprehensive resource through the date it is published. The information can generally be found elsewhere through multiple sources if one is inclined to undertake the search, but having everything together in one handy reference is certainly a plus.
Barry Broskowitz did a superb job with the DCS book and I have found it to be a great source of useful information whenever I have a question about my own DCS system. Now that I also have Lionel Legacy installed (recently), I still tend to have more questions than answers. I have the good fortune of being in close touch with my friend Mike Reagan, whose operation is just a few miles away, so my situation is somewhat different than others.
The downside to a book is that, especially when it comes to technology, things can be rather quickly outdated. Still, unless one is determined to always have the latest and greatest techno gizmos, that really doesn't have all that much impact. Once I have something that works well and have learned all that I care to know about it, I'm usually content to just stick with what I have unless there's some compelling reason to "upgrade."
Hi guys,
I'll second the topics of ground planes and the assorted modules. A review of the modules should include...
-Original TMCC components (CB-1, Cab-1, SC-1, SC-2, new ZW, Power Masters, etc.)
-IC-Controls components (ASC, ARC, TPC 300 & 400, etc.)
-Legacy components (CB-2, Cab-2, ZW-L, Power Master Bridge)
-Third party TMCC compatible components (Z-stuff DZ-2500, DZ-2001, etc.)
Information on pinouts for making cables would be very useful, including the pinouts of the Legacy Y-cable.
There should be a chapter on conventional control that explains the functionality and idiosyncrasies of the Power Masters, new ZW's, ZW-L's, TPC's, etc. You wouldn't need to repeat things that are explicitly in the user manuals (like how to program the ID's or starting voltage), but a comparison of their merits for different applications would be useful.
There could be several chapters related to locomotives. One chapter should cover the various generations of Railsounds up through RS5. Another chapter should be dedicated to variations of Legacy engines (w/ or w/o Odyssey II, RS5.5, etc.). Perhaps the most useful chapter for folks buying used engines would be a review of TMCC licensed hardware from TAS, ERR, K-Line, and Digital Dynamics. It would be very useful to get that info in one place while it's still easy to find manuals for some of the electronics that have gone out of production.
There could also be a chapter dedicated to computer control options. It should explain the capabilities of the various TMCC compatible software packages including JMRI, Rocrail, RR&Co. Train Controller, and Kam Industries Train Tools.
There's probably a good chapters worth of TMCC enabled accessories as well. Lionel items like the operating crane car and command enabled FasTrack switches would be a must. Other third party items like the TAS smoke fluid loader, Z-stuff DZ-2000 switch machine controller, and Ross turntable would also be helpful. You could also include ASC, SC-1 and SC-2 wiring and programming instructions for conventional accessories such as the Atlas turntable, Tortoise switch machines, and Lionel magnetic crane.
One thing that might work well as an appendix would be a series of Cab-1 button overlays. You could include the generic TMCC steam and diesel overlays as well as some of the special overlays such as the Acela and operating crane. If someone lost an overlay, or purchased one used and didn't get the overlay, they could print a copy on a transparency.
There's a LOT of good stuff out there for TMCC and Legacy. Third party items have greatly expanded the possibilities of the system, but they also have left a hole in the documentation of how to integrate non-Lionel items with Lionel control hardware. For newbies who haven't absorbed the institutional memory found on this forum a comprehensive book could be of great value. Barry's experience with digital and on-demand paper publishing has proved there is a market for this type of book and a feasible means to bring it to the public.
Originally posted by gunrunnerjohn:
The one thing I'd like to see in that book as well as any Legacy book is a very comprehensive index.
That's one of the reasons I've warmed up to the digital edition of the DCS Companion. The pdf is searchable. That makes it a LOT easier to find even brief references that can be scattered throughout the book.
That's also why I got the digital version. 
However, there are times I wish I had the print version.
Every so often a request comes around asking for a book like Barry's DCS guide to be written for TMCC.
So the question is asked, what would you like in the book?
One subject that will not be discussed is how to get TMCC/Legacy/DCS to all work together. Barry more than covers that in his book, and if you are a DCS user you should be buying that book anyway.
As someone said earlier, a book is only as good as the day it is published, so therefore why not create a dedicated website and that way you can always keep it up to date as changes occur.
Regards,
Neil
I'm guessing the writer of the book wants to get paid. 
Also, you can't carry the website everywhere with you as you can a book.
I'm guessing the writer of the book wants to get paid. Also, you can't carry the website everywhere with you as you can a book.
Yes, I agree that there would be a financial element behind it, perhaps it could be a contender for the 'Booker' prize at some point.
At least with a website you can still print off pages/sections and take them with you or if you have 'tablet' device you can view it while mobile.
Regards,
Neil
I'm guessing the writer of the book wants to get paid. Also, you can't carry the website everywhere with you as you can a book.
Yes, I agree that there would be a financial element behind it, perhaps it could be a contender for the 'Booker' prize at some point.
At least with a website you can still print off pages/sections and take them with you or if you have 'tablet' device you can view it while mobile.
Regards,
Neil
UK
That was my thought. It's easier to update, correct and manage a website than a book.
I'm guessing the writer of the book wants to get paid.
I would expect that he certainly would expect compensation for such a work, be it an online version, a print, version, or both. After all, it would involve a great many hours of work, and would probably need to go through a peer review process and a lot of editing. Even setting it up online for billing purposes, etc. involves both time and money. And then there's the matter of licensing (with Lionel in this case).
Doing a book--however it is published--is an exhausting process that relatively few are able to complete successfully without a whole lot of personal sacrifice.
I would like to be able to access my PDF without having to type a password each time. While I understand why some people choose this route, I find it fairly annoying.
For some reason, I have trouble remembering what information is stored in which component (engine, command base, remote). I always seem to mix things up between TMCC/Legacy and DCS. I think understanding "where things are stored" helps understand how the systems function and aids in figuring out what is going on when there are problems.
Some of my computer books use a "recipe" approach to give an approach to solving a particular problem. This might be a good thing in a book like this. Start with a list of "common" installation scenarios and guide the user step by step as to what they need to do.
I can't see the information being out of date very quickly but it would be nice if people who bought an electronic copy got any corrections in an updated PDF if errors are discovered.
That is why an "online book" via a website would probably be most effective. Updates would be quick and easy.
Maintaining the site though would be imperative. I have also looked into this venue for a Legacy "book". Unfortunately I do not have the time, which is why I have to for go a book (yes I did give it some hard thought) to do it solo.
I also do not own all the components like TPC and such to do the required testing, installation research, and photography that I would deem needed for a complete tutorial.
Access to this requires an OGR Forum Supporting Membership
