I’m running the latest SGP 4.x as of April4th 2025, and i’m having issue with switches. I added the Asom driver for the Pegasus Power Box v1, but the switches dont seem to work. It allowed me to connect the switch, but it’s causing issues when i load my default profile.
I get an error saying that it lost communication with the switch, but shows it connected with a green connected button, but i cant seem to disconnect the device. Also i could not see any way of changing device settings, e.g. in this case dew heater values.
I really want to disable this without having to to create a whole new profile.
I know this issues is specific to SGP 4 as i dont not see these kinds of issues when i test in Nina, and have full control over the dew heaters and can easily disable the switch.
Well i tried deleting my hardware profile, and then removed the Ascom driver for the switch and then tried creating a new hardware profile and the damned switch is still showing SGP.
Looks like i’m going to have to delete SGP and reinstall unless anyone can come up with a way of disabling the switch in SGP.
Ready to throw SGP out of the window. I’ve uninstalled the Pegasus PowerBox Ascom driver, uninstall SGP, deleted SGP folder under windows $appdata%\local, Reinstalled SGP and it’s still corrupted with the Pegasus switch and rendering the application completely unusable
@ribuck, I understand your frustration.
I had problems deleting switches last year and it took a while for it to get fixed. In the meantime I spent hours deleting files, reinstalling SGP, manually removing switch info from SGP files, uninstalling the switch in ASCOM, etc.
You just posted a few hours ago and it usually takes the SGP folks several days to respond.
Did you try deleting the switch in the “Switches” Control Panel page? If you don’t see that page, right-click on the list of pages in the Control Panel and enable the “Switches” page.
If that doesn’t work, you’ll need to include a log file when this occurred. In SGP click on “Help → Report an Issue” then look for this issue in the drop-down at the top of the dialog box. You can then pick a log file from when you were having the problem.
If you can reproduce this, I suggest restarting SGP, doing only what’s necessary to show the problem, then attaching that log file. It will be easier for the developers to parse.
Unfortunately it wont let me do anything on the switches tab. The bit that i’m confused about is where it stored the info about the switches, as i removed SGP, and removed all folder references to it in %AppData%\local as well as programs files, and removing the askom driver and rebooting my PC so that there should be nothing left, the switches still remained and said they were in a connected state which is not possible as the Ascom driver was removed.
I’ve also seen a few other issues, so i’m finding V4 a little buggy for me.
I’ll keep trying to sort it out and see how it goes as i really like the GUI for SGP, but as it stands i cant remove or disconnect the switches and cant use SGP as it stops me from loading my hardware profiles or creating new ones as the switches keep appearing.
Can you please attach a screenshot of your “Switches” tab (I assume with the switch you are trying to delete)?
What did you try clicking on in that tab?
When I am on my PC I will look for where Switch info is stored.
Do you take backups of your PC? If so, try restoting some SGP files from before you had the problem.
If you create a brand new Sequence, does it also have the switch?
Switches in SGPro are more complex than they seem at face value as SGPro does not treat them as simple interfaces to change the value of a thing (though sometimes I wish it did)… switches as SGPro implements them have been a major thorn in our side.
The crux of the issue is that SGPro is designed in a way that allows you, for the most part, to craft your sequences in a completely offline environment. Not in the sense of “internet” offline, but rather equipment. And thus we encounter our first issue… how do we approach this in a way where switch states (that SGPro needs to interrogate at least one time to even know what switches are present) are available without a connected switch? The answer is of course to cache them and as with any cache it can be corrupted or go missing, etc. SGPro can definitely do a better job here… no arguments here.
To answer a few questions if this pops up again:
SGPro sources the available switches from one of 2 different places:
The ASCOM driver itself (obviously SGPro has no control over this)
Cache. Whenever the switch connects it builds a device level cache. This can be cleared in settings. These cannot be deleted in the switches tab.
Sequence. If the sequence is opened on a device with no cache, the possible states for a switch device will also travel with the sequence itself. These can be deleted in the switches tab.
Many thanks Ken, i’ll refer back to this if i need it again.
I’ve got a few other issues to still try and resolve after my rebuild but hopefully i’ll get them ironed out this week and get a nice stable platform to work with.
