Thank you, this was really helpful to me. I removed the other properties I was setting and focused on CCD_CAPTURE_FORMAT.

I was able to get 16 bit raw mode. I maybe have a unique use case. But one thing I ran into is that if you start with a empty ~/.indi/ directory I needed to set the properties, disconnect from camera, then reconnect to really have all the properties have effect. I would see the properties set with indi_getprop, but the camera was not doing the right thing. It might just be something pyindi-client, or the toup driver, or my environment.

I am able to do what I need, and your reply got me moving again, so thank you very much!

Read More...

I'm sure it is user error. I've ran into some trouble switching from libindi 1.8.9 to 1.9.9 in setting raw mode for my camera with pyindi-client. I've tried debugging with indi-getprop and indi-setprop. It was working great for me in 1.8.9, but in 1.9.9 I can't get raw data.

I've gone through and set:

Toupcam GPCMOS01200KPC.CCD_VIDEO_FORMAT.TC_VIDEO_COLOR_RGB=Off
Toupcam GPCMOS01200KPC.CCD_VIDEO_FORMAT.TC_VIDEO_COLOR_RAW=On
Toupcam GPCMOS01200KPC.CCD_CAPTURE_FORMAT.INDI_RGB=Off
Toupcam GPCMOS01200KPC.CCD_CAPTURE_FORMAT.INDI_RAW=On


However I still see:
Toupcam GPCMOS01200KPC.CCD_INFO.CCD_BITSPERPIXEL=8

And also the blob dimensions are still 3xHxW instead of just HxW.


When I use Ekos It see CCD_BITPERPIXEL=16, but not sure how it set that, all I changed there was Format from RGB to RAW.

Does anyone know what step I am now missing to get RAW data instead of 3 channel 8 bit format?

Read More...

Okay in controls-> Resolution.

And I see the default for arm vs non-arm had changed since 1.8.9:Just confused myself real hard since I had a both script thas was getting the lower resolution and ekos was getting lower resolution, but not when on amd64. Really helped me see my error when I did git diff against 1.8.9 and saw default just for arm had changed.

Sorry to waste your time. Thank you for the help.

Read More...

In Image Settings -> Frame?

If I try to change it to 1280x960 it says invalid width requested.

Read More...

I currently suspect it isn't with the SDK itself. Sorry if my messages were confusing. My second message was trying to say that I swapped out the SDK and the issued remained. While this doesn't rule out a problem in the SDK it does seem to indicate that it was something that changed in indi that is causing this.

I am up for trying to debug this some more but would need some guidance on where to start.

This may or may not be helpful but the output of the lower resolution image still has color in raw format, so whatever is causing it to be scaled keeps the bayer pattern.

Read More...

I also did try different libtoup debs. I was using libtoupcam_1.48.0-1_armhf.deb with 1.8.9 and libtoupcam_1.50.1_armhf.deb with 1.9.4

However extracting the .so file from 1.48.0 deb and copy it over onto 1.50.1 made no change.

Read More...

Russell Valentine created a new topic ' indi_toupcam_ccd arm32' in the forum. 12 months ago

Hello. I having a RisingCam IMX224 that uses the indi_toupcam_ccd driver on a raspberry pi.

I've notice on indi versions 1.9.2 and 1.9.4 the maximum resolution is 640x480 even though it should be 1280x960. I also can't manually set it to the higher version it errors with it being invalid.

If I use 1.8.9 I get the full resolution (sorry I have not tried other versions besides these three).

I do not see this issue on amd64.

This happens if I build it myself, or if I use astroberry binaries for raspberry pi. Has anyone else noticed this or found a solution?
 

Read More...

I really appreciate the reply David.

I will look out for those messages, but I don't know that I saw the same last time I used it.

Sounds like maybe time to sniff serial messages with socat and tee or github.com/geoffmeyers/interceptty

Read More...

More of an update. The LX200R is really just the optical tube. The base is just a LX200GPS. Playing with it a few more nights I've found the following:

  • Sync and Slews give the correct coordinates to the mount. The mount is really at those coordinates
  • The position that indi/ekos/kstars thinks the mount get an offset. This varies from 10' to 35' in both RA and DEC. So if I do a sync it syncs the telescope correct (as in the telescope itself on the handpad shows it correct), however the position in indi/ekos/kstars automatically jumps back off.
Not sure why this is, my first thought is some J2000 <-> JNOW conversion when it shouldn't but I currently do not know.

Has anyone else with a LX200GPS experience such an issue?

Read More...

It is my guess that toupcam doesn't work on armv6l (raspberry pi zero w) maybe because of the binaries parts of libtoupcam.

I tried a orange pi zero lts(armv7l) and it seems to be working good there.

Read More...

Hello,

In the past I've successfully used indi_toupcam_ccd in raspberry pi 4. I was trying to use it on raspberry pi zero w and I get sigfaults. This is with the astroberry apt repository, or if I build from git repo source. Does anyone know if it just doesn't work on the zero w?

$ indiserver indi_toupcam_ccd  
2021-04-18T02:32:00: startup: indiserver indi_toupcam_ccd  
2021-04-18T02:32:01: Driver indi_toupcam_ccd: stderr EOF
2021-04-18T02:32:01: Driver indi_toupcam_ccd: restart #1
Child process 8073 died


$ indi_toupcam_ccd  
Segmentation fault

 

Read More...

Our club has a 12" LX200R. I've been having a couple of issues.

1) When I sync there always seems to be a offset of 10minutes of RA. So if I sync to 12h40m12s after syncing it reports it is at 12h50m12s. This is after a manual sync or if a solver syncs it doesn't matter.

2) Sometimes when I connect it seems like the offset is even greater like 90 degrees. Usually I can park and reset a few times to get it to work normally but I still end up having issue #1. I thought it might be a time issues. I've never been able to have it use the GPS successfully from INDI. When just using the handpad it gets gps find and is able to goto objects fine. From INDI if I turn on GPS and have it use GPS I always get an error about not being able to process the time, like "2035-23-48T01:05:00"

Does anyone have any experiences with this. I originally was trying to capture the log just for #1 but I was in a hurry last night and just kept getting #2. So I only have the log for #2.

I feel like this is an operator error on my part, like I need to do some steps to make it works correctly, but I am not sure what. I am hoping that people can use this remotely so I hope the steps don't involving having to physically use the handpad first before connecting, but what to do would be good to know at least for when people are on site to use.

Thank you.

File Attachment:

File Name: log_23-46-50.txt
File Size: 47 KB


Read More...

I posted this issue on github. I believe the issue is because the indi driver sets IDLE and not OK similar to what I've read in the below forum post regarding fcusb shoestring driver.
github.com/indilib/indi/issues/1233

indilib.org/forum/focusers-filter-wheels...-3-3-3.html?start=12

Read More...

I've been trying to get autofocus to work using a Meade microfocuser on a Meade LX200R with INDI and Ekos/KStars. When running autofocus it says moving focus for 100ms and does nothing after that. Like it is waiting for some feedback. Has anyone had luck using autofocus with the microfocuser? The focus in and out buttons work (I can hear the focus motor turn), but autofocus seems to just wait for the focuser response or something. I've tried both GPS and Autostar versions of LX200 mount drivers with similar results.

Read More...