155 replies to this topic

[Takito Nagai]

Check that auto-focus is on manual - it is the common reason it fails.

thank you.

I'll check again.

[artik]

I usually don't access Android's internal files, so I researched how to retrieve the files and would like to share them with you.

1. Get the “Files by Google” app

2. Access Android/media/org.openlivestacker/OpenLiveStacker/

3. Select the Log file and save it to “Share” → “Google Drive”

4.change extension　.log→.txt

5.upload

I think that now even general users who have not acquired root will be able to acquire log files. (I would like a function that can be obtained from the OpenLiveStacker app...)

 

ps.

I compiled the linux version from source.

It seems to have been installed successfully, but I can't seem to do anything with the installed config.json.

How should I write the config.json file for the INDI driver to work?

It does not require root access. Just to set in file viewer see all files. I don't have even a single rooted device.

But I agree that some shortcuts could be nice. Including sharing image, gallery etc.

 

Also please add application logs with UVC device (log.txt)  I don't see any specific errors.

 

Regarding touptek - especially since it fails on ToupView as well try different Android device. I have Meade/ToupTek based camera and it fails to open on some devices and work on some others, and sometimes unstable on some. I tried to address with ToupTek support but without much success. Probably need to pressure them more.

 

Regarding Linux - please refer to this: https://github.com/a...OpenLiveStacker

[Takito Nagai]

Check that auto-focus is on manual - it is the common reason it fails.

I changed to manual focus and confirmed it.

・Recognition and connection are OK
・Change of ISO and shutter speed works
・When I press the "Stream" button, the shutter continues to be released.
・If you check the "Find View" checkbox, the mirror will be raised, but the live view will not be displayed.

Apparently the live view mode isn't working.

When I press the "Stream" button, the shutter continues to be released, so I felt it would be better to have a "Preview" button for test shooting.

I also got the log, so I'll attach it.

Attached Files

•  gphoto2_camera.txt   336.19KB   3 downloads

[Takito Nagai]

It does not require root access. Just to set in file viewer see all files. I don't have even a single rooted device.

But I agree that some shortcuts could be nice. Including sharing image, gallery etc.

 

Also please add application logs with UVC device (log.txt)  I don't see any specific errors.

 

Regarding touptek - especially since it fails on ToupView as well try different Android device. I have Meade/ToupTek based camera and it fails to open on some devices and work on some others, and sometimes unstable on some. I tried to address with ToupTek support but without much success. Probably need to pressure them more.

 

Regarding Linux - please refer to this: https://github.com/a...OpenLiveStacker

Regarding the Touptek camera, SharpCap was also buggy and didn't work as desired a month ago, but it seems like the developer got the camera and it has improved amazingly in about a month.

This company's cameras seem to have problems with the SDK. . .

An INDI environment has already been created on Linux.
I would like to somehow connect with OpenLiveStacker, but no matter how I change the config.json file, an error occurs and the connection does not work. . .
I read the article in the link, but I couldn't get it to work.

I would like to know the description of the config.json file that runs the INDI driver. . .

[artik]

I changed to manual focus and confirmed it.

 

Looking into the log

GP2 LOG:lookup_folder:Lookup folder '/store_00020001/DCIM/100CANON'...
Got file /store_00020001/DCIM/100CANON/IMG_0720.JPG
GP2 LOG:camera_trigger_capture:camera_trigger_capture
...
GP2 LOG:gp_filesystem_get_file_impl:Getting file 'IMG_0720.JPG' from folder '/store_00020001/DCIM/100CANON' (type 1)...
GP2 LOG:lookup_folder_file:Lookup folder /store_00020001/DCIM/100CANON file IMG_0720.JPG
GP2 LOG:lookup_folder:Lookup folder '/store_00020001/DCIM/100CANON'...
GP2 LOG:gp_filesystem_get_file_impl:Downloading 'IMG_0720.JPG' from folder '/store_00020001/DCIM/100CANON'...
...
Deleting file /store_00020001/DCIM/100CANON/IMG_0720.JPG
GP2 LOG:gp_camera_file_delete:Deleting file 'IMG_0720.JPG' in folder '/store_00020001/DCIM/100CANON'...

I do see that files arrive. I want to see what happens from App point of view

Please add relevant log.txt - application log as well - it is as critical as camera log.

 

When I press the "Stream" button, the shutter continues to be released, so I felt it would be better to have a "Preview" button for test shooting.

 

See unlike "capture" programs like EKOS, Indi AIN - it is live view - live stream.

 

I understand that it is less natural for DSLR especially when it is clicking all the time, still change it to single capture is to redesign entire data flow. All typical astronomy cameras work with "streaming" so same is simulated with DSLR.

[artik]

Regarding the Touptek camera, SharpCap was also buggy and didn't work as desired a month ago, but it seems like the developer got the camera and it has improved amazingly in about a month.

This company's cameras seem to have problems with the SDK. . .

An INDI environment has already been created on Linux.
I would like to somehow connect with OpenLiveStacker, but no matter how I change the config.json file, an error occurs and the connection does not work. . .
I read the article in the link, but I couldn't get it to work.

I would like to know the description of the config.json file that runs the INDI driver. . .

did you build it with touptek SDK or with indi only? I strongly recommend using direct SDK driver if possible. Indi is relatively new and less tested (I tested it with ASI, sv105 and ToupTek/Meade)

 

Anyway the most important configuration in config.json is "driver" set it to "indi" for indi camera or to "toup" . Also what is the error do you get?

Edited by artik, 21 November 2024 - 07:04 AM.

[Takito Nagai]

It does not require root access. Just to set in file viewer see all files. I don't have even a single rooted device.

But I agree that some shortcuts could be nice. Including sharing image, gallery etc.

 

Also please add application logs with UVC device (log.txt)  I don't see any specific errors.

 

Regarding touptek - especially since it fails on ToupView as well try different Android device. I have Meade/ToupTek based camera and it fails to open on some devices and work on some others, and sometimes unstable on some. I tried to address with ToupTek support but without much success. Probably need to pressure them more.

 

Regarding Linux - please refer to this: https://github.com/a...OpenLiveStacker

I looked for the app log when connecting to UVC capture, but I couldn't find it. . . (There is another UVC log file, so I will send it to you)

Attached Files

•  uvc_cameralog.txt   5.51KB   2 downloads

[artik]

1. Is app log

2. Is camera specific log (

3. Is indi mount log 

 

 

Attached Thumbnails

• 

[Takito Nagai]

did you build it with touptek SDK or with indi only? I strongly recommend using direct SDK driver if possible. Indi is relatively new and less tested (I tested it with ASI, sv105 and ToupTek/Meade)

 

Anyway the most important configuration in config.json is "driver" set it to "indi" for indi camera or to "toup" . Also what is the error do you get?

Since I have an INDI environment that works properly, I wanted to try it out, so I installed OpenLiveStacker.

INDI's Touptek driver also has a bug, so I plan to test it with other cameras.

I would like to know the full text of config.json that works with INDI driver. (I'm not a programmer, so it's hard for me to understand what's in config.json...)

[Takito Nagai]

1. Is app log

2. Is camera specific log (

3. Is indi mount log 

There was no LOG of the app for the same time period that checked the UVC driver.

I'll check it again when I have some free time.

[artik]

{
    "libdir" : "./build",
    "driver" : "indi",
    "indi" : {
        "connection": "192.168.2.101:7624"
    },
    "sim" : {
        "path" : "sim"
    },
    "mem_limit_mb" : 0,
    "toup" : {
        "oem": false
    },
    "astap" : {
        "exe": "astap_cli",
        "db": "data/db"
    },
    "http": {
        "ip":"0.0.0.0",
        "port":8080
    }
}

And if you want OLS to control the indi server (start/stop_ 

 

Add to "indi" part

"start_cmd" : "indiserver indi_touptek_ccd inid_skywatcherAltAz_telescope"

Not sure regarding exact driver names thou - not near dev PC

[Takito Nagai]

{
    "libdir" : "./build",
    "driver" : "indi",
    "indi" : {
        "connection": "192.168.2.101:7624"
    },
    "sim" : {
        "path" : "sim"
    },
    "mem_limit_mb" : 0,
    "toup" : {
        "oem": false
    },
    "astap" : {
        "exe": "astap_cli",
        "db": "data/db"
    },
    "http": {
        "ip":"0.0.0.0",
        "port":8080
    }
}

And if you want OLS to control the indi server (start/stop_ 

 

Add to "indi" part

"start_cmd" : "indiserver indi_touptek_ccd inid_skywatcherAltAz_telescope"

Not sure regarding exact driver names thou - not near dev PC

 

thank you.

After starting INDI,
I tried changing the IP to localhost and running it.

I compiled it according to the instructions on GITHUB, but I can't find the INDI executable file in the build directory. . .

 

The only time I was able to proceed to the camera settings screen on the web browser was when I changed the driver from "sim" to "wdir".
(However, settings cannot be made...)

Attached Thumbnails

• 
• 

Edited by Takito Nagai, 21 November 2024 - 08:35 AM.

[artik]

It seems you are missing indi dev files. Check if there is something under /usr/include/indi/?

You likely need to install indi dev files and rerun cmake.

 

(Indi is latest addition so I forget to add the package names needed)

Not near dev PC to tell which exactly.

 

Also note for mount support make sure to use indi_mount_support branch (i.e. git checkout indi_mount_support)

Once I'll release an official version I'll merge it to main version.

[Takito Nagai]

Looking into the log

GP2 LOG:lookup_folder:Lookup folder '/store_00020001/DCIM/100CANON'...
Got file /store_00020001/DCIM/100CANON/IMG_0720.JPG
GP2 LOG:camera_trigger_capture:camera_trigger_capture
...
GP2 LOG:gp_filesystem_get_file_impl:Getting file 'IMG_0720.JPG' from folder '/store_00020001/DCIM/100CANON' (type 1)...
GP2 LOG:lookup_folder_file:Lookup folder /store_00020001/DCIM/100CANON file IMG_0720.JPG
GP2 LOG:lookup_folder:Lookup folder '/store_00020001/DCIM/100CANON'...
GP2 LOG:gp_filesystem_get_file_impl:Downloading 'IMG_0720.JPG' from folder '/store_00020001/DCIM/100CANON'...
...
Deleting file /store_00020001/DCIM/100CANON/IMG_0720.JPG
GP2 LOG:gp_camera_file_delete:Deleting file 'IMG_0720.JPG' in folder '/store_00020001/DCIM/100CANON'...

I do see that files arrive. I want to see what happens from App point of view

Please add relevant log.txt - application log as well - it is as critical as camera log.

 

See unlike "capture" programs like EKOS, Indi AIN - it is live view - live stream.

 

I understand that it is less natural for DSLR especially when it is clicking all the time, still change it to single capture is to redesign entire data flow. All typical astronomy cameras work with "streaming" so same is simulated with DSLR.

"Live View" did not start when you clicked the "Stream" button, but continued to shoot continuously. (The camera's live view function could not be activated no matter where I operated it.)

Attached Files

•  log.txt   11.61KB   2 downloads
•  log1.txt   36.88KB   2 downloads

[Takito Nagai]

It seems you are missing indi dev files. Check if there is something under /usr/include/indi/?

You likely need to install indi dev files and rerun cmake.

 

(Indi is latest addition so I forget to add the package names needed)

Not near dev PC to tell which exactly.

 

Also note for mount support make sure to use indi_mount_support branch (i.e. git checkout indi_mount_support)

Once I'll release an official version I'll merge it to main version.

There was no "INDI" in the "include" directory.

Please add INDI-related addition methods to Git when you have time.

Attached Thumbnails

• 

[artik]

"Live View" did not start when you clicked the "Stream" button, but continued to shoot continuously. (The camera's live view function could not be activated no matter where I operated it.)

From the logs I see images are arriving...

2024-11-21 20:15:21; stacker, info: Real time video frame 17 arrived (video_stream.h:119)
2024-11-21 20:15:23; stacker, info: Real time video frame 18 arrived (video_stream.h:119)
2024-11-21 20:15:24; stacker, info: Real time video frame 19 arrived (video_stream.h:119)
2024-11-21 20:15:26; stacker, info: Real time video frame 20 arrived (video_stream.h:119)
2024-11-21 20:15:26; cppcms_http, info: Timeout on connection for URI: unknown from  (http_api.cpp:185)
2024-11-21 20:15:27; stacker, info: Real time video frame 21 arrived (video_stream.h:119)
2024-11-21 20:15:29; stacker, info: Real time video frame 22 arrived (video_stream.h:119)
2024-11-21 20:15:30; cppcms_http, info: POST /api/camera/stream (http_api.cpp:294)

Can it be that images are just dark (iso too low, lens covered etc)

Don't forget there is no auto exposure.

 

Generally you should see "green screen" and than images.

[artik]

There was no "INDI" in the "include" directory.

Please add INDI-related addition methods to Git when you have time.

You need libindi-dev package

 

This is probably relevant for you: https://indilib.org/...spberry-pi.html

[Takito Nagai]

You need libindi-dev package

 

This is probably relevant for you: https://indilib.org/...spberry-pi.html

 

You need libindi-dev package

 

This is probably relevant for you: https://indilib.org/...spberry-pi.html

The INDI environment is already set up.

I installed everything from the linked repository.

libindi-dev is a developer library and does not seem to be installed along with the server or driver installation.

If Jasem's repository was added, I was able to install it using the following command:

 

sudo apt install libindi-dev

 

Although libindi-dev has been added, the executable file for OpenLiveStacker that calls INDI is probably lacking at present, so please add it to GIT if you have time.

Edited by Takito Nagai, 22 November 2024 - 08:36 AM.

[Takito Nagai]

I changed the config.json description you taught me and tried the UVC driver in a Linux environment.

The camera was recognized, but it seems that permissions are insufficient when accessing from a browser.

Are there any additional usernames required for camera access on the Linux version of OpenLiveStacker?

/dev/video0

I have already added the logged in user and www-data.

 

Attached Thumbnails

• 

[artik]

Look here https://github.com/a...o-access-camera

 

Also note uvc is accessible directly via usb

[Takito Nagai]

ps.

This is not limited to the Linux version, but the INDI driver will not work properly unless you configure and save the driver settings on a client called the control panel when starting the server driver for the first time.

There is no existing INDI client environment in which driver settings can be made from a browser.

If OpenLiveStacker is used alone, it is expected that many drivers will not function properly unless a function equivalent to a control panel for configuring drivers is provided. (Driver settings are required only for the first time.)

 

ASIAir uses INDI only for the mount driver, but it contains configuration files that are validated by the manufacturer and cannot be modified by the user.

I think it is necessary to add a control panel function for driver settings or incorporate a configuration file that has been confirmed to work, similar to ASIAir. (It would be nice if the functionality equivalent to the control panel was already built in...but I have included it here just in case, as I have not yet confirmed the operation of the Linux version)

[artik]

ps.

This is not limited to the Linux version, but the INDI driver will not work properly unless you configure and save the driver settings on a client called the control panel when starting the server driver for the first time.

There is no existing INDI client environment in which driver settings can be made from a browser.

If OpenLiveStacker is used alone, it is expected that many drivers will not function properly unless a function equivalent to a control panel for configuring drivers is provided. (Driver settings are required only for the first time.)

 

ASIAir uses INDI only for the mount driver, but it contains configuration files that are validated by the manufacturer and cannot be modified by the user.

I think it is necessary to add a control panel function for driver settings or incorporate a configuration file that has been confirmed to work, similar to ASIAir. (It would be nice if the functionality equivalent to the control panel was already built in...but I have included it here just in case, as I have not yet confirmed the operation of the Linux version)

Ok on OpenLiveStacker android app the files that are usually placed under /usr/share/indi go to a special location.

 

Out of telescope drivers under core indi repostory none required.Under 3rd part eqmod and other derivatives use it and indeed load them. There are some more telescope drivers in indi-3rdarty I hadn't ported yet (avalon?)

 

Additionally indi driver save config under ~/.indi/ directory it is simulated under Android by Android/media/org.openlivestacker/OpenLiveStacker directory - you'll find .indi directory there with all settings.

 

Regarding control panel - I understand there may be some more options. Can you be more specific what you expect to be controlled?

[Takito Nagai]

Ok on OpenLiveStacker android app the files that are usually placed under /usr/share/indi go to a special location.

 

Out of telescope drivers under core indi repostory none required.Under 3rd part eqmod and other derivatives use it and indeed load them. There are some more telescope drivers in indi-3rdarty I hadn't ported yet (avalon?)

 

Additionally indi driver save config under ~/.indi/ directory it is simulated under Android by Android/media/org.openlivestacker/OpenLiveStacker directory - you'll find .indi directory there with all settings.

 

Regarding control panel - I understand there may be some more options. Can you be more specific what you expect to be controlled?

I've been using INDI for quite some time.

The Android version of OpenLiveStacker is planned to be used as a lightweight EAA environment that can be completed only on Android by porting INDI.

Regarding the Linux version, there are many INDI environments that already work, so I tried compiling it to confirm. (I was thinking of using it as a live stack EAA if things go well.)

 

The above are concerns when dealing with INDI.

Although the files in /usr/share/indi are xml files for starting drivers, it is recommended that you only use drivers that are known to work (configuration files are properly recorded).

INDI driver

1. Start the server driver (use the XML file in /usr/share/indi to select the driver to start in the GUI environment)

2. Connect the driver and device

It works in a two-step process.

 

A configuration file is created in ~/.indi/ when 1 is started, but it often does not work properly unless it is connected to a device and configured in the control panel and then saved. (Since the configuration file will be created in an incomplete state, part 2 can be automated as long as you have a configuration file that operates normally.)

I think you can use the ported Android version without any problems if you only allow drivers that have been confirmed to work. (It worked fine when I checked because I was using the same mount as you.)

 

The problem is the Linux version.

In the case of Linux, if you update the INDI driver and load an old configuration file, there is a risk that the driver will crash. (Because driver setting items change frequently)

Every time a user updates the software, they have to go through the tedious process of deleting the old configuration file, loading the default settings, checking settings and operation, and saving the settings. . . (Most of the trouble reports that are flooding the INDI forums are due to insufficient (or no) settings.

 

I wrote this because I felt that it would be better to consider how to deal with the above problem since the Linux version of OpenLiveStacker seems to only be operated from a browser. (You have two choices: leave the settings up to the user, or allow them to select only drivers whose operation has been confirmed.)

[artik]

Ok lets do some "order"

 

There is a difference in how OLS works with indi on Linux and on Android. Most of settings you select in Android UI like driver, or memory limit you define in configuration file. (Probably I need some wrapper)

 

However there is a difference regarding how telescope indi drivers are handled.

 

On Android I build a special version of indi that runs the indi server and indi driver inside the process because Android is very unfriendly to non-native processes.

So under Android when you need to actually select start the indi driver/server you need. This was the main and most complex part of the port.

 

Under Linux you use standard well tested architecture. When you open mount configuration you'll only see "indi:remote" driver - basically connect to an external indi server and selection of driver can be done via EKOS. Or you can it manually via "indiserver indi_eqmod_telescope" or give this command line in the configuration that would start the server prior to running the OLS and shut it down upon exit.

 

Note: I noticed that start_cmd worked only with indi driver (for camera) so I moved indi_cmd to top level and it would run any process regardless of camera driver (so run git pull to get this update)

{
    "libdir" : "./build",
    "driver" : "toup",
    "mem_limit_mb" : 4096,
    "astap" : {
        "exe": "astap_cli",
        "db": "./data/db"
    },
    "http": {
        "ip":"0.0.0.0",
        "port":8080
    },
    "start_cmd" : "indiserver indi_eqmod_telescope"
}

For for indi camera

{
    "libdir" : "./build",
    "driver" : "indi",
    "mem_limit_mb" : 4096,
    "astap" : {
        "exe": "astap_cli",
        "db": "./data/db"
    },
    "http": {
        "ip":"0.0.0.0",
        "port":8080
    },
    "start_cmd" : "indiserver indi_eqmod_telescope indi_asi_ccd"
}

And of course you can start it externally via EKOS...

[Takito Nagai]

Ok lets do some "order"

 

There is a difference in how OLS works with indi on Linux and on Android. Most of settings you select in Android UI like driver, or memory limit you define in configuration file. (Probably I need some wrapper)

 

However there is a difference regarding how telescope indi drivers are handled.

 

On Android I build a special version of indi that runs the indi server and indi driver inside the process because Android is very unfriendly to non-native processes.

So under Android when you need to actually select start the indi driver/server you need. This was the main and most complex part of the port.

 

Under Linux you use standard well tested architecture. When you open mount configuration you'll only see "indi:remote" driver - basically connect to an external indi server and selection of driver can be done via EKOS. Or you can it manually via "indiserver indi_eqmod_telescope" or give this command line in the configuration that would start the server prior to running the OLS and shut it down upon exit.

 

Note: I noticed that start_cmd worked only with indi driver (for camera) so I moved indi_cmd to top level and it would run any process regardless of camera driver (so run git pull to get this update)

{
    "libdir" : "./build",
    "driver" : "toup",
    "mem_limit_mb" : 4096,
    "astap" : {
        "exe": "astap_cli",
        "db": "./data/db"
    },
    "http": {
        "ip":"0.0.0.0",
        "port":8080
    },
    "start_cmd" : "indiserver indi_eqmod_telescope"
}

For for indi camera

{
    "libdir" : "./build",
    "driver" : "indi",
    "mem_limit_mb" : 4096,
    "astap" : {
        "exe": "astap_cli",
        "db": "./data/db"
    },
    "http": {
        "ip":"0.0.0.0",
        "port":8080
    },
    "start_cmd" : "indiserver indi_eqmod_telescope indi_asi_ccd"
}

And of course you can start it externally via EKOS...

If the Android version of INDI you created does not require the user to update the driver configuration file like the Linux version, the Android version is likely to be more stable to use.

I am using Ubuntu Linux, but security has become stricter since 22.04, making it difficult to handle non-standard network processes like INDI. (Even worse at 24.04)

 

This time, the environment in which OpenLiveStacker was compiled on Linux was 24.04. (INDI is also the latest)

In this system, there were many cases where INDI itself malfunctioned, so I will try it in a different environment.

 

ps.

I did a push pull, but it seems that the binary to start INDI is not written.

Edited by Takito Nagai, 22 November 2024 - 10:12 PM.