@dan issue persists with 1.0.3

@sandipg The voltage and capacity are OK but it's the wrong connector, you want a JST PH-2 (also check the polarity as there is no standard) For Germany perhaps check out these two from HobbyKing: (the higher capacity 2000mAh is cheaper as it's on sale, but see dimensions etc) https://hobbyking.com/de_de/turnigy-2000mah-1s-1c-lipoly-w-2-pin-jst-ph-connector.html https://hobbyking.com/de_de/turnigy-1200mah-1s-1c-lipoly-w-2-pin-jst-ph-connector.html

Every update seems to be different. This time, the PyTrack was detected as a COM device. With the same number as before :). But I was not able to connect. To fix it, I had to select show unconnected devices in the device manager, browsed for the usk driver and deleted the unknown and unconnected device.

@jcaron Thanks for the tip. Output below. from pytrack import Pytrack py = Pytrack() py.read_fw_version() 4 Which I think means it had flashed successfully (partly as my previously loaded libs had disappeared!). I had tried to connect the External I/O header as an alternative but had similar lack of luck. Tried High speed transfer both ticked and unticked based on reading another similar post. Just tried this again with same result. Flash tool states it is connecting... then shows a Failure! warning. The only COM port in the drop down is COM3 but I am not sure that's the attached PyTrack as removing the PyTrack from USB doesn't de-list the item listed in Device Manager. I am still concerned that it is more related to not having the correct Windows drivers in place that's preventing things from working as they should. Thanks again for the response. Regards Shaun