hi all,

i'm about to get my firs piko locomotive, which has a #56405 PIKO SmartDecoder 4.1 Sound PluX22 decoder. amongst the many functions, i was interested in the possibility of a constant braking distance. i read that this can be activated by ABC braking , DC braking (marklin braking module), speed set to zero, and DCC braking signal. i was interested in this last one, but i don't understand if this is something that can be sent with a marklin central station 3 (which i am about to get in place of my actual mobiles station 2), and/or this mode is only available with some pc programs and/or other ways which i don't know. thanks to those willing to give me a hand,

Fab

Hi Fab
I started purchasing a couple of Märklin brake modules but soon realized for a medium-size layout, there is a lot of wiring (3 sections with Märklin), it is not cheap and to handle bi-directional blocks is a pain in the neck.
Then I made my own brake module (using a relay to switch a DC voltage and a car 5W lamp in series to avoid destruction if a loco connects by accident the digital power and the DC power.
Last I used Rocrail (excellent, inexpensive software to manage trains) and using my all-purpose laptop and it gives me this:
- cost 5€ for a CAT5 cable between my CS3 and the laptop plus the facultative contribution to Rocrail
- reduced wiring: no more insulated track section, only track detection zones
- ANY trail can become a shuttle train and still stop at the right place
- any block can be bi-directional without ANY complication
- access to "Fish-bowl" operation (trains travel randomly anywhere permitted)
- access to 'Schedule Operation" (trains travel after a schedule on fixed or relative time)
- manual mode
- all signals are ONLY DECORATIVE so you may start with NO SIGNALS and then install nice signals ONLY where they are visible.
- start with Rocrail is progressive: when starting no checks on block lengths, train lengths, train constrains (electrified section, main line section, remote trunk line, etc), interdictions (goods trains, shuttle trains, etc) and all this can be added WHEN YOU WISH.

Your question "constant braking distance"
- fast trains travel ...fast and brake quickly while goods trains travel slow and brake/ start slowly.
- blocks have often a very variable length and some blocks are bi-directinal

So all this seems like mission impossible but it is not. Here is my solution:
- using Rocrail, each loco has four standard speed set individually: V_min, V_moy, V_route, V_max
- of course freight locos travel much slower than D-trains and a little slower than rail cars (Schinenbüsse)
- a loco speed between blocks is V_route, when it enter a block the V_moy is used and when coming near a red signal, thespeed is zero
- the adjustments on each loco are: maximum speed (resulting in a realistic route speed for that loco) and the inertia (acceleration and braking, set depending on the loco type
- I have standardized a length of deceleration of trains to 18 cm (to go from V_moy to zero and stop a few centimleters before the signal.
- no matter each loco speed and deceleration adjustment, the locos can be set to stop within 1 to 2 cm of the set location
- this is made possible because the slowing down zone of an approching train (variable length because all blocks have not the same length) must slow down from V_route to V_moy and must have finished the deceleration before entering the stop zone

To give an idea of the operations permitted by Rocrail ( or other more expensive train-control software) here is my layout in total automatic mode



Don't get the idea that controlling trains is gone. Quite the opposite, instead of being a loco driver you are a chief dispatcher
Cheers
Jean

You say you are getting a CS3 which is a good move and I would wait until you have this and see the advanages over the mobile staion. I would not consider any software which can cause problems setting it up but rather play with the CS3 first.
Our hobby is about driving trains in my view and although I do have events in the CS3 I prefer to control the locos myself rather that just press a button and watch.
It is a matter of choice to have a computer controlled layout or you are the driver. A mixture can give the best of both worlds.

It depends how you set dec. and what maximal speed set too.
CV4 are for the dec.
CV5 are to set maximal speed.
If you have 1 metres brake section you just set value in both CV4 and CV5.
If you want longer brake secition for example 2 metres then in case you have set higher value in both CV adress.
I don´t like Pikos decoder and i prefer to use ESU and Zimo decoder with ABC brake.
ABC brake are cheaper too than use Märklins expensive brake module.

Edited by user 14 June 2024 08:16:19(UTC)  | Reason: correct number CV5

Hi Fab
I learned the hard way that changing detection zones on lower levels of track is very painful and the quality of work is inferior so I think, now that you are at the lower level, it is time to install the detection zones before covering the tracks with upper levels (I have 3 levels of tracks total). Testing your work is an absolute must.

First is a Rocrail page (here in English but you may get the same in Italian by replacing "en" with "it" at the end of the pathname.
Sensors and blocks with Rocrail - WIKI Page

Here are a few tips (If I may) when using Märklin C Track:
- you must select your priority: EITHER precision of stopping and security--> you need 2 sensors per mon-direction blocks and 3 sensors for bi-directional ones OR you select to minimize the number of sensors, then you may use one senor per block mono-directional or bi-directional BUT this is detrimental to the precision of stopping (you need blocks that are roughly twice the length of a train and also detrimental to the security because less zones will be under supervision. This choice is also reflected by a different deceleration adjustment on locos
- in each block, standardize the length of the IN detection: I use 20 to 22 cm. This allows any loco to go from V_moy to V0 (stop). That way you adjust all you locos on ONE block and this is good for all others.
- if you choose a one sensor per block approach then remember that only the central section is detected (otherwise train will stop far away from the signal and possibly not clearing the previous turnouts.
- C track turnouts may be tricky to insulate (for occupancy detection) so you may skip that part without jeopardizing the operation safety.
- using Märklin C Track insulators is fine BUT (1) make sure of the condition of the 74030 red isulator and (2) make sure that the facing rails over the insulator are not touching each other (a 0.5 mm clearance is recommended). Remember that when aging C-Track plastic retracts while the rails do not, resulting in phantom contacts.
- mark the rails where the insulation is made (I use a small bar of acrylic color and where the screws are used. Use a small number of them because when intervening for repairs on lower levels, accessibility is very poor (use a small mirror and a light).
- another method is to cut one of the rails using a hand drill (Proxxon / Dremel) and a diamond disk. Works very fine, can be reverted later BUT the rail must be thouroughly cleaned of stainless steel dust (Phantom contacts)
- always leave a little loop of connecting cable so that you may work on it later (remember turnouts will fail over the years
- avoid ABSOLUTELY using C-Track contact tracks like the 24994 as they are expensive, not very reliable and stop trains at slow speed (slider tacks off)

Cheers
Jean