Recently acquired used LX90 telescope with DSI and LPI, have spent hours reading forums trying to find a solution to communication problems. The DSI and LPI manuals don't show Envisage screen the same as on the program and I can't figure out how to get buttons to work correctly.
I can use Autostar Suite 5.0 on Vista Home Premium SP1 32-bit Toshiba Laptop with LX90 on com port 4 to guide scope. PC has a webcam (Trust Webcam) that I don't use and close it's toolbar when starting up since the toolbar is in my way. I'm successful in aligning, viewing the sky and taking autostar tours. I was finally successful in getting laptop to recognize DSI after copying the dsiusb.sys driver file dated 1/15/2008 from the Meade Driver folders and pasting it to write over an older version in the windows system32 drivers folder.
1. DSI Problem: When I choose Imaging DSI in Autostar Suite and Envisage opens up, many buttons are grayed out. In addition the connect button only gives a choice to connect through network server but I'm already connected via com port and insists that my telescope is not connected. (the PC is connected to the Autostar hand controller port). I also get a "Firmware Command was rejected". I had read that using a com port was more secure than a network server and I'm assuming you can't use both at the same time. I use the option under telescope menu in Autostar Suite connect via com port. Can anyone explain what I'm doing wrong?
2. LPI Problem: When I choose Imaging LPI in Autostar Suite, Envisage opens up but doesn't show LPI as a device. When I check system device drivers, the LPI shows up with properties that say "this device cannot start" (Code 10) and the driver is dated 6/24/2004. I'm unsuccessful in trying to update the driver or ask Microsoft to find a solution. Driver details: Windows\system32\drivers\DsiUsb.sys File version 1.06. I find a DsiUsb.sys file dated 12/13/2004. In trying to troubleshoot I activated the LPI Install wizard which apparently put the old driver back in place. After putting the 1/15/08 driver back in the Win/Sys32/driver file, I tried again but it still is pointing to file version 1.06 even though the newer driver is in the win/sys32/driver folder it accesses. My PC is not recognizing the LPI. Why doesn't the LPI properties at least give the latest driver version for the dsiusb.sys 1/15/2008?