You use the WPD Application Programming Interface to create Windows applications. You can write both Windows applications and Web applications with WPD. The system is designed to be flexible so that many types of devices can be explored, and extensible so that driver developers can define custom properties and commands for custom devices. This system supersedes both Windows Media Device Manager and Windows Image Acquisition.Īpplications that are built on WPD can explore a device, send and receive content, and even control the device, for example, take a picture or send a text message. WPD provides a flexible, robust way for computers to communicate with music players, storage devices, mobile phones, cameras, and many other types of connected devices. I'm very concerned about trying to write to the TX with the inconsistent connection.Windows Portable Devices (WPD) enables computers to communicate with attached media and storage devices. Later I was able to go back in, read the TX, modify the settings on one model, but then when I went to write it back to the TX the connection had failed. ![]() It seems like there is a stability problem. Now after rechecking the connection, it seems the popups are not starting, but I do get drive letters in the hidden icons tray. When I closed the popups, I got this message from eepe:ĭ:/RC Aircraft/Eepsky Files/eePe/avrdude.exe -c usbasp -p m64 -U eeprom:r:C:/Users/Jim/AppData/Local/Temp/temp.hex:iĪvrdude.exe: error: could not find USB device "USBasp" with vid=0x16c0 pid=0x5dc It was interesting because eepe would only communicate with the TX when the AutoPlay Popup displayingg Removable Disk (F:) & (G:) was open. I was able to get the model simulator to work, but I could not control the simulator from the TX. I would like to report that eepeskye was able to read the TX file. eepeskye is no joy, when I try to connect, I get two Read Revision = 1 messages. Through all of this typing, Windows explorer is not showing drive letter, Device Manager is showing two additional mass storage devices. The USB tried to reload a couple of times and then the TX stared reporting the two firmware files again.Īt this point I am stopping for the night. The USB tried to reconnect, MS Explorer shut down and the TX screen stopped showing the two Firmware on the screen and reported No Firmware. I clicked on the drive letter and then all hell broke loose. The good news was I got to one drive letter for my TX, the other still had the yellow triangle. I did this and indeed it cleared the code, but I still had the (Code 10) left. I read on the MS website to try to clear the (Code 47) by restarting the computer with the device connected. History since my last post: When I first tried to connect the TX to the USB I got two failed (yellow triangle) Mass Storage Devices. Can you advise what the correct driver is or where is supposed to be? My PC is loading the standard Microsoft USB Mass Storage Device driver dated. Most likely the problem driver is (or is not) on the computer. ![]() It is pretty compelling there is a USB driver and or a timing issue. V1.1 would time out after about a minute. Mike, I installed the Boot Loader per your instructions. If I leave the TX connected, it drops out of the USB mode and then starts up into it normal mode. ![]() ![]() This lasts for about a minute and then the Other Devices and Portable Devices lines disappear. watching the Windows 7 Device Manager, The following lines appear:ĥ. The TX immediately reports it is connecting and the computer makes the connected sound.Ĥ. Once the boot loader is going, I plug the USB into the computer. I press the rudder and Aileron trims toward the center and turn it on. The TX willingly goes into the Boot Loader mode. Before I realized it, I incorrectly ran the eePe. When I try to read the TX memory with eePeSKY it tells me the Disk is not Mounted.ġ. I have cleaned up and removed all of the old and unused USB device drivers (not the USB drivers itself, but the mass storage devices). This is the link: viewtopic.php?f=123&t=7788 At first I started a thread in the hardware section for this computer. I'm struggling to get my 9XR PRO to communicate to the eePeSky Program. What we have here is a failure to communicate.
0 Comments
Leave a Reply. |