×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

INDI drivers too much %CPU load

  • Posts: 2
  • Thank you received: 2
Hi,

While tutorial_two example driver is running top Linux utility shows as much as 95% CPU occupation !

We have nearly achieved development phase of our INDI driver based on above example.
It will soon enter into validation phase.
La Villette Radioelescope is a thirty years old object and mechanics have suffered from time erosion. It is a 10 m dish initially built for Galaxy atomic hydrogen 1420 MHz listening.

Our driver was developped after tutorial_two example. It is now able to perform GoTo at low and high speed and compensate for Earth motion, following INDI clients Stellarium and Skycharts requirements.

Driver is running on a RaspBerry Pi connected to an interface card via /dev/USB0 driving antenna motors electronic control interface.

As shown by Linux "top" utility, indiserver is using less than 1% CPU whereas tutorial_two is using up to 95 %CPU time even when not performing any task. So does our own driver.

However we found a very simple solution that corrected this situation and now our driver is only using 0.6 to 1% of CPU even when performing a GoTo asked by client Skycharts.

Bernard,
F6BVP
radiotelescope-lavillette.fr/
The following user(s) said Thank You: Jasem Mutlaq
5 years 7 months ago #28201

Please Log in or Create an account to join the conversation.

Great progress!

tutorial_two was a bit old, so I just modernized it a bit just now. At any rate, I just tested and can't see any CPU loads.
5 years 7 months ago #28202

Please Log in or Create an account to join the conversation.

  • Posts: 1029
  • Thank you received: 301
Félicitations pour vos efforts de rénovation, c'est super de voir du monde s'occuper de ce radio-télescope. Je suivrai vos avancées avec beaucoup d'intérêt !

-Eric
The following user(s) said Thank You: Bernard Pidoux
5 years 7 months ago #28204

Please Log in or Create an account to join the conversation.

Time to create page: 0.429 seconds