Wolfgang Birkfellner replied to the topic 'SkySafari middleware?' in the forum. 4 hours 12 minutes ago

hi!
i did an interface to sky safari for my controller project TSC - github.com/selste/TwoStepperControl/wiki/TSC
here is how i did it - i open a QServer that listens for an incoming connection and process the LX200 commands directly in the controller once a socket is established. the LX200 interface of sky safari is rather clean, by the way. if i would do that for another mount controller, I would use a pi zero w and a RS232 level shifter (like this one: www.sparkfun.com/products/449 ) to communicate with the mount ...
running an INDI server on the pi is of course also a possible method.
yours
wolfi

Read More...

Wolfgang Birkfellner replied to the topic 'May I introduce - my Raspberry Pi Controller/Autoguider - TSC' in the forum. 4 hours 18 minutes ago

hi!
no, i was not aware of that. good to know. mount control via indi is still on the to-do list, also for kstars lite ...
yours
wofli

Read More...

hi!
just a little update - more testing, debugging, hardware addons like a hardware watch and an internal USB/RS232 converter, all INDI cameras (theoretically) and above all a rather stable interface to Sky Safari, CdC, Stellarium , SkyTechX via ASCOM (thanks knro for INDI, btw ...) - screenshots are in the appendix of the wiki ... github.com/selste/TwoStepperControl/wiki/TSC
yours
wolfi

Read More...

Wolfgang Birkfellner replied to the topic 'Still stuck with my ZWO 120MM' in the forum. yesterday

hi!
hum - which operating system? the 120 MM works fine with my Raspian, could it be a USB-cable/hub/whatever problem????
yours
wolfi

Read More...

thanks man ... this was a classical case of coders mental blockage ;)
yours
wolfi

Read More...

hello!
I have modified the INDI client example to quite an extent to read ccds - however, one thing I was not able to manage in the past few hours is the retrieval of the device connected. i have, for instance, an INDI server for the qhy running (as "indiserver - v indi_qh_ccd") and my old qhy device has the name "QHY CCD QHY5-0-M-" ... but upon connecting to the server, I fail to get the device name ... it should be INDI::BaseClient::getDevices(), right? does someone have a few lines of code where this works, I failed completely :D
yours
wolfi

Read More...

Wolfgang Birkfellner replied to the topic 'Rajiva MCU UPDATE' in the forum. 1 week ago

hi!
from my experience, CdC has a rather clean implementation of basic lx200 - before i kicked my littlefoot controller, things worked fine with CdC. maybe try CdC first, especially when it comes to accuracy and so on ....
yours
wolfi

Read More...

nMAC thanked Wolfgang Birkfellner in topic Rajiva MCU UPDATE 1 week ago

hi!
almost solved the problem - INDI LX200 classic sends ::Sr HH:MM:SS# instead of :Sr HH:MM:SS# and ::SdsDD*MM:SS# ... to unfamiliar with bug reporting, how can i do this?

just one additional question: LX200 basic still does not work, and the dialog still does not disappear although the system now works. with INDI LX200 classic, I get an <ACK> (ASCII 6) first, which I respond to with "P". THEN I get #: with a bunch of non printables, followed by :GR#, so it is #: :GR# ... then, calendar format and so on is requested .... does anyone have an idea what this first command after <ACK> is???
yours
wolfi

Read More...

Wolfgang Birkfellner replied to the topic 'Rajiva MCU UPDATE' in the forum. 1 week ago

hi!
I think I have found the answer 15 minutes ago. I had the same problem with TSC, my current programming project, a telescope control/autoguider system on a raspberry pi. it is an INDI bug in my opinion: the LX 200 commands for conveying ra and decl are :SrHH:MM:SS# and :SdsDD*MM:SS# where HH MM and SS are hours, minutes and seconds, s is the sign and DD is the degree ...

INDIs LX 200 classic driver sends ::Sr HH:MM:SS# and ::SdsDD*MM:SS#

notice the difference? the LX 200 parser looks for the characters after : ... so in a proper command, it finds for instance Sr ... - in the INDI command, it finds :Sr and does not recognize the command. this is specific to the INDI drivers (it is not found with Advanced LX200 ASCOM or the direct LX 200 implementations of CdC or C2A). therefore it has to be fixed in the INDI driver as the MCU update and other Littlefoot controllers are no longer supported....
yours
wolfi

Read More...

hi!
I had these problems before, but I thought it would be better to solve other issues in the course of my home project TSC, a telescope controller/autoguider on a Pi - github.com/selste/TwoStepperControl/wiki/TSC

In short - a qeustion to all who have programmed LX200 communications before. I can now control my scope via LX200 in CdC and C2A as well as with the Advanced ASCOM LX 200 driver using CdC, SkyTechX or C2A. But LX200Basic does not work with KStars.

A log follows. and what happens in short is the following:
- I connect via the telescope wizard
- INDI claims that I am connected, but a Dialog "Please wait while KStars is connecting to your telescope" showing 100% remains up in the background ...
- I get #:GR#:GR# ... #:GR# ... #:GD# - i also respond to these properly using high precision. I see " LX200 Basic is online. Retrieving basic data... " in the the INDI Control Panel ...
- Then KStars stops polling data
- If I try to sync or slew, I get the Right Ascension, and then the INDI control panel says "Error setting RA/DEC. " - I do respond with "1" to a Sr command, but that is apparently not accepted ...

any idea?????

yours
wolfi



- I can try to sync but I do not

2017-04-13T17:30:29.839 - DEBG - INDI: Starting local drivers...
2017-04-13T17:30:29.847 - DEBG - INDI: INDI Server started locally on port 7624
2017-04-13T17:30:29.847 - DEBG - INDIListener: Adding a new client manager to INDI listener..
2017-04-13T17:30:29.847 - DEBG - INDI: Connecting to local INDI server on port 7624 ...
2017-04-13T17:30:29.848 - DEBG - Connection to INDI server is successful
2017-04-13T17:30:29.853 - DEBG - Received new device LX200 Basic
2017-04-13T17:30:29.854 - DEBG - INDI Server: "2017-04-13T15:30:29: startup: /usr/bin/indiserver -v -p 7624 -m 100 -f /tmp/indififoaa3e7375 "
2017-04-13T17:30:29.854 - DEBG - INDI Server: "2017-04-13T15:30:29: listening to port 7624 on fd 3"
2017-04-13T17:30:29.854 - DEBG - INDI Server: "FIFO: start indi_lx200basic -n \"LX200 Basic\""
2017-04-13T17:30:29.854 - DEBG - INDI Server: "With name: LX200 Basic"
2017-04-13T17:30:29.854 - DEBG - INDI Server: "FIFO: Starting driver indi_lx200basic"
2017-04-13T17:30:29.854 - DEBG - INDI Server: "2017-04-13T15:30:29: Driver indi_lx200basic: pid=2920 rfd=4 wfd=7 efd=8"
2017-04-13T17:30:29.854 - DEBG - INDI Server: "2017-04-13T15:30:29: Client 5: new arrival from 127.0.0.1:50964 - welcome!"
2017-04-13T17:30:29.854 - DEBG - INDI Server: "2017-04-13T15:30:29: Driver indi_lx200basic: Initializing from LX200 Basic device..."
2017-04-13T17:30:29.854 - DEBG - INDI Server: "2017-04-13T15:30:29: Driver indi_lx200basic: snooping on GPS Simulator.GEOGRAPHIC_COORD"
2017-04-13T17:30:29.854 - DEBG - INDI Server: "2017-04-13T15:30:29: Driver indi_lx200basic: snooping on GPS Simulator.TIME_UTC"
2017-04-13T17:30:29.854 - DEBG - INDI Server: "2017-04-13T15:30:29: Driver indi_lx200basic: snooping on Dome Simulator.DOME_PARK"
2017-04-13T17:30:29.854 - DEBG - INDI Server: "2017-04-13T15:30:29: Driver indi_lx200basic: snooping on Dome Simulator.DOME_SHUTTER"
2017-04-13T17:30:29.854 - DEBG - INDI Server: ""
2017-04-13T17:30:29.877 - DEBG - INDIListener: Processing device LX200 Basic
2017-04-13T17:30:29.900 - DEBG - < LX200 Basic >: < CONNECTION >
2017-04-13T17:30:29.908 - DEBG - < LX200 Basic >: < DRIVER_INFO >
2017-04-13T17:30:29.943 - DEBG - < LX200 Basic >: < DEBUG >
2017-04-13T17:30:29.956 - DEBG - < LX200 Basic >: < SIMULATION >
2017-04-13T17:30:29.960 - DEBG - < LX200 Basic >: < CONFIG_PROCESS >
2017-04-13T17:30:29.961 - DEBG - < LX200 Basic >: < DEVICE_PORT >
2017-04-13T17:30:29.962 - DEBG - < LX200 Basic >: < TELESCOPE_BAUD_RATE >
2017-04-13T17:30:29.962 - DEBG - < LX200 Basic >: < ACTIVE_DEVICES >
2017-04-13T17:30:29.963 - DEBG - < LX200 Basic >: < DOME_POLICY >
2017-04-13T17:30:31.749 - DEBG - LX200 Basic : "LX200 Basic is online. Retrieving basic data... "
2017-04-13T17:30:31.773 - DEBG - < LX200 Basic >: < ON_COORD_SET >
2017-04-13T17:30:31.781 - DEBG - < LX200 Basic >: < EQUATORIAL_EOD_COORD >
2017-04-13T17:30:31.793 - DEBG - < LX200 Basic >: < TELESCOPE_ABORT_MOTION >
2017-04-13T17:30:31.805 - DEBG - < LX200 Basic >: < TELESCOPE_MOTION_NS >
2017-04-13T17:30:31.836 - DEBG - < LX200 Basic >: < TELESCOPE_MOTION_WE >
2017-04-13T17:30:31.838 - DEBG - < LX200 Basic >: < TELESCOPE_INFO >
2017-04-13T17:30:31.844 - DEBG - < LX200 Basic >: < TARGET_EOD_COORD >
2017-04-13T17:30:31.845 - DEBG - < LX200 Basic >: < USEJOYSTICK >
2017-04-13T17:30:31.846 - DEBG - < LX200 Basic >: < Slew Accuracy >
2017-04-13T17:31:04.060 - DEBG - ISD:Telescope: Sending coords RA 1.87143 DEC -10.253
2017-04-13T17:31:09.066 - DEBG - LX200 Basic : "Error setting RA/DEC. Unable to Sync. "
2017-04-13T17:31:45.433 - WARN - QSqlDatabasePrivate::removeDatabase: connection 'userdb' is still in use, all queries will cease to work.

Read More...

Wolfgang Birkfellner replied to the topic 'QHY5 - alccd5 mono distorted images' in the forum. 4 weeks ago

hi!
my ALccd5 is ~ 5 years old, maybe things have improved since then. under windows, it can only be accessed when plugged into the usb port which was used during installation, it had to undergo a hardware fix and all kinds of unnecessary stuff like that.

the opensource comunitiy consists of people like jaseem and me who develop software and provide it as a community support. in other words - no more support from qhy :/

i have recetly bought a ZWO ASI 120 MM (i think, i don't have it at hand) - have not tested it under the skies yet, but it works fine with INDI ...
lg
wolfi

Read More...

Hi!

recently I trashed my Littlefoot V-power, an action that left my without a stepper controller for my rather heavy Houghton telescope. Beyond that, I was annoyed by the plethora of adapters, cables, additional programs hampered by Windows component updates and so on. So I programmed my own stepper controller on a Raspberry Pi 3, which features standalone autoguiding via INDI, observation lists and catalogs, an LX200 interface and a ST4 interface. Not all features are fully tested and everything is in a very early stage - but code is available and I documented the project a little bit. It can be found under TSC-Wiki alongside with the C++code. Comments are highly welcome ...
yours
wolfi

Read More...

Wolfgang Birkfellner replied to the topic 'QHY5 - alccd5 mono distorted images' in the forum. 2 months ago

hi!

well ... I try to translate without being nasty ...
"On linux there is no concept of system driver. "

= "I don't have the faintest idea of UNIX-type operating systems. All those little files in this so-called /dev folder are a mystery! Books like this one - Linux Device Drivers - should be filed under Science Fiction..." :blink:

"It is the communication protocol between camera and the host . We now is making a new low level protocol standard for our cameras to let the cameras working under other systems. We can put the QHY5V into this todo list to make this protocol . And then the indi developer can use this protocol to communication with camera."

= "I am unaware that there is actually an interface for the camera and yours was forgotten anyhow..."

sorry for not being more enthusiastic. The only solace I can offer is that operating my QHY 5 under windows is even more of a pain ...
yours
wolfi

Read More...

Wolfgang Birkfellner replied to the topic 'QHY5 - alccd5 mono distorted images' in the forum. 3 months ago

hi!
the now defunct Alccd 5v ( www.astrolumina.de/kamerasysteme/alccd-q...pen/alccd-qhy-5v.php )
astrolumina is a german seller that relabels qhy cameras ...
the original appears to be this one - stargazerslounge.com/topic/72350-review-of-qhy5v-camera/
yours
wolfi

Read More...

Wolfgang Birkfellner replied to the topic 'QHY5 - alccd5 mono distorted images' in the forum. 3 months ago

hi!
no quick solution as skipping the header and reading the first 752*480 bytes did not work as expected; however, the problem is nevertheless clear. you read 1280*1024 with INDI, whereas the image is only 752*480 pixels, as read correctly by openphd. if you develop your own software, i still believe it can be circumvented - but i would rather contact the qhy people directly and notifiy them of this bug as they are the ones developing the drivers for INDI, as far as i know ...

yours
wolfi

Read More...

Wolfgang Birkfellner replied to the topic 'QHY5 - alccd5 mono distorted images' in the forum. 3 months ago

hi!
first, i would like to take a look whether i am right - as FITS is raw data (header + bytestream), we can at least take a look whether my suspicion is right as the data are contained in the image that you see - but they are only a part of it and the lines are distorted. i assume that the upper quarter of your image (or the lower quarter of the FITS) is the image data, and the remainder is - well, something. that would also make sense as it is 1.3x10⁶ pixels (1280*1024) vs. 3.6x10⁵ pixel (752*480) ...
lg
wolfi

Read More...

Login

3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!