Jump to content

Britannia Builder

Members
  • Posts

    348
  • Joined

Posts posted by Britannia Builder

  1. I installed my 4th 8-TXS decoder today, in a Hornby Black 5 which previously had factory-fitted TTS. I installed the Black 5 profile successfully. I didn't install a power bank, since it has pickups on loco and tender and never lost power with TTS. The sounds work fine under bluetooth, but when I set the loco moving it stops after a few seconds and the sounds also stop. The bluetooth light on the app remained blue, so it hadn't lost power. Cycling the track power restored the sound but the same problem occurred as soon as the loco started to move. It all appears (at least on cursory testing) to work fine under Railmaster/DCC.

    I think I've seen this problem reported more than once before on this forum, but I don't recall seeing a solution. Do I need to send the decoder back for a replacement?

    Regards, John

  2. Thanks Paul.

    I looked at the Windows antivirus log and the reason it gave for blocking the exe file was that it contained 'HackTool:Win32/RemoteAdmin!MTB'. I guess that this is the software that HMRS use when logging in remotely to do diagnostics. 'HackTool' is presumably the virus checker's view of the thing, rather than part of the name! I hadn't realised that HMRS installed this as part of RailMaster, and frankly I'd rather that they didn't. I wouldn't knowingly let them or anyone else log in remotely to my computer.

    Regards, John

  3. Prompted by this thread, I checked my RM version number and found that I was still on 1.72.0! I thought RM was meant to update automatically, at least for major updates?

    I then went through an incredible palaver to do the update - the HMRS link didn't seem to do anything, so I tried the backup MEGA site and eventually after turning off virus checking in Windows Defender and turning off safe browsing in Chrome and overriding security warnings I was able to download the installer and do the update.

    I can't say that I noticed any difference!

    Regards, John

  4. Do you have power banks installed? I'm wondering if the inrush of current to the power bank when the loco first starts moving is upsetting things. If so, you could try installing the Tornado profile which charges the power bank before the loco starts moving.

    Regards, John

  5. All fixed now. I tried reading out all the CVs on the programming track under Railmaster, but there's no easy way of updating them again as RM will only update CVs that have been manually changed.

    However, having read the CVs into the app and reset CV8 to 8 (which fixed the DCC communication problem as expected), it's quite easy to scroll through the CVs in the app, tap on each one that needs updating, and press exit in the CV value screen without changing anything. It only took a few minutes to reset AFC sounds, complex speed curve etc, then re-run auto calibration.

    There's obviously still an underlying bug somewhere that needs fixing, but I can't think what combination of events causes the loss of communication. It's only ever affected one of my three TXS locos.

    Regards, John

  6. Can I put in a vote for a DMU sound profile too - I have a Hornby 3 car Class 101, currently running the Class 31 profile. This sounds OK - it's 60 years since I used to commute to school on Class 101s, so I can't really remember what they sound like - just remember the diesel fumes and the vibration!

    Regards, John

  7. I've just had this problem again, 3 months after it last happened (see my post from 22 May above). I had done lots of CV updating via the app to set a complex speed curve, then reverted to Railmaster and tinkered with the speed factor to get the scale speed realistic again, then was running the loco quite happily under Railmaster/DCC when it suddenly lost control when running at full speed.

    I'd been half hoping that this would happen again because I had a theory that CV1, the DCC address, might be corrupted, but I read all the CVs back from the decoder into the app and sadly they all look fine. I've tried power cycling the decoder, and restarting Railmaster.

    The next step which will hopefully fix it is to reset CV8 to 8, but this will lose all my CV changes including the complex speed curve. I don't suppose that there is any way of backing up the CV settings and restoring them after the reset?

    Regards, John

  8. Thanks Rob.

    The APROM version is in CVs 47-49 and the SPIROM version is in CVs 202-203, but I can't see a combined version number.

    Interestingly the APROM version in my charge-when-stationary Tornado is 0.0.5, the same as my other two TXS decoders which were installed a couple of months ago, so perhaps the new charging feature is not in the APROM?

    Regards, John

  9. Thanks Steve and Rob.

    When a new version of a profile is released for this or any other reason, will it be possible to update just the APROM code and SPIROM sounds without overwriting all the CVs and functions that have previously been amended by the user? I imagine that this charge-when-stationary feature is a change to the APROM code rather than a feature of the sound file - will it just download the small APROM file if the SPIROM is unchanged? And is the APROM actually different for all the different sound profiles?

    Regards, John

  10. How will we know when existing profiles have been updated to include the charging when stationary? I have a Bachmann 3MT Tank which needs it - I'm currently running the Black 5 profile, but I would switch to another similar profile if it got the update earlier.

    Regards, John

  11. I would say that my Tornado is making between 5.5 and 6.5 chuffs per revolution at low speeds. I guess that is about as accurate as can be expected without sensor hardware to synchronise the chuffs precisely to the revolutions.

    Each cylinder will make two chuffs per revolution, so 4 chuffs for a 2 cylinder and 6 for a 3 cylinder. I believe that 4 cylinder locos such as a Duchess have the cylinders synchronised in pairs, so 4 (double) chuffs per revolution.

    Incidentally I had run the auto calibration on my Tornado before setting up the speed curve. I don't know if this would affect the result - ie will auto calibration change the mapping between speed steps and motor speed?

    Regards, John

  12. I've set up the 3 cylinder speed curve from Rob's post above (5, 6 .... 125, 140) for my Peppercorn A1 with the Tornado profile, and it works very well - 6 chuffs per revolution from the slowest to as fast as I can make them out, and a realistic top speed.

    I didn't note down the default CV values in the Tornado profile before changing them, but they were nearly twice the above values and the chuffing was way too slow at all but the slowest speed, and the top speed was dangerously high!

    I'll try my Bachmann BR Standard 3MT Tank next with the 2/4 cylinder values above, and/or LuLuJo's alternatives.

    Regards, John


  13. That's interesting, and a good enhancement. I downloaded the Tornado profile yesterday and I can confirm that its power bank does now charge when stationary.

    You say that this is the default - is there a way of turning it off? The only reasons that I could think of for turning it off would be prior to a profile download to speed up the power cycling (which takes a long time on my Tornado, even with the sounds playing, which they won't be during a download), and to allow conventional CV updating on a programming track. But now that the app allows the complex speed curve CVs to be set up, I can't see much reason for doing the latter.

    Regards, John

  14. I had this problem twice, over a month ago now, and recovered by setting CV8 to 8. This is inconvenient because all CV changes then have to be reapplied.

    If it does happen again, I shall refresh all the CVs in the app from the decoder and try to see what's changed. I suspect that the DCC address will have been corrupted, since I can't think of any other CV changes which would render the decoder incommunicado.

    Regards, John

  15. I tried both random and sequential when trying to get F9 to sound, but it made no difference.

    I guess most looped sounds are quite short before they repeat. They seem to run for about 10 seconds under AFC, so plenty of gap before the next sound which is typically at an interval of 20-30 seconds.

    If AFC looped sounds work as they appear to, it might be worth updating the decoder manual to say how they work rather than advising against using them.

    Regards, John

×
  • Create New...