Hi Marc,
I intend to use 3 cameras with Kstars/Ekos but only one imaging and one giuding camera are supported. The third one I intend to use shall observ the sky in the direction ob main OTA. I call it a cloud camera.
The idea is to start an indiserver with all the major equipment for regular observations and secondly start another indiserver on the same hardware (RPi) with a different port. This will not work. Ofcourse I know the few options of indiserver as the port option.
When I start just one server with all equipment plus the QHY "Cloudcam" and than try to use this device (indi_qhy_ccd) from a second instance of Kstars. It doesn't work eigther.
How would you approach this problem?
Read More...
Hi,
I know it's an old topic but still hot from my perspective.
I know Jasems Tutorial on chained servers and it works well for me.
But my question is, is ti possible to run two indiservers on one system on different ports? I can not make that happen. The only way I have found is to run a users indiserver and another in a systemwide context. like:
systemctl --user enable indiserver.service (on port 7624)
sudo systemctl --system enable indiserver.service (on port 7634)
What I like to accomplish is more like:
sudo systemctl --system enable indiserver.service (on port 7624 and 7634)
What is wrong?
Read More...
Hi everybody,I use a Celestron CGEM II mount on a concrete pole in a sliding roof observatory. I have defined the park position so that the telescope fits under the sliding roof. Please see the screen shots.
What I supprisingly found is the discrepancy between the AZ/ALT coordinates shown in the mounts module and the indi control panel. As well in the hand controler module.
The same is observable in the second screen shot of the Polaris position.
Can somebody explain what the reason for that might be? Or am I wrong and overlook something?
BTW, everything works fine like guiding, goto a.s.on.
Thank for any hint.
bes regards Gunter
Read More...
Good morning and thanks for your report. I saw all the things you mention. But Wolfgang will help. Please read my note. BTW, I ajusted all the pathes in different scrips to /usr/share/weatherradio. I think we will make it work. What OS du you use? In the Apache2 configuration is one differnece to the instructions of WEATHERRADIO.Wolggang enables a module by:sudo a2enmod weatherradio but there is no one. For me only worked: sudo a2enconfThis could not be the reason for the missing data because the web content / frame is shown.
I thing it is a issue with permissions. We will see.
Have a good day.
Gunter
Read More...
Hi Wolfgang,
thank you for your offer to help. I will send you a pn if still necessary. But now I will answer your note.
Yes I followd your instruction in README.md but I have some questions to it:
1. in the first place I was able to create the two rrds, but now I get an error because it seems to be impossible for a regular user to create thosefiles.
How are the permissions for /usr/share/weatherradio and further down? In my case it's pi.pi
2. What does it mean in line 2:
./bin/wr_rrd_update.py
./bin/wr_rrd_ (???)
./bin/wr_rrd_fetch.pv -s 6h
...
3. whitch user should generate the data? root or pi?
Thanks for the hint with the ERROR 11. I disabled all servers and restarted them but still I get the error 11.
In the attached file you will find the service files and the sytemctl status outputs, last part is the weatherradio.conf copy.
Please see also the slide I send about the topology a few entries before this.
In case I run kstars and Ekos I can use weatherradio driver and all other wanted drivers. In parallel I run the indi-allsky package with no issues.
It's getting late now. Have a good evening and clear skies.
Gunter
Read More...
Hi Mark,
can you please provide more detail? I have no issue with indi-weatherradio as the driver itself, but can't get the data in the rrd database. I get a a json file from the webserver of the weatherradio microcontroler 8266 like this (http://192.168.178.74:80/p). see attachement.
Do you have experience to deserialize such a file and put the data into the rrd db?
That'll resolve my issue too.
have a good day.
ggtux
Read More...
Hi Ferrante,
it works just fine. I attache s scheme of ma indi topology. But still I can not compile resp. link indi_ikarusroof_dome under Stellarmate (debian) but works with Raspbean.
I guess I do not habe the right or appropriate WiringPi library.
The project with indi_dome_scripting worked also but I stopped it because the custom driver works flawlessly.
Have a good day.
Gunter
Read More...
Hi Gilles,
after more than 2 years I'd like to ask you what have you accomplished? I'm following this weatherradio threat since about 2 years but still struggling with the data transfer to the webpage.
I run two RPi 4B one on the OTA rig the other in the observatory. Please find the attachement.
Even the last version of weatherradio will not cooperate 
. with the rrd-database and theire scritps. wr_rrd_update.py comes back with"ERROR 11 Resource temporarily not available".
The drivers in Ekos all connect and working. Data are presented and the wifi transmission (JSON pretty print of sensor data "/p") also works fine.
It was also possible to combine the relatively new indi-allsky programm and the "observatory" indi-drivers on different indi ports. So they stoped fighting and concurring about the several devices.
I'm very interested having this system working.
best regards ggtux
Read More...
Hi Ferrante,
sorry for letting you wait for an answer.
Yes I compiled it locally and was successful last week.
The distributed/chained servers are working well. But I see a concurrence between two indiservers on the same machine "allsky". They are blocking each other.
Reason is, I use the new "indi-allsky" suite to control my allsky camera. This package comes with it's own setup and just uses the libindi environmend. It runs on standard port 7624.
My other equipment wath is also connected to the "allsky" raspi starts it's own indiserver on the same port. Now I have the idea to change the port for "indi-Allsky" to 7634 and leave the "standard port" open for my observation purposes with RPI44 and the notebook client.
I attached a sketch to illustrate the topology of my system. Could that working with different ports? And how can I startup the servers (systemctl, I know) in the right order or doesn't matter?
Thank you
Gunter
Read More...
Hi Ferrante,
it's been a while but now I start using the modified indi-ikarusroof driver. it works on a seperate RPi called "allsky".
Usually I use my laptop as a client for a StellarmateOS-Server called "RPI44". This server uses drivers from "allsky" like indi_gpsd and indi_ikarusroof_dome.
Masterserver "RPI44" links to "allsky" by @allsky term in config module of EKOS. The client laptop can not find the "ikarusroof" driver under "Domes" section. Can you explain or advice hoew to proceed? Again the driver works and shows up in the local EKOS-Profile on "allsky" but not on the client laptop.
thank you in advance
Gunter
Read More...
Hi community,
I have adapted the given scripts to my needs, but one question came up. What actually shall abort.py do? And how can I recognize the state after an abort?
My idea would be to count runtime of the motors. But how to transfer this information to the driver or client?
How actually works status.py? It needs 2 arguments but who is sending this path information?
thank you in advance
ggtux
Read More...