OrigenAE S10V. VFD intermittent errors after sleep.
Posted: Tue 16. Jun 2009, 07:47The VFD on my OrigenAE S10V works perfectly until i enter hibernation, sleep or standby. After waking up the VFD intermittently receives wrong IR code about every 15 button press on a remote (the codes it receives appear to be completely random).
The only way to get the VFD to work flawlessly again I have to:
1. Completely cut the power to the system, rebooting is not enough.
2. Change any of the VFD IR receive timing values, it appears to reset the VFD and temporarily fixes the problem
How can I solve this? Unless there is a fix, is there a simple way to make the VFD reset itself after each wake-up?
Specs:
OrigenAE S10V
Motherboard: Gigabyte EG45M-DS2H
Windows Vista 64bit
Troubleshooting:
- Updated to latest MB BIOS (F4)
- Updated to latest Irtrans drivers from 29.05.09
- Tried different sleep modes (hibernate, sleep, hybrid sleep)
- Tried different USB MB headers
- Updated MB chipset drivers
- Tried with different remotes
I have spent months trying to fix it, even replaced the remote believing there was something wrong with it. Now I finally narrowed the problem down to the VFD receiving intermittent wrong codes after the system has been in sleep. As the problem persists also after a reboot, it appears to be hardware related?
The only way to get the VFD to work flawlessly again I have to:
1. Completely cut the power to the system, rebooting is not enough.
2. Change any of the VFD IR receive timing values, it appears to reset the VFD and temporarily fixes the problem
How can I solve this? Unless there is a fix, is there a simple way to make the VFD reset itself after each wake-up?
Specs:
OrigenAE S10V
Motherboard: Gigabyte EG45M-DS2H
Windows Vista 64bit
Troubleshooting:
- Updated to latest MB BIOS (F4)
- Updated to latest Irtrans drivers from 29.05.09
- Tried different sleep modes (hibernate, sleep, hybrid sleep)
- Tried different USB MB headers
- Updated MB chipset drivers
- Tried with different remotes
I have spent months trying to fix it, even replaced the remote believing there was something wrong with it. Now I finally narrowed the problem down to the VFD receiving intermittent wrong codes after the system has been in sleep. As the problem persists also after a reboot, it appears to be hardware related?