Auto Calibration Observations

[Rallymatt]

The power of DCC means almost anything is adjustable and the HM DCC app makes changes so accessible. As my latest TT:120 Silver King seems to be nicely run in now I thought I would see how much smoother I could get running across the speed ranges. 

Manual covers this really well with exception of a missing power cycle after setting CV149 to 0 but by now if you are do this stuff you know it’s needed. All went well and it’s just tidied up smoothness. No need to go further. 

My Piko BR130 is on a Next18 HM DCC decoder so thought I would give it a tune up too. Just as straight forward, reset CVs via CV8, follow the process, but surprisingly loco ran worse! Ok it was pretty near spot on as was but I didn’t expect that. I tried again, no difference and altering CV150, 151 or 152 as in stage 2 didn’t do a thing, absolutely nothing. I simply reset it via CV8 and made my speed values realistic again and it’s back to very good. I haven’t ventured into the PID values, Not sure it could justify the effort. It’s pretty reassuring though that any changes are easily reversible. 

I would certainly recommend doing an auto calibration and see if it adds anything to the performance

[96RAF]

Although auto-cal is working fine on DCC direct there is a slight glitch in the app such that CV149 is not being written back to value 2 after the event. This is being fettled.

It is worth noting that a power cycle is always worth doing after fiddling with anything in the app along with a CV refresh. This puts the decoders ducks in line with those of the app. A bit like having to restart your PC after a new installation or update.

[Rallymatt]

Rob, it does seem to be a smart thing to power cycle after any ‘event’ to get changes to ‘stick’

What you said about CV149 Not automatically reverting to value 2; would that be why when I tried to change values in 150, 151 and 152, I saw no change?

[96RAF]

Possibly.

Changes to CVs in the app do not seem to stick when they should read across to the decoder and any changes made under DCC control should synch back with the app but this doesn’t always happen. It is being worked.

The sound profile load system is also being made more robust. The team has spent a lot of time endlessly loading and reloading all the profiles in the listings. Only one is proving a tad troublesome, but that will be fettled in time.

[Rallymatt]

Hats off the people behind the scenes, I’m still convinced there is an element of witchcraft and eye of newt involved 🤣

[Fishmanoz]

And the witch is preferably one with a blue tooth.

[96RAF]

Definitely Fishy, but the recipe is working. Loading of sound profiles is almost bombproof, but the current install time of around 15-30 minutes may niggle folk. Never mind it fills one’s day waiting for it to happen time after time, the joys of testing innovation.

[Grenkin]

On 13/05/2023 at 13:04, 96RAF said:

Although auto-cal is working fine on DCC direct there is a slight glitch in the app such that CV149 is not being written back to value 2 after the event. This is being fettled.

It is worth noting that a power cycle is always worth doing after fiddling with anything in the app along with a CV refresh. This puts the decoders ducks in line with those of the app. A bit like having to restart your PC after a new installation or update.

Was trying to do calibration on TT Duchess and after it makes short fast run I cannot change CV149 back to 2, what to do in this case?

[Too Tall]

On 18/05/2023 at 10:02, 96RAF said:

Definitely Fishy, but the recipe is working. Loading of sound profiles is almost bombproof, but the current install time of around 15-30 minutes may niggle folk. Never mind it fills one’s day waiting for it to happen time after time, the joys of testing innovation.

On the ones being beta tested I assume ?

ATM far from that for me, granted I am using a very old galaxy (android) tablet, but falling over at updating spirom is a common occurrence for me (100% either error or app crash).  After 3 or 4 attempts we will get there, and then await around an hour to load. If the updated system is bombproof and 15-30 mins, its a big step forward 🙂

Edited July 25 by Too Tall

[LTSR_NSE]

@Too Tall your choice of device (along with quality of internet connection) have a significant impact on speed & reliability of profile loading.

The timings that you quote & comment on are what the app is currently perfectly capable of - provided device/internet allow!

You may not wish to hear/read this, but I cannot imagine app development that becomes less resource-hungry over time - the opposite is virtually guaranteed.

Hornby stated at launch that the app should work with most devices up to 5yrs old (if some older devices are also compatible, that is merely short-term fortune, it shouldn’t be relied upon, expected to remain the case & certainly not going to be improved/increased!)

App development is under continual progression therefore the approximate 5yr window of recommended devices keeps moving in real-time too.

[Too Tall]

Yes its a given, I do have a modern tablet for my TT120 stuff, (although that still isn't flawless) but Primarily the OO is only set up on the app on the old tablet then will be controlled via an ACE3.

As per Rallymatt's conclusion, I tend not to bother messing to much with CV's unless something is amiss, I find I just tweak the accel/decel a bit via the easy app interface then call it a day !

[96RAF]

18 hours ago, Grenkin said:

Was trying to do calibration on TT Duchess and after it makes short fast run I cannot change CV149 back to 2, what to do in this case?

After auto-cal the software sets various CVs values and these should not be changed. Auto-cal should set CV149 value as part of that procedure. Refresh the C~vs in the editor and check it updates .

[Rallymatt]

The manual is now saying to ‘manually reset CV149 to 2’ although I have had success just on doing the CV refresh and power cycle.