Open pabender opened 2 years ago
From an operational perspective, the consistent use of code 55 was more important when joiner rails were used between modules. With butt end connections between modules, this concern is eliminated. Simple matched rail head height works.
Suggest restructuring section 2 (goal is clarity) with: S2.0 Rail & Track S2.1 Rail S2.1.1 All rail shall provide clearance for NMRA Standard wheels between rail head and track spikes, tie plates and ties. S2.1.2 Mainline track shall have Code-55 nickle-silver rail. S2.1.3 Non-mainline track shall have Code-55 or lighter nickle-silver rail. S2.1.4 All rails shall join with the top and inside of rail head flush to one another. S2.2 All Track...
I like the direction of Steve's clarifications. How can we say the same thing in less words?
Code 40 rail soldered to PCB ties, gives roughly the equivalent flange clearance of Code 55 flex. From that perspective I don’t see a problem with Code 40. Could phrase the standard something like “Main line rail shall be code 55 or smaller. If smaller, it shall need to accommodate the same flange depth as Code 55 flex”
As a FAQ entry: “Free-moN track should look prototypical, but also work reliably. Seeing Code 85 rail in N scale, looks “Too big” and distracts from the realism. Even Code 55 is large, for some rail - but we need properly functioning track for all locos/cars so it’s a compromise. Code 40 track soldered to PCB ties does provide a similar wheel flange clearance to Code 55 flex, so that’s an option for the advanced modeler - but for most, Code 55 flex is the safe bet.”
The language in the standard is ambiguous with regard to rail code. At least one module builder has interpreted the standard as saying hand laid code 40 rail is allowed on the mainline.
also there is a question as to whether the standard specifically forbids larger rail sizes on non-through routes.