FS-2 won't slew [SOLVED]
I remember the same problem had occurred many years ago when I first tried INDI. At the time I made a slight modification to the source code after which INDI worked perfectly. I had forwarded my modification to the maintainer but somehow the old version must have made its way back. Unfortunately I can't remember as to what the modification was.
Are there any other FS-2 users out there who can confirm my problem? Many thanks for replies.
I got a similar situation here (Mount controller FS-2, Version 1.26, mounts ALT 7AD and "ALT 3" - trying to move from MS Windows to Linux Kubuntu).
After connecting to the FS-2 controller via /dev/ttyS0 the FS-2 Indi control tab shows the correct RA/Dec values and i
- can sync to the mount,
- slew once only!
After that slew will not work again unless I do a new sync to the current position. After that slew will work once again - and so on.
BTW syncing does update the RA/Dec values in the FS-2 handbox - so there is still some bi-directional connection working.
Any idea how we can get to the bottom of this problem? I really would like to switch to Kstars/Ekos.
many thanks for your message. Knowing I'm not the only one experiencing problems eases my pain. I almost came to the conclusion that I'm just too stupid to make it work.. Up until now I am still unable to get it working correctly. Michael Koch has agreed to test my equipment since he was unable to confirm the problem using the same setup. I'll keep you informed of his findings.
Funnily, I found a very old laptop that I haven't been using for many years. This laptop (running Suse 10.2!) has the modified indi version installed that DOES slew and sync.. Same FS-2, same cables, same mount. So the old laptop does the job flawlessly, 4 other computers running newer software (including several versions of Windows, Linux, KStars and Stellarium) do not.
I'll keep you updated.
knro wrote: Do you have the source code in the old laptop for the FS-2 driver?
Many thanks for your reply. I was searching like mad but unfortunately it turned out there is no source code on the laptop anymore.
knro wrote: I just checked the INDI FS-2 driver and it is the only remaining driver that is using the older LX200 Legacy driver. It seems there are hardly any differences between it and LX200Basic driver. Can you try LX200Basic and see if that works? If you have firmware version >= 1.9 then it should be OK.
Both FS-2 and Basic don't work here. My firmware is 1.21. Are there any FS-2 users whose setup actually DOES work? I'll do a few more tests later this week and will report my findings. I tried to send commands by hand using Minicom (9600 8N1) but that didn't work either.
I checked FS-2 documentation and they support all commands in LX200Basic (and even more). You can also enable DEBUG in the driver and check the output.
knro wrote: If Minicom is not working, this could indicate another issue. Check if it could be permission problem, or simply physical cable/USB cable issue. Try changing the physical USB ports. Make sure your user is part of the "dialout" group.
/dev/ttyUSB0 was manually set to 777, my user was member of dialout, connection was reported as OK. Same with another computer that I connected the FS-2 to via RS-232. Crosshairs did move but SYNC and SLEW would not work. The cable did work on my laptop so it should be OK.
However, I've got excellent news. I just installed INDI V1.0 and the latest version of KStars (which was a bit of a hassle). To my utter astonishment everything did work right away! I have no clue as to why because the whole setup is 100% the same and as far as I know no changes had been made between 0.98 and 1.0 with regard to FS-2. Nevertheless, my FS-2 will now SYNC, SLEW, and work perfectly. BTW, LX-200 Basic and Astro-Electronic FS-2 both do the job just fine. I'll do some more testing later tonight in order to confirm that everything is fine, indeed.
Michael, the only thing that I can suggest is installing the very latest versions of INDI and KStars if you haven't done so already. In my case that's INDI V1.0.0-2.1 and KStars 15.04.3-1.1. I truly hope this will solve your problem as it did solve mine.
Happy to hear that FS-2 should work correctly. However, I seem to have trouble getting the correct kstars version to work:
After a standard apt-get update and the following apt-get upgrade (repositories ppa:mutlaqja/.. had been added before) nothing really had changed. Then I uninstalled kstars and libindi* und did a complete reinstall. Still no change in the FS-2 behaviour (no further slewing after the first slew).
A closer look at the software version using apt-cache show xxx reveals the following situation:
libindi0 Version: 0.9.9+r664.187~ubuntu15.04.1
libindi1 Version: 1.1.0+r812.221~ubuntu15.04.1
kstars Version: 4:14.12.3-0ubuntu2
kstars-bleeding: Version: 5:15.04+r5236.221~ubuntu15.04.1 Replaces: kstars
(BTW: neither kstars -v nor kstars --version show version information but start the program. The version-information at the Help tab says "KStars Version 2.3.0 Unter KDE Frameworks 5.9.0" ?!)
At this point I'm lost!. Starting kstars from the comand line gives no clues which version is being started. How can I make sure kstars-bleeding is the program at work?
just got to read Your reply and immediately installed teamviewer.
If You find the time please please contact me at
mhellriegel (at) t-online.de
for further information.
My FS-2 controller does connect but is still not responding to slew commands. Jasem did some changes to an alternate FS-2 driver to enhance debug information and gave direct support to me but we did not yet solve the problem.
Currently I have got hold of another FS-2 controller and will install kstars-bleeding on my laptop (Intel core i5) as well as on an older and smaller Intel Core Duo PC (which has two com ports) and do some testing with various combinations of these hardware components. This may take some time (off home vacation waiting for me as well) and I'll report back as soon as I come to new conclusions.
I will contact You directly about the results of my testing (might be only by the end of September).
Jasem did some intensive debugging on my PC and eliminated problems concerning buffer on the serial connection (I wonder who except me is still using RS232 ports) and an issue with the format the FS-2 controller returning RA values in the format hh:mm,m. (The comma is the decimal sign in a German language environment.)
Now, my two FS-2 controllers just work fine and on top of it Jasem added a parking function to EKOS that does not depend on the FS-2 which does not have this feature. Parking position can be entered using Alt/Az coordinates so I finally get to park my scope array due south on the celestial equator - something I have been missing all the time.
Thanks again to Jasem and I would like to hear from others using a FS-2 controller.
PS: How can I set this thread to being solved? I didn't start it, however.