Hi Bob,
Am trying to set up the RASC demo system.
Ran into a problem related to the RCOS TCC1 based rotator.
See attached screen shot.
Any idea?
Attachment 9828
Running Win 7 64 Pro, ASCOM Platform 6.3
Printable View
Hi Bob,
Am trying to set up the RASC demo system.
Ran into a problem related to the RCOS TCC1 based rotator.
See attached screen shot.
Any idea?
Attachment 9828
Running Win 7 64 Pro, ASCOM Platform 6.3
Ok, since posting this, I've learned its some kind of issue with elevation - run as admin and UAC.
Turning UAC off, was able to get it working.
With UAC on, now I get an error that ACP requires elevation.
With UAC off, ACP connects just fine.
Will continue to poke around and see if I can figure this out.
Any RCOS owners out there?
Connect nothing as Administrator. This causes loads of trouble. If you started ACP as Administrator, you will need to repair the virtualization damage that did to Settings. Re-run the ACP installer and let it repair the settings info.
It wasn’t clear why you needed to run as Administrator in the first place... Was the RCOS software acting up? Maybe you can change its Program Files install directory to allow all access read and write full control.
Yes, the RCOS software was acting up.
(It wasn't me running it as admin. (I know better... (or at least I should)).
I have RCOS mostly fixed.
Right now ACP will connect successfully to the rotator. It will also launch the mini-console.
Unfortunately, the big TCC console will not connect - I get a Permission Denied 70 error.
Running the Console as admin will work, but obviously this is not desirable.
I think its some windows security "fix" getting in the way between the RCOS TCC.exe and the RCOS_AE.exe server.
My guess is write access permissions to data in Program Files, and if you figure out what the problem is, Windows updates will probably come along and lock some of that stuff back down. Older software suffers from this. I'm planning on putting an auto - fix feature into the next update of ACP.
This is an old thread, however, I thought I would post and document here what I had to do to solve the problem, as I am in the process of replacing my observatory pc.
On my MiniX pc during installation of the RCOS software, the RCOS TCC software was installed to the c:\Program Files (x86) directory. Once installed, I received the same error as Colin.
Steps I took to resolve the issue:
- Verified that the RCOS_AE.Rotator object was in the ASCOM Profile Explorer.
- Turned ON UAC 3/4 to the top of the slider bar.
- Re-registered rcos-ae.exe.
- Changed the rcos-ae.exe & the rcos.exe compatibility to Windows 7.
- Double clicked on the rcos-ae.exe and rcos.exe files, and different messages appeared with both. Just clicked YES through them.
- Turned OFF UAC.
And that solved my problem (knock on wood), after about 8 hrs of troubleshooting. I can now connect to the RCOS_AE.Rotator object in ACP.
Thanks for reporting back Matt.