hans_van de burgt Posted February 11, 2016 Share Posted February 11, 2016 I want to shunt in exact distance. When I run a loc from 0 to 1 sec, I mark the distance. I repeat this from 0 to 2 sec, from 0 to 3 sec etc. The delay functions on the decoder are set to zero. The results are very unexpected. There seemed to be no logical relation between time and distance. The only way to set a program is by trial and error. When possible I want to use this sort of exact distance operating for an Inglenook Sidings Railpuzzel. What do I wrong? Link to comment Share on other sites More sharing options...
96RAF Posted February 12, 2016 Share Posted February 12, 2016 I don't think you are doing anything wrong. It is the way RM works - time not distance until we get the loco detection system.. Their answer is to bash the buffers to provide the program with a known starting point, which takes away the variable you are seeing when you try to stop in the same place each time. The Hornby decoder that supports asymmetric DCC and programmable actions (Sapphire) also works on time not distance. the equivalent Lenz decoders (silver & gold) work on ADCC by distance, so may be better for what you want, although I don't know of a way to incorporate this into an RM program. ADCC works by way of a 5-diode module biasing the DCC signal to either slow or stop a loco in an isolated section. This can be set for both directions or only one way. To restart you de-isolate the section. you can read about it on Lenz website under ADCC. The basic BM1 equivalent module is easy to make. Link to comment Share on other sites More sharing options...
Fozzy Bear Posted February 13, 2016 Share Posted February 13, 2016 You will never get it right. I have tried to write programs to get engines to enter my turntable, rotate and head off to do stuff then return but since the engine never stops in exactly the same place, the only way was to fit balsa wood stops on the oppposite sides of the TT to make the engine stop exactly. And this only worked with engines with no front coupler!The RM programming works well but there are just too many variables with the engine such as age, cleanliness of tracks and wheels, supply voltage and basically the mood that the engine is in. It might work 9 times in a row but the 10th time, the engine will stop short and snag on the TT tracks. Same with just getting it to stop at a station. Works ok then it will overrun or stop short. If the program repeats, the error just gets larger and larger. Link to comment Share on other sites More sharing options...
St1ngr4y Posted February 13, 2016 Share Posted February 13, 2016 You will never get it right. I have tried to write programs to get engines to enter my turntable, rotate and head off to do stuff then return but since the engine never stops in exactly the same place, the only way was to fit balsa wood stops on the oppposite sides of the TT to make the engine stop exactly. And this only worked with engines with no front coupler!The RM programming works well but there are just too many variables with the engine such as age, cleanliness of tracks and wheels, supply voltage and basically the mood that the engine is in. It might work 9 times in a row but the 10th time, the engine will stop short and snag on the TT tracks. Same with just getting it to stop at a station. Works ok then it will overrun or stop short. If the program repeats, the error just gets larger and larger.Do you use the loco's acceleration/deceleration CV's or do you use the accelerate and decelerate program commands?Ray Link to comment Share on other sites More sharing options...
Fozzy Bear Posted February 14, 2016 Share Posted February 14, 2016 Just shunt ,cruise and stop commands. It appears the stop command is the culprit. Sometimes it works when it is supposed to and other times, the engine just keeps going for a bit longer. Link to comment Share on other sites More sharing options...
96RAF Posted February 14, 2016 Share Posted February 14, 2016 Have you got 'controlled stops' ticked in setup. Link to comment Share on other sites More sharing options...
Peter Ruifrok Posted February 14, 2016 Share Posted February 14, 2016 How does that make a difference? I am personally using the CVs for a more natural start and stop (I made CV3=25 and CV4=10 while both come from the factury with a value of 2). So I am wondering now what is better? To use the CVs or to use railmaster. And what is the difference between ticking the box or not? Interesting subject, not only for shunting but for stopping anyway. Link to comment Share on other sites More sharing options...
St1ngr4y Posted February 14, 2016 Share Posted February 14, 2016 If you use the decelerate command in a Railmaster program, it will send a speed command to the loco every second (the default interval but variable), so if one of these commands is missed for any reason, it doesn't make too much difference. With a stop command, sometimes it is missed by the loco or obeyed a second or two too late, which makes a significant difference to where the loco stops. Why not give the accelerate/decelerate commands a try. You can achieve superb realistic control with a little tweaking of the commands here and there.Ray Link to comment Share on other sites More sharing options...
96RAF Posted February 14, 2016 Share Posted February 14, 2016 How does that make a difference? The loco either stops according to the CV decell value setting or it stops dead. Link to comment Share on other sites More sharing options...
Michael_A Posted February 14, 2016 Share Posted February 14, 2016 The manual says use the slider to stop the train, not the stop command, I guess for just that reason. Thank goodness comms on airlines is more reliable, eh? :) Link to comment Share on other sites More sharing options...
Fishmanoz Posted February 14, 2016 Share Posted February 14, 2016 Have you ever seen how long it takes the pilot to plug his laptop into the plane and get it recognised by the Airmaster program? Link to comment Share on other sites More sharing options...
Peter Ruifrok Posted February 14, 2016 Share Posted February 14, 2016 I will give the decelerate command a try. Sounds good Link to comment Share on other sites More sharing options...
hans_van de burgt Posted February 17, 2016 Author Share Posted February 17, 2016 Well, I changed the decoder to a Lenz one. At the end I succeed in calibrating the shunting behaviour. With a shunting speed of 5 Km/hr, the loc is moving exact 5cm in 10 sec. (10cm in 20 sec etc).Now I have to calibrate the Kadee couplers.Is it possible to program "forward 10" km/hr. or "reverse 20" km/hr.?Grzz, Hans Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.