h0ughy
20-03-2007, 07:19 AM
Yes thats right, 2 hours after setting everything up for the first time to test before SPSP, I then decided to upgrade the firmware - well:
everything started OK, did the 0-8 boot sequence and then connected and found the controller and the V2.6 updater program started to update the controller with 3.12, then I went and did something for 10 minutes.
Upon my return the updater program said the controller communications had failed. Upon inspection I noticed the controller wasn't on. Then checked the leads and supply - everything ok. Just to make doubly sure I went and got my other v3 controller, the mount powered up and worked. Then I tried the controller again - dead as a dodo.
I will be begging tasco today for a quick repair, as SPSP is not far away.
everything started OK, did the 0-8 boot sequence and then connected and found the controller and the V2.6 updater program started to update the controller with 3.12, then I went and did something for 10 minutes.
Upon my return the updater program said the controller communications had failed. Upon inspection I noticed the controller wasn't on. Then checked the leads and supply - everything ok. Just to make doubly sure I went and got my other v3 controller, the mount powered up and worked. Then I tried the controller again - dead as a dodo.
I will be begging tasco today for a quick repair, as SPSP is not far away.