Group I started JMRI Decoder Pro to speed match using the speed tables and I was unsuccessful in doing so. After letting the Kato P-42s warm up for 20 minutes I started the process with the first one. After setting the max speed of 100 Scale MPH using a Digitrax 402D throttle I went on setting the rest of the speed tables. What I was going for was Speed step 1 at 1 MPH speed step 7 at 25 MPH speed step 14 at 50 MPH, 21 at 75 MPH, and step 28 at 100 MPH. When using the sliders step 28 was set to (114 the numbers at the to of the slider). As I worked my way down the engine didn't respond well. Setting step 21 to (77 the numbers at the to of the slider) the engine would only run at 36 MPH. As I tried to adjust the sliders to get the proper speeds nothing was correct in adjusting the speeds. Trying to find a work around in sliding the bars down to 0 position and sliding step 21 to 114 also didn't help. The engine would start when 63 was dialed on the throttle at 34 MPH then jump to 102. Has anyone experienced this issue when trying to speed match a locomotive? This was very frustrating and after working on this for 1.75 hours I was done. Looking for any suggestion is this a TCS issue or could the decoder it's self have an issue? Peace be with you, Arthur
Simple question -- Did you remember to click on the "use speed table" button at top of settings page? (Have to ask - but I assume so) I have had hit-and-miss luck with TCS decoder speed matching. Have had a few that have weird bumps in the speed response. Supposedly one can send the decoder back to TCS for a micro-code update to fix. Playing with the Dither controls also seems to help (see below) Here is what I use for my FP40H (same Kato mechanism) CV67 = 4 CV68 = 9 CV69 = 14 CV70 = 19 CV71 = 24 CV72 = 29 CV73 = 34 CV74 = 39 CV75 = 44 CV76 = 49 CV77 = 54 CV78 = 59 CV79 = 64 CV80 = 69 CV81 = 74 CV82 = 79 CV83 = 84 CV84 = 89 CV85 = 94 CV86 = 99 CV87 = 104 CV88 = 109 CV89 = 114 CV90 = 119 CV91 = 124 CV92 = 129 CV93 = 134 CV94 = 140 As you can see, quite linear. Other motor settings Accel 1 Rate (CV3) = 10 Decel 1 Rate (CV4) = 5 Dither Freq (CV56) = 3 Dither Amp (CV57) = 10 BEMF - Enabled BEMF Cutout (CV10) = 0
Rick this is a really great help. First things first LOL the answer to your question is yes I did click the use speed tables. It's a good question because I know some may have forgotten. I will put in the CV you suggested and let you know how it works out. Rick how did you come up with these settings? I'm just curious because I know speed tables take a lot of work and trial and error. Peace be with you, Arthur
One of the things I have found is to not spend too much time trying to fiddle with the numbers. What I do is first find the top speed I want (in my case, the same as you - 100 smph). To do this, I use an Accutrax II speedometer on my testing / programming loop. (I have a separate 3x5' "portable" setup for programming; with lots of toggles to select LokProgrammer / PR3 / CS program track / CS prog-on-main). Then, I find the best minimum speed setting, to get the loco crawling at speed step 1 (normally do this with Vstart and Vmax, first). This is also where I play with TCS dither settings. Very important for the low end, and they do change loco to loco, but not much within brand. I then set these values on the speed table and do a "match ends". Using the throttle, i then test where the loco is on the speedometer at intermediate points. I don't really worry about +/- 5 smph variations, but will tweak the step points up or down as necessary. I have found that Digitrax decoders need the most tweaking, followed by TCS. Lenz, ESU and Zimo have never needed tweaking (all my testing with modern motors). As you can see, for this FP40, I didn't have to tweak at all.
I've encountered issues with TCS decoders having discontinuous speed using the speed table. I wonder if the problem is related to BEMF. Now I use Vmin, Vmid, and Vmax, and declare victory.
