bu-353 driver loading
i had centrafuse booting up fully with audio playing (from hibernation) in about 7 or 8 seconds. until now. I just installed my gps, which is running perfectly so far without the aid of xport or anything else. I'm running it with all the default settings, and it seems to allocate com5 every time.
My problem is that the time to boot takes about the same, and the music will start to play. however, the screen freezes and the touchscreen fails to operate for about a minute or more until you hear the "usb device chime", at which point the screen un-freezes and the system is fully functional again.
before the gps, during bootup from hibernation, you would hear the music begin, and then seconds later the usb chime would sound and the touchscreen would then function.
is there a way to set the touchscreen driver to load first, and then the gps. I rarely use the gps, and obviously touchscreen functionality is more of a priority.
nobody has experienced this, or can think of a solution to load the drivers at diff. times?
I'm not 100% sure about this, but heres a shot...
Windows must be picking some order to scan through all the USB ports for devices.
So if it is scanning ports in a certain order, maybe swapping the usb ports of the screen and gps will work.
That is strange. The chime means new hardware was just connected that wasn't connected before, so there could be an issue with the USB hub or controller. Whatever those devices are connected to.
What's you're setup like? XP or 7? SSD? Cold boot, hybrid sleep? It could also happen if you're cold booting and not shutting down completely which would require Windows to install the drivers every time, or hibernating without having rebooted since the drivers were isntalled.
Originally Posted by PaulF
Good thought, and easily done as well. I'll try it out tommorrow. thanks
I'm running tinyXP on a sata 2.5". This is happening after coming out of hibernation. I did just install the gps, but i always try too do a cold boot every once in a while so i'm not always hibernating. I give it another shot and see if it happens the first time after a cold boot and hibernate.
Originally Posted by Curiosity
Also, as far as i remember, the chimes have always happened for the lilliput touchscreen. after coming out of hibernation, i would always get the "high, low" and then the "low, high" before the touchscreen would work, but it used to only be a matter of seconds before the gps was installed.
Good. XP doesn't really save all parts of the registry until it shuts down.
OK, both chimes. That reminds me of the time I plugged a USB plasma ball into a non-powered hub. The initial surge from it starting up dropped the voltage so low that the hub went offline and back on. That can be seen with a volt meter, but usually we don't look for things like that.
So possibly adding more devices increases the current requirements above the 5V rail maximum output. Find something else to unplug and try it.
Another possibility if that works is too much on 1 non-powered hub. Many of us experience that one. A hub can only supply 400mA total to all ports (100mA to itself).
Then there's the USB conflicts. Usually a touchscreen and GPS together on a hub causes all kinds of problems like working every other time.
Originally Posted by Curiosity
I'm not actually running on a hub. My via c7 migrus motherboard has 8 usb ports. the header goes to the two front usb's and the 6rear... would the rear be a built in hub? because i have a bluetooth dongle, gps, touchscreen, and wifi all running off the back. I did pull the bluetooth with a small improvement. Also, every time i hit reverse and the monitor switches to the rearview camera I hear the "high, low" disconnection chime and when it goes back to "pc" i hear the "low, high" twice before the monitor and touchscreen come back on fully again. and when i hit the brakes it also wants to switch and i hear the chimes. I'm at a loss, at least you seem to have a grip on what's going on! thank god for these forums!
Any internal USB ports should be on the root hub and should have 500mA per port. Sometimes with that many ports, the front and back share the same port and can't be used at the same time, but you'd know because something wouldn't be working.
Working better without the bluetooth still sounds like a power issues. WiFi probably uses more. Remove that and try. If it's working great, then I'd say power. Most likey you need a stronger power supply. You can also try different ports, but not sure if it will help.
The chimes from the monitor connecting/disconnecting are normal. It's just like unplugging your monitor. The brake switching the monitor sounds annoying though. I'd check on that. How is that wired? Something in the car to an input on the monitor? Are you sure it's not shorting anything?
force it on port 1 if you dont use it for anything else so it doesn't have to scan so much. If you can force the touchscreen drivers onto another port, like 2 or 5 or something, that would be great too. Keep them always plugged into the same physical USB ports so that they don't get reassigned something else.