Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by jpendle

  1. Hi, FWIW, my N Gauge locos with Zimo decoders have curves that look like your Lenz decoders. The only difference that I can think of is that I don't set CV6, I leave it as the Zimo default (1), I then have CV2 set to around 20 and CV5 set to around 120. (This is for N Gauge Diesels). I did try using CV57 instead and didn't get good results. Regards, John P
  2. Hi, FWIW I was using Wine to run the Roco Z21 maintenance app on my Mac Mini, but after an upgrade to the latest OS wine was no longer available. I went for the cheapest Crossover option and it works, but IMHO it's not as intuitive as Wine was. Regards, John P
  3. I model N Gauge, so shipping costs may make a difference, but in my experience there is almost nothing British Outline that I can buy over here that I can't get cheaper from UK suppliers. Regards, John P
  4. Yes, it's uses fuel made from used vegetable oil. Regards, John P
  5. There are a number of ways that this could be done, depends how much money you want to spend. One simple way would be to add a double pole double throw switch and connect the wires from the signals to this, wired such that in each position just one of the BM1 modules is active. You could also use occupancy detectors either side of the platform and use them to control relays, or a simple logic circuit, to turn on the correct ABC module when its signal is red. Regards, John P
  6. Hi, CV's 124 and 156 let you turn momentum off, i.e. the decoder ignores what's in CV's 3 & 4. So if you set CV156 to 2 then pressing F2 will turn momentum off and any speed change that gets sent to the loco happens immediately. I would set CV's 124 and 156 back to 0 and start again. Now I have never done this myself so I may get this wrong. First set CV4 to 50, this would mean that the loco would take 45 seconds to slow down from top speed to a complete halt. Then set CV309 to 2 and CV349 to 5. Now if you run the loco at max speed and then set the speed to 0, it should coast for 45 seconds, if you press F2, then the loco should brake harder. If you keep F2 activated then it should stop in around 4.5 seconds. Oh, what DCC system are you using? Hope that helps. Regards, John P
  7. Yeah, K-type Pullmans and 38 tube stock. Oh, sorry, wrong thread. John P
  8. Hi, CV7 = 0037 so that is version 37.nn, the subversion (the numbers after the decimal point) are read from CV65. So your decoder is at a higher version than 33.23. The default values of CV's 309 and 349 are 0, and the default value of CV4 is 1. All these CV's will need to be adjusted to get the a brake key to work. When you say what do you mean? Regards, John P
  9. Hi Iain, This is slightly off topic but the whole "Direct Control" thing in the iTrain manuals has been bugging me for a while. I cannot find any mention in the Zimo manuals of a Direct Control feature, so how have you got this to work? I've been setting CV's 3 & 4 to 0 for my speed measurements. Thanks, John P
  10. I have removed the springs from all my Peco Code 55 Streamline points so that they work with my Tortoise motors, similar to the Cobalts. Tis also means that you get slow movement of the point blades, BUT you must connect the point frog to one of the accessory switches on the Cobalt because without the spring blade contact will be unreliable.. Regards, John P
  11. Hi Robert, I think that there may be more then just revision 40.5 coming into play here. So first , mea culpa, I got my reply wrong in your other post. I am running revision 40.1 on all my profiled locos and have experienced no issues. Second, and I think this is very relevant to what you are seeing, I found a significant speed difference between decoders running revision 31.5 and those running 37.8. I was trying to double head two identical N Gauge locos, one had an MX622N at rev 31.5 and the other had an MX617N at rev 37.8. The loco with the MX617N ran almost twice as fast as the one with the MX622N. After upgrading the MX622N to 37.8 it's loco ran at almost the same speed as the MX17N equipped one. So as you say that the MX634's were at 36.5, it may be that upgrading them to 37.8 (or higher) has had the same effect that I saw on my MX622N decoders. I was never able to determine which specific firmware revision was responsible for changing the speed characteristics on my decoders. I can also try upgrading one of my decoders from 40.1 to 40.5 to see if it has any material effect on its speed performance. BTW, were you able to get your locos to run properly once they had been re-profiled, it seemed like you were still having issues, at the end of your other thread? Regards, John P
  12. A little bit of thread drift. SP's internal phone network was so good that they started to compete with AT&T to offer long distance calling in the US. Eventually SPRINT (Southern Pacific Railroad Internal Networking Telephony) was sold off (to GTE) and became a stand alone long distance and mobile phone company. Regards, John P
  13. The Kirkby line has been singled from Rainford, and the MerseyRail bit is single to Fazackerley. Regards, John P
  14. A wild guess. There appears to have been a mineral line that ran behind North Manchester General (Crumpsall) Hospital. It has a couple of overbridges according to the NLS map site. Regards, John P
  15. I am definitely no expert on OHLE, but wouldn't a neutral section be a bit problematic for eastbound trains, having stopped at Wallgate and then having to climb the gradient after the bridge? I assumed that electrics coasted through neutral sections? John P
  16. Yes, it is a bit of a squeeze! I would have thought that the only option to get wires to Wallgate would be to lower the track bed, but then that'd mean even more of a gradient to get in and out. Raising the bridge would presumably entail demolishing every property in the terrace that sits on top of it on the East side. Regards, John P
  17. What puzzles me is given that most services on this line run through Wallgate, what's the benefit of electrification of the line? Would this be considered a diversionary route if the line between Lostock Junction and Preston were blocked? But more electrification is a good thing. Regards, John P
  18. Hi Arthur, If it helps the Zimo small decoder manual has recommended CV values for coreless motors. Regards, John P
  19. Yes it does. The firmware upgrades are always enhancements and bug fixes. I've not seen any that are directly related to other DCC systems/controllers. Although they describe the enhancements in detail, they usually don't explain what bugs have been fixed. Regards, John P
  20. The Z21 will update any Zimo decoder. Here's the secret sauce Make sure that CV144 is set to 0 and that DC running is OFF in CV29. Then in the maintenance app, instead of pressing the update button, press Ctrl + Alt + Z. I have tried this and it does work, the original document, that is on RMEB somewhere, came from a Zimo employee. Regards, John P
  21. FWIW I have updated all my locos at least twice now and as far as I can tell it has not introduced any issues. As I said in my earlier post going from 31.5 to 37.8 changed the speed of locos that had been upgraded. BUT this was a good thing as two otherwise identical locos would run at different speeds depending on the firmware revision of the installed decoder. This made double heading problematic. What do the Traincontroller speed profiles look like? Regards, John P
  22. Not me, but. All my loco's have Zimo decoders. I also use a Z21 and have been upgrading the firmware in my decoders on an occasional basis. I discovered by accident that something changed from earlier versions of firmware, an N Gauge loco with an MX622N ran over twice as fast after upgrading the firmware from 31.5 to 37.8, I never found out what Zimo had done to make this happen. So I would expect that a loco could well run at different speeds depending on the brand of decoder fitted. One other thing I've noticed is that with CV5 set to 1(255) ,which is the default, all my locos max out at about speed step 70 and then exhibit very erratic speeds up to SS128. As a result I've had to set CV5 to around 120 to get a reasonable response from the decoders between SS1 to SS128. I use iTrain not Traincontroller, which I hope isn't relevant, but with CV2 set to 20 and CV5 set to around 120 I have not seen any speed profile issues with any of my Zimo equipped locos, other than those which could be attributed to the locos actually getting run in properly, at last I am also running all my locos at revision 40.5. Hope some of that helps. Regards, John P
  23. Is that a typo? DCC surely. John P
  24. My son did that to his PC. I didn't realise that we were friends John P
  • Create New...