JohnP1707822380

I have had a response from Hornby Technical Services regarding short circuit protection when a P9100 PSU is wired directly to the track to power a HM7000 system (raised earlier in this thread). "The P9100 power supply is specifically designed to deal with any short-circuits to ensure that your decoders are not damaged. If a short occurs, a simple reset of the mains power will have the Bluetooth system come back online within 10 seconds."

I have a couple of questions regarding wiring a PSU directly to the track to power a HM7000 system. Firstly, my current 3/4 circuit DC layout is controlled by two HM6000 units, each with its own P9100 15V 1A PSU. If I upgraded to HM DCC, could I wire the two P9100 units in parallel directly to the track to create a 15V 2A power supply? If so, how would the load be distributed? Secondly, irrespective of the number of PSUs wired to the track, what protection is there against short circuits? As I understand it, if the App can detect a short circuit it can only cut power to the locos, not from the PSU. Do P9100 PSUs have some form of internal cut out to protect against short circuits? In a DC system, this would normally be incorporated in the controller.

@96RAF Thank you for pursuing this for me - it's good to know that these things are being looked at.

Request for Improvement I have an 8' x 4' DC layout with 3 independent circuits controlled by 2 HM6000 units (with no HM6010 units). I operate the layout from either an ipad mini 3 running ios 12.5.5; or an iphone 7 running ios 15.5. The App software is v1.2 (B61r1). I like the system, particularly its graphical display/controls and the freedom it provides to walk around and operate locos without wires attached to the layout. However, there are a couple of areas which could benefit from improvement. When operating the layout under mesh connectivity, the response of locos to App controls (speed slider, stop button) is much slower on the circuits allocated to the non-host HM6000 unit than those allocated to the host unit. In the former case, there is a material delay before the loco responds to a change in control, to the extent that actions to slow and stop a loco need to be taken much earlier on these "non-host" circuits. This is not the case when operating with BLE connectivity, which I am sticking with for now - although I appreciate that I will need to switch to mesh to install any firmware updates.The process of un-provisioning units connected under mesh (e.g. to switch devices) can be cumbersome - generally I have to do a forced delete and factory reset. Maybe as a result of this, I now seem to have lost the unique 4 digit -#### number assigned to a HM6000 unit when scanning with mesh connectivity (they are both labelled on the App as simply HM6000) - would reinstalling the App on my devices cure this? Also, on occasions, I have ended up (under mesh) with both HM6000 units shown on the App controlling the same physical HM6000 unit.