Come and join our community. Expand your network and get to know new people!
porkyhttp wrote: EkosLive is a service and it is not related if you use astroberry or other systems. I am interested to the OFFLINE version, but I do not know how it works
@ MG!IFOS! this is what i did to get the camera driver working in Ubuntu 20.04 on my laptop and Ubuntu Mate x64 on the rpi.
create directories to hold project and builds:
download project from github:
git clone --depth=1 github.com/thx8411/indi-3rdparty.git
git checkout thx8411_sv305_2
change to the ~/libsv305-build directory
sudo make install
change to the ~/indi-sv305-build directory
sudo make install
to start the indiserver
sudo indiserver indi-sv305-ccd
i had to start the indiserver as sudo, though im unsure why at this point. perhaps because the library and driver were installed as sudo.
this library is still experimental (though its working quite well).
EkosLive is a service and it is not related if you use astroberry or other systems. I am interested to the OFFLINE version, but I do not know how it works
Just a quick note on this. I managed to raise this with Radek on the SGL forum and he has just pushed through a fix which appears to be working so you just need to sudo apt upadte and sudo apt upgrade and it should ok. I have tested the fix using 1 second updates for the GPS and all seems well.
It is worth noting that EKOS Live is available to Astroberry users as well. Just register on EKOS Live and in the EKOS control click on the little cloud symbol and hey presto - just pop in your log in details and away you go. I have tested this and it works very well.
Thank you for your replies. I wasn't aware of Ekos live. Not exactly what I was looking for, but close.
rickbassham wrote: Some quick searches of the forum show that Stellarmate has an offline version for Ekos Live. Which is good if you are using a Raspberry Pi for imaging.
I try to install pyindi-client as described in
When I try to pip install, for example, with
sudo pip3 install pyindi-client
Downloading pyindi-client-0.2.5.tar.gz (12 kB) ERROR: Command errored out with exit status 1: command: /usr/bin/python3 -c 'import sys, setuptools, tokenize; sys.argv = '"'"'/tmp/pip-install-7g1ed4rp/pyindi-client/setup.py'"'"'; __file__='"'"'/tmp/pip-install-7g1ed4rp/pyindi-client/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-install-7g1ed4rp/pyindi-client/pip-egg-info cwd: /tmp/pip-install-7g1ed4rp/pyindi-client/ Complete output (3 lines): Unable to find libindiclient.a in ['/usr/lib/x86_64-linux-gnu', '/usr/lib', '/usr/lib64', '/lib', '/lib64', '/usr/local/lib'] Please specify a path where to find libindiclient.a in the setup.py script Exiting ---------------------------------------- ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
Thanks Radek this looks like solution I was looking for.
This will save me buying a new Motor Hat
Thanks for your help
i wonder what we think about the benefit of having the option of a:
'Reset alignment after guiding failure'
toggle for the scheduler.
it may give us an extra chance to resume in the correct position after a cloud passes.
Cheers and clear skies,
I believe that it is not a good idea to run simultaneously the hand controller and the USB serial interface of your mount. The hand controller and the indi-eqmod driver may send serial messages at the same time, and I don't know if this is supported (I mean electrically, there is only one wire for the RX port on the microcontroller, thus there should be some multiplexing somewhere or some short circuit protection). And as suggested by Avocette, both the hand controller and the indi-eqmod driver will have their own idea of where the mount is pointing. I believe it may depend on the order of your actions, without speaking of the auxillary encoders and different alignment models. If you perform an alignment with the hand controller, indi-eqmod has no way to access this model, and obviously vice-versa.
May you try without running kstars at the same time ?
It seems the python client does not get the blob data (you may easily check that, there is a print in the newblob callback in the tutorial code).
If you see the print message, there may be something updated in the threading.Event python library which causes this issue.
1. You monitor the property and check if it changed to the new filter number.
2. There is no current filter slot name text property.
3. There are 3 BLOB modes from the client point of view:
3.1 B_NEVER: Never send any binary data (default)
3.2 B_ALSO: Send binary along with regular INDI Messages.
3.2 B_ONLY: Only send binary object, no regular INDI messages are sent.
I added the python article to the tutorial. Do you think you have update it to clarify any issues? or write a new one based on it perhaps?
Hi, apologies if this has been answered in detail - I have this camera and want to use for guiding with an rPi4 & Astroberry. A few weeks ago I attempted to install the driver mentioned in these threads (I believe) but no luck, camera wasn't recognized using any of the software in AB (Kstars/EKos, etc). I have some time again to work on it and I was wondering if maybe I had installed the wrong driver (or incorrectly)? Can someone help point to the location of the latest driver? Is there a guide for installing, in case I did so incorrectly? And can this cam be used as a guide cam with this driver? Sorry for all of the questions, I'm just really anxious to get this part sorted out so I can determine definitively where the issue(s) is. Thanks!
You need a modded camera to control the long exposure (it sets a specific pin available on the internal connector of the cam).
Usually the control of the long exposure pin is made through a serial port (RTS if I remember) and this adds another cable in addtion to the USB camera port.
The LXLED mod consists in unsoldering the led on the board and using that wire to control the long exposure pin. And the LXLED also needs a modded version
of the pwc kernel driver (which does not expose the LED control).
Thus unfortunately, you would have to mod the cam if you want to use it with long exposure.
Hello, i change my setup
Before in this topic:
Stellarmate on RPI4 (box Argon one), Power box GX12 connector 2pins (home made), Hub usb3 12V startech powered (and RPI4 powered with this), EAF ZWO, QHY183M (with FW CFW3), Evoguide 50ED SW with QHY5LII-M and GPS.
TSA102 on AZEQ6.
60x180s L Filters
10x180s RGB Filters
btw, Markus patch for AP Experimental was merged in a couple of days ago. Is that working for you? It's suppose to fix the issues reported before.