Model Railway Forum

The app has been launched for Android phones.

It's not, as one would expect, called HM7000 but simply HM DCC

I've not tried it yet so can't comment on functionality.

Ian, there are a couple of us on here that have been involved in the ongoing testing of both the iOS and Android versions of the app. The initial iOS launch identified a few issues with compatibility of power sources but that is now fully understood and documented.

While iOS versions worked from day one, a few improvements and fixes were quickly identified (as with most new products) and updates were quickly put in place.
The learnings from this were incorporated in the Android version so that when it was released to the test team about a month ago it just worked - straight from the box and no dramas. As you would expect the testing still threw up a few challenges but the remedies for those have been incorporated in both the Android release and the IOS update applied this week.

There is still work to be done and the system will undoubtedly be refined and expand over time. Personally, I am looking forward to getting my hands on the ‘dongle’ that will allow me to control my non HM7K locos via the app but without buying all new decoders.

I have one niggly glitch (which does not impact on day to day operation) that needs resolving by the clever people on the team but that is no big deal in the overall scheme of things.

What is interesting, for me anyway, is that there have been many people on various railway forums that have been extremely vocal in their criticism of the company and the new system - they have been strangely silent over the last couple of days. Probably too busy chewing on humble pie.

In a nutshell, the system works, it’s not too expensive in relative terms and it will continue to develop. Follow the best practices and recommendations from Hornby and you can’t go wrong.

Hi Steve,

The idea behind both HM DC and HM DCC are quite interesting to me, as some may remember my posts regarding the HM600/HM DC system when it was announced. Well done for getting involved with the testing... if you are able, I and maybe others would be interested in hearing about the processes you've gone through.

Do you know if there have been discussions within Hornby to develop the app for Windows or Mac PC's, giving a whole extra dimension to the usability of the system. Furthermore, do you know if there are plans to produce an API to allow 3rd Party applications to connect to either the HM6000 unit, or the HM7000 decoders?

Would you be able to elaborate on what this niggle you've had is?

It's a shame that Hornby have clarified on using a DC train controller as a power source for HM7000... as that would have fit my use case perfectly.

RAF96 may be better placed to expand on some of the technical aspects of the system as he has been involved in this from the start. I think I was recruited to represent those that just want to plug it in and see it run - which it did.

The system got a lot of bad press as a result of the Sam’s Trains YouTube video where he didn’t read the instructions and used an incompatible PSU (that may have been deliberate). So my approach was to do exactly the same but with a recommended PSU. The result was spectacularly successful in that the loco was programmed and ran without fault at the first attempt.

I then followed a self determined testing regime for basic operation ie do all the sounds work, does it start/stop, does it switch between Bluetooth and DCC operation. Does anything change when you add a second loco and can you switch it to other devices. Anything that looked out of place was reported direct to Hornby resulting in either guidance for the operator where the problem was ‘finger trouble’ (it happened a lot ) or an almost immediate hotfix for the app being sent out if it was needed.
This was repeated as various enhancements, upgrades and new features were released to the test team to confirm functionality.
I know that the more technically gifted members of the team went diving into the details of the app and the functions alongside those working in the lab in Margate. The result is that the app, as released, seems to be very robust and is already vastly improved from the initial iOS version.

On the DC supply question, I think it was more a case of overactive imagination on the part of the marketing dept that came up with the ‘just turn your existing DC controller up to max’ claim. Little did they realise just how many ‘spikey’ supplies there are still in use. Yes they are fine as DC controllers but do not produce a consistent supply to suit modern electronics. The solution is easy though, just use one of Hornby’s recommended PSUs which at only around £50. With the launch of Android, not a single issue (as far as I am aware) has been raised relating to the DC supply so maybe the message got through.

Unfortunately I could elaborate on the niggle but my NDA would mean I would have to shoot you. All I can say is that it is on the to do list for a fix. For that matter so are many of the enhancements being mentioned across the media (including yours possibly) are also on the list for investigation. What must be taken into account is that this is very early in the life of this application for the technology - I know the guys at Hornby are very excited by the possibilities that it offers for development. As the great Arthur Daley once said “ The world is your lobster, my son.”

I will not watch Sams video, and it maybe wise for others to follow suit and stop lining his pocket.

I'd definitely agree that Sam's review/demo of the HM7000 did not do him any favors whatsoever... it was rushed and poorly researched on his part. What he should have done is follow up, get the information correct, and do a new video... but that's beside the point really!

Thanks for the explanation on your involvement. Its great to see this level of user involvement with the testing process. It's common in the IT Development world, so it's refreshing to see Hornby are adopting this attitude as well.

I'll wait to see if RAF96 wants to weigh in on the technical side.

brian1951 wrote: ↑Wed Jun 21, 2023 3:57 pm I will not watch Sams video, and it maybe wise for others to follow suit and stop lining his pocket.

Same here Brian.

I enjoy some of his videos as being a light-hearted look at the hobby. I don't like loco reviews (from anyone) and their associated 'unboxing'.

As for his review of the HM7000 reading the instructions would have helped a great deal.

I'm more interested in how the Android app works though!

Give it a try Ian, I don’t think you will be disappointed. Just be sure to follow the instructions and take note of the best practices.
It’s all documented on the Hornby website and there are lots of sticky threads on the Hornby forum that will lead you through it.

Stese wrote: ↑Wed Jun 21, 2023 1:53 pm Hi Steve,

The idea behind both HM DC and HM DCC are quite interesting to me, as some may remember my posts regarding the HM600/HM DC system when it was announced. Well done for getting involved with the testing... if you are able, I and maybe others would be interested in hearing about the processes you've gone through.

Do you know if there have been discussions within Hornby to develop the app for Windows or Mac PC's, giving a whole extra dimension to the usability of the system. Furthermore, do you know if there are plans to produce an API to allow 3rd Party applications to connect to either the HM6000 unit, or the HM7000 decoders?

Would you be able to elaborate on what this niggle you've had is?

It's a shame that Hornby have clarified on using a DC train controller as a power source for HM7000... as that would have fit my use case perfectly.

Trying to answer your questions as they are presented:
HM6K was a proof of the Bluetooth concept, and if you pull the lid off the modules you can see the track driver is a pair of DCC decoders lashed to a Bluetooth module and the accessory driver is essentially an R8247 PAD again lashed to a Bluetooth module. It worked well enough for the Bluetooth mesh concept to be developed and read across to HM7K and of course the task of getting the Bluetooth functionality onto a standard size decoder.

The original development decoder was a 21-pin monster with the Bluetooth module from HM6K lashed to it. Needless to say although it worked it would never fit in a loco. That was Gen1-Dev. Updatable only by return to works.

Gen2-dev was a more normal sized green board decoder but by way of a Toolbox app it could have the firmware and sound files update at my bench. A great time saver. At the same time the HM7040 dongle made an appearance and it worked straight out of the box - brilliant bit of kit with no limit as to the number of regular decoders that can be assigned to it.

Gen3-dev was essentially the production ready components white board decoder but with ongoing firmware development.
Initially the decoder was proven by DCC then it progressed to the app side. Some difficulty was seen in a reliable mesh but this got ironed out over the course of the basic testing. That decoder then became Gen1-Production.

An expanded test team was now recruited to try the UAT iOS app which once fettled was then released to more or less coincide with the launch of the decoders. The team then went on to wring out the android app which as Steve says had all the fettles for the iOS app wrinkles sorted. Out of the box it was pretty solid. Work continued with improving the sound profile loading to make it Sam-proof.

Next phase of testing is the dongle which now has to be updated to cater for the mesh improvements before it will work properly. That testing will start as soon as the test dongles arrive in country.

Following that work starts on the non-sound decoder range, which due to board architecture is a completely different animal to the TXS decoders.

Windows has been mentioned but to be effective as an app it needs a touch screen monitor and it takes away the portability aspect of the system. Ditto on a Mac. Then there is expanding the app functionality to include the scope of RM, such as operating from a track-plan, running programs and schedules, etc. also a whole range of Bluetooth accessories is being brain-stormed.

Farming out licences or concessions has also been talked about but Hornby is concentrating on getting the product as is established before seeing where external aid would be beneficial. The things I can think off are setting a Bluetooth standard so everyone is singing from the same hymn sheet, then allowing external agencies to fill in the sound profile gaps and add additional compatible accessories or even decoders.

As Steve said with regard to full whack dc power - marketing left hand not properly talking to engineering right hand, but to be fair the quality of this type of power had not been fully assessed for effect although it was known from HM6K that adjusting the PWM frequency did affect decoder operation. It was quickly realised that some controllers could spike up to 400% of max voltage so a blanket ban was introduced, however not before some decoders had been toasted. Hornby now has a better understanding of power supplies in general and work continues to assess controllers as and when the lab can get their hands on them.

I think that covers most of what you added about but feel free to ask for more. Much of the NDA restriction was to keep present testing activity under wraps but now the product is on the streets more can be discussed in the open.