|
|
Post by Uncle De4dly (Ian) on Nov 5, 2018 23:44:13 GMT
I seem to be hooped here.
I installed drivers onto my Windows 10 VM (I run Mac) and plugged in the TX. Went through calibration and all seemed well. What I did wrong at this point was that I screwed around putting the wheel into firmware update mode and went through a bunch of plugging and unplugging that didn't follow the procedure.
Now I'm following the procedure but the firmware update utility won't recognize the wheel. I can confirm that the hardware is being recognized but the windows 10 driver is giving errors - I've reloaded it several times. The driver says 'device cannot start' and driver status shows - This device cannot start. (Code 10)
{Device Timeout}
The specified I/O operation on %hs was not completed before the time-out period expired.
I've called tech support and they're useless. Next step is to send screen shots unless somebody here is more windows savvy than I. I've run the install program in compatibility mode just for shits and giggles to no avail.
|
|
|
|
Post by XRF HammerPH on Nov 6, 2018 10:48:31 GMT
That sucks mate. Have you had any luck sorting this out since last night? Have you tried uninstalling the drivers/software from the PC and then going through the whole procedure from scratch? Does the Xbox still recognise the wheel or is it completely hosed in that respect?
|
|
|
|
Post by XRF HammerPH on Nov 6, 2018 10:51:32 GMT
|
|
|
|
Post by Uncle De4dly (Ian) on Nov 7, 2018 16:43:00 GMT
Yep - I've been into it all pretty deeply. What occurred here is I interrupted the firmware update process. Firmware is of course low level code dealing with I/O and if the process is interrupted resulting in the firmware being partially loaded / cleared, the device can become 'bricked', which is what's happened to me.
The windows driver loads when the device is connected and starts the calibration process, if there's no feedback from the wheel moving the driver will fault.
This can happen with any electronic device btw. There are ways to get into the circuit board apparently and reset the chip I supposed, but the wheel is new and I'd be better to just return it for a refund.
Amazon will issue a refund and I'm working on sourcing a replacement. There's a couple used in Vancouver that I'm trying to sort out pickup for Friday, otherwise I'll have to order a new one from Walmart or Amazon appear to be the best prices and it'll take a week or so.
So I'm out of action for a bit but will be back soon. Lol - sad how upset and missing this I've been without it already. I was just getting going! Will be on the grid soon.....
|
|
|
|
Post by XRF HammerPH on Nov 7, 2018 17:52:40 GMT
That's crap buddy, sorry to hear that and I hope you can get back up and running again quickly.
Keep up with things here and we'll be sure to keep an eye out for when you are ready to go again.
|
|
|
|
Post by XRF HammerPH on Nov 15, 2018 9:44:46 GMT
Yep - I've been into it all pretty deeply. What occurred here is I interrupted the firmware update process. Firmware is of course low level code dealing with I/O and if the process is interrupted resulting in the firmware being partially loaded / cleared, the device can become 'bricked', which is what's happened to me. The windows driver loads when the device is connected and starts the calibration process, if there's no feedback from the wheel moving the driver will fault. This can happen with any electronic device btw. There are ways to get into the circuit board apparently and reset the chip I supposed, but the wheel is new and I'd be better to just return it for a refund. Amazon will issue a refund and I'm working on sourcing a replacement. There's a couple used in Vancouver that I'm trying to sort out pickup for Friday, otherwise I'll have to order a new one from Walmart or Amazon appear to be the best prices and it'll take a week or so. So I'm out of action for a bit but will be back soon. Lol - sad how upset and missing this I've been without it already. I was just getting going! Will be on the grid soon..... What happened in the end buddy? Dod you get your refund and then a new one? |
|
|
|
Post by Uncle De4dly (Ian) on Nov 15, 2018 17:50:15 GMT
I just picked up the new one last night. Probably crazy but I’m going to do the firmware update on the new one but won’t interrupt the procedure.
So I’m all ready to go. Practiced willow springs last night for the weekend. It’s a funny thing wheel vs controller. Wheel is of course faster but things are much more intense i.e. shit can go wrong fast. I hadn’t spun out at all with the controller but definitely fought spinout at first back on the wheel and pedals
|
|
|
|
Post by Uncle De4dly (Ian) on Nov 16, 2018 6:39:44 GMT
Resolution!
Problem was basic.....I run windows under a VM in Parralells on my Macbook. Most of the time no issues. Oddity here was that the wheel was recognized under the normal driver no problem but not under the boot loader driver. Tech support was basically useless at this point. So used a cheap windows laptop and all updated fine and up and running under new firmware.
|
|
|
|
Post by XRF HammerPH on Nov 16, 2018 11:23:28 GMT
Resolution! Problem was basic.....I run windows under a VM in Parralells on my Macbook. Most of the time no issues. Oddity here was that the wheel was recognized under the normal driver no problem but not under the boot loader driver. Tech support was basically useless at this point. So used a cheap windows laptop and all updated fine and up and running under new firmware. Glad to hear it... the less barriers put in the way of these firmware updates the better so the old laptop was a good move. |
|
