Hello all, I've been a bit frustrated lately with issues regarding our setups at the university. Below is a rundown of what I am using. SW EQ8-R Pro + PPBAV2 + SBIG STC-428P + SC Star Chaser Auto guider Windows 11 23H2 TSX pro Build 10.5.0 Build 13878 (64bit) PHD2 Ive tried getting the best USB cables possible for this. I currently have a USB cable connected from the PC port on the mount to the computer. The PPBAV2 is mounted on a dovetail with usb connection to one of the 4 USB ports on the DEC portion of the mount. This connection is "PC" on PPBAV2 to the USB hub on the DEC portion of the Mount. Power is supplied to the PPBAV2 by connecting to one of the power ports next to it. From there I connect all my necessary components to the PPBAV2 such as: Mount, CMOS, guider, and focuser. Because this issue persisted so much, I did a clean install of windows but kept my files so it would remove the drivers on the OS so that I can start clean. After installing TSX, I proceeded to install ASCOM platform 7.0, Then the DLAP driver before installing the ASCOM drivers for both 64 bit and 32bit. I am currently using TSX 64 bit since this computer is a 64-bit operating system. The star chaser I found was a 32-bit driver so i had to install both so that the camera would work with the TSX and guider with PHD. However, for the past 3hours of troubleshooting, the drivers are fighting each other and are very unstable. I've saw some forms that related to me about the camera drivers disappearing and to follow steps on updating system drivers, but despite this it says my drivers are up to date. The remaining 5 telescopes we have do not have this issue and I am still trying to figure out why. For example, when having the STC 428-P connected to TSX and then connecting the SC star chaser to PHD, when opening up ASCOM to select my camera, you can hear the driver disconnect almost immediately. It sometimes causes the PPBAV2 to disconnect as well. I can't run diagnostics with ASCOM because nothing will connect cause of the exception is thrown. I have attached some images with the error I have received. Thanks for the help. Best, Darien
Darien, My best guess is this is a two-part problem. Sorry for the length of this message. A) Windows and USB B) We've gone 100% 64-bit, and so has Software Bisque. Open PHD Guiding 2 isn't 64-bit yet. There is a solution called ASCOM JustAHub. A) Windows and USB ================ If it's a fresh system install, you might want to check Steps 1-5 here: https://forum.diffractionlimited.com/threads/new-computer-installation.10016/ If you are having USB connection issues, this is usually the problem with cameras, focusers, mounts, dew controllers, dome controllers, and more: https://forum.diffractionlimited.co...connects-turn-off-usb-selective-suspend.7848/ It is important to review and be thorough on the above, especially after any OS changes, updates, or driver updates. What is a PPBAV2 ? If its one of the Pegasus Power Boxes with USB hub hardware: They updated the Unity Platform 2025-07-01. So go get that update, install it, and then check and Update the Firmware in the Power Box. https://pegasusastro.com/download/ B) 64 bit ======= Here's a combination that I know works: 1. Write down which filter is in which carousel slot, as you are likely to lose that setup. 2. Control Panel (cpanel.exe) - Programs - Uninstall Uninstall every older DL Imaging driver and DL Imaging ASCOM drivers. Both the 32 bit and 64-bit versions. It might be listed as ASCOM DL Imaging .... DL Config x64... DL Imaging... It seems that recent Windows Updates have made changes to what is displayed in the Uninstall screens. Reboot. 3. Launch the ASCOM Profile Explorer. Expand [+] Camera Drivers. Verify that there are no DL Imaging camera drivers in the profile. If there are, delete them. 4. ASCOM Profile Explorer Expand [+] FilterWheel Drivers. Verify that there are no DL Imaging filter wheel drivers in the profile. If there are, delete them. 5. Go get and install the most current software updates: a) ASCOM Platform 7 Update 3 Release Candidate 7: https://download.ascom-standards.org/beta/ASCOMPlatform703-rc.7.4755.exe This includes the JustAHub Camera (for 64-bit drivers). You will use this to bridge between 32-bit Open PHD Guiding 2 and the 64-bit DL Imaging ASCOM drivers. The ASCOM folks say it will be a few weeks before the Release Candidate becomes official. b) DL Imaging x64 Driver: https://diffractionlimited.com/down/SetupDLAPIx64.exe c) DL Imaging ASCOM 64-bit driver: https://diffractionlimited.com/down/DLImagingASCOMDriverInstaller_x64.exe d) Run DL Config x64 after installing b) and c). Help... About should show: dlapi.dll ......................... 4.1.2.5 DLAPIWrapper.dll .................. 4.0.2.0 ASCOM.DLImaging.Camera.dll ........ 6.4.26.0 ASCOM.DLImaging.CameraExt.dll ..... 6.4.26.0 ASCOM.DLImaging.FilterWheel.dll ... 6.4.26.0 ftd2xx.dll ........................ 3.2.16.1 ftd3xx.dll ........................ 1.3.0.10 e) Open PHD Guiding 2 development snapshot 2.6.13 dev 7 (January 11, 2025) https://openphdguiding.org/development-snapshots/ This is 32-bit software, no 64-bit yet. They fixed a bunch of stuff after the 2.6.13 release came out,and it's in the Development Snapshots. f) TheSky X Professional 64-bit Version 10.5.0 Daily Build 13936 from 2025-02-09 (February is the latest release). https://www.bisque.com/ You'll have to log in to get the latest. I think the version you have is ok, but I recommend the above. 6. Setup: Let's use 64-bit. Open PHD 2 - the ASCOM camera should be set to JustAHub Camera (for 64-bit drivers) Set JustAHub properties to point to DL Imaging (Camera 2), and then set those properties to pick the StarChaser out of the list of cameras. Like this: e.g. 32-bit PHD -> Camera = JustAHub -> DL Imaging x64 TSX - Camera = ASCOM - DL Imaging (Camera 1) = STC-428 TSX - Filter Wheel = ASCOM - DL Imaging FW Then you should be good to go. Clear skies!
Hi Colin, We were able to try majority of this except TSX update but we are waiting on our dept to renew the license. Despite that, no joy so far. When we reinstalled windows, we did "keep files" and delete everything else that way we have a copy of the old TSX build that we could test on will all known drivers removed. I think the better option to do is do a clean install of windows 11 completely and star from scratch for T3. T2's problem is the CMOS would disconnect at random times during data acquisition or during pointing model development. It'll give the classic 206 error in TSX. Thanks for the help will keep you updated.
Hi Colin, sorry for not defining this variable. We have 6 Meade LX200 12"s we define them by T1-T6 as they are in the same roll-off on 6 separate piers
Hi Colin. We just got renewal for TSX software. We will do the clean install of windows and report back to let you if anything happens.
Hi Colin, Here is an update so far. I have gotten T2 up and running it seems to be stable from following your instructions by the route of a clean windows install. I upgraded TSX to the latest build and also used just a hub to bridge the guide camera in PHD2 For T3 the telescope that I initially made this thread for has the most issues. The SBIG camera Driver is very unstable in general, and I can't figure out the problem. It basically disconnects and reconnects multiple times. This happens from the following situations When connecting the PC cable from the mount to the computer which the Pegasus powerbox Advance v2 (PPBAV2) PC port connected to one of the ports on the DEC it sometimes gives a "Descriptor request failed" Or it will connect and re connect each time. SBIG A and B drivers stay stable. When I do direct connection from PPBAV2 it also dose it similar. However, when connecting it to another PC it seems to be more stable. If i connect the main camera directly its fine. Any ideas? I did see on the SBIG driver which is having the most issues that the boxes "allow this computer to turn off this device" was checked, I unchecked these and rebooted but similar issues.
Glad to hear it. Usual suspects: Cable is too long - USB 3.0 maximum length is 3m / 9.8 feet. USB hardware failure in computer - bad port USB hub or extender - bad port; bad main port to computer; bad power assuming a powered hub; bad oscillator so if it is hot (over 30C/85F) or cold (10C or below) it gets flaky Blown USB port in the camera a Windows Power Management setting missed somewhere in the hierarchy of PCIe host controller; USB Root hub; USB hub, Device; Windows Power Management - USB Selective Suspend = Off What's a "DEC" in "one of the ports in the DEC"? Any chance you could send a photo of the setup, so I can see what you have plugged in where, cable lengths, that sort of thing? Device Descriptor Request Failed (code 43) means there is a hardware communication problem. Bad cable, bad PPBAV2 port or entire USB hub, bad port in the computer, or the USB port in the camera is bad. If the camera works on another computer or directly to the PC, then likely the camera is fine. Suggestions for each of 1-5. 1. The STC-428 will run at either USB 3.0 or USB 2.0 speeds. So you could change to a USB 2.0 cable (like a printer cable - USB A on one side, USB B (square) on the other side.). It will run a touch slower, but this might solve the communication problem until you figure out the root cause. 2. Try another port - eg on the other side of the computer. Try another computer e.g. a desktop - port on back of PC that is on the motherboard, not the case. Microsoft Device View utility will show what ports are connected to what. Device Manager View... Devices by connection can help. Handy trick for Device Manager: Click on the SBIG Camera. View... Show Devices by Connection It will show all the hubs, ports, and root hub that it cascades up through. Like this - orange arrows will show everything up the hierarchy from the camera. Each of those could be powering down, and dropping connection. 3. If you can go direct to computer, bypassing the Pegasus, and it works, then Pegasus is suspect. 4. If camera never shows up on a known-good PC, connected directly (STC-428 will be SBIG Camera; StarChaser will be SBIG Camera A and B), and Unknown Device, or Device Description Failed; THEN let's RMA it for repair. 5. I could remote in and have a look if that would help.
Hi Colin, Sure Ill send some images on how its setup A bizzard scenario. I plugged the USB cable on the port on the side of the computer and everything works! lol One thing i noticed is the FW threw an exception twice but was fixed when unlpluging and replugging the FW connector. Some of the older models of STC 428p have Cord that powers the FW separately we have two cameras like This. Here are some pics
I have quick assist open if you want to remote in just let me know about the code IMG2124 is the DEC portion of the mount where USB ports and power is IMG2122 is where main USB to PC and Main power source for the components. Power for motors is on the side.
Thanks for the clarification and photos - Super helpful. After you sent that, I did some serious digging online - and discovered the SkyWatcher EQ8-R Pro is known to have bad USB wiring, not compliant with USB 3.0. Lot's of stuff about it problems with the EQ8-R PRo's USB online: https://www.cloudynights.com/topic/826206-solvedskywatcher-eq8-r-usb-30-issues/ https://groups.io/g/SkywatcherEQ8/topic/solving_all_eq8r_pro_usb3/97719193 Seems like the "smoking gun" and root cause of the communication problems. Cameras and disk/storage drives are the most demanding of USB devices. So that's the reason it's showing up. Avoid the internal hub in the Dec axis of the EQ8-R Pro - Don't plug the camera into the mount. Go as close to straight to the PC as possible. Yes, this means USB 3.0 wiring OUTSIDE the mount. Not as neat and tidy, but it will work. How far is it from the telescope to the PC? e.g. is there some kind of USB extender between the PC and the mount? Am thinking you might want to do something like this: PC - Powered USB 3.0 Extender (eg Icron 3104 or "known good quality" cheaper one) - Powered USB 3.0 at mount - to (a) Cameras, (b) Pegasus, (c) mount
I saw this too and was a bit disappointed by it. Id say about 16ft but i would need to figure out some cable management to make this work to make it as tidy as possible. maybe mount some hub at the bottom of the pier. and connect from the PPBAV
That sounds like a decent plan. Another customer is using these - I am skeptical, however he says it works: https://www.amazon.com/Extension-CableCreation-Extender-Booster-Compatible/dp/B0BXXCC46Z Apparently it draws a fair bit of power from the PC USB 3.0 port, and is a self-powered extender. I've had good success with the StarTech Industrial USB 3.0 hubs, powered off +12V, however your mileage may vary.
Hi Colin Thanks alot, With fall semester around the corner will keep the setups as is at leas for fall and then will change them in spring as teaching labs are most heavy in the fall. I will need to coordinate with Vallia, but we will need new power cables. Should I still email you? For Telescope #5 New power cable and extender for STC-428P New Power cable and extender for SC star chaser auto guider For Telescope #6 Just the extension cables for them.
You can order them from our website (eg use a departmental Visa or Mastercard as that's usually fast and easy): Power supply with cable: https://diffractionlimited.com/product/camera-ac-power-supplies/ Extension only: https://diffractionlimited.com/product/12vdc-extension-cable/
