Get Connected!

Come and join our community. Expand your network and get to know new people!

Sorry, we currently have no events.
View All Events

Will an old v1.7 Raspberry Pi camera work with indi-allsky?

I am also building indi-allsky on an Rpi 3 Bullseye installation. Judging from the time to build it, I may be a little too ambitious!

Thanks

Read More...

Gary McKenzie created a new topic ' Fujifilm cameras?' in the forum. 3 hours 34 minutes ago

Hi,
I'm thinking about buying a new Fujifilm camera - model as yet undetermined. I see that Indi appears to have drivers for Fuji cameras. Can anyone confirm which models are supported or not supported, and that the driver has no significant issues?
TIA
Gary

Read More...

I'm trying to connect an ASI294MC Pro with 'ZWO Camera 1'.
Sometimes it works but sometimes not.
When the driver could not connect to the camera, I changed to 'ZWO CCD' which will get it work.
What are these 'ZWO Camera 1/2/3' meaning for?

Read More...

Try to use ZWO CCD instead of ZWO Camera 1/2/3
I'm also fucked with these 1/2/3, and confused what ware they meaning for.

Read More...

Nope - sorry. I ended up doing a support ticket and they said it didn't work.

SM isn't the most secure thing so I guess I understand the reluctance to all it to be on a public network but I wish they'd put in a side door so people with VMs can still get at it.

Read More...

Confirmed all working on Ubuntu Mate 22.04

Read More...

Pete,
These are small systems and there is just a 100k swap file which is next to nothing. Just try creating a 4GB swap partition for the OS to use and see if it helps.
/Tom

Read More...

I'd be interested if anyone has made this work. I've tried and failed.

It looks to me that the Stellarmate App is only looking at the local network and that would have to be addressed to get it to work.

Read More...

Nice catch, I notified Jasem and he said he will fix it.

Read More...

Hmmm... what is strange is that this cam is working when used with Ekos... even is qhy_ccd_test fails.

I will cont. test this setup.



Read More...

Thank you for that tip.

However that didn't fix the issue. I'm still getting the same unmet dependencies / broken packages message.

Read More...

Because of previous failed install attempts, I had to start with

sudo apt update --fix-missing
sudo dpkg --configure -a

Then the exact steps you did worked for me.

Read More...

Hi Nigel,

The clicked current and write is an Ekos thing (Indi control panel, mount, site management, park position "Current" "Default" "Write Data" "Purge Data". I presumed you can move the mount to a park position, click current, then write data and it should make that the park position. I *think* this is actually for custom park positions.

When I connect to the mount, it shows up at Polaris. But there is a feature under Eqmod where you can right click anywhere on the screen, select Eqmod mount, then Goto & Set as Park Position. When I did this, the mount would slew to some place way way away from Polaris. I don't know why.

The good news, apparently, is that I reprogrammed the AstroEQ controller to invert DEC, and the mount now appears to be slewing in the correct direction. I had assumed inverting DEC in Indi control panel would have done this, but apparently not. Hopefully, skies will be clear for real testing!

Paul

Read More...

Not sure, just tested with QHY268M without issues.

QHY Test CCD using SingleFrameMode, Version: 1.00
-- qhyccd.cpp param
QHYCCD|QHYCCD.CPP|InitQHYCCDResource()|START
QHYCCD|QHYCCD.CPP|InitQHYCCDResource|auto_detect_camera:false,call InitQHYCCDResourceInside
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|START
QHYCCD|QHYCCD.CPP|libusb_version 1.0.23.11523
QHYCCD|QHYCCD.CPP|libusb_init(libqhyccd_context) called...
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|numdev set to 0
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|END
************************** config file path  22.5.11.7 svn: 12117  ************************************
QHYCCD|QHYCCD.CPP|InitQHYCCDResource|Load ini filePath = /home/stellarmate/Projects/build/indi-qhy-Desktop-Debug  fileName = qhyccd.ini
SDK resources initialized.
Number of QHYCCD cameras found: 1 
Application connected to the following camera from the list: Index: 1,  cameraID = QHY268M-fb15d443a91ab4a6c
Open QHYCCD success.
SetQHYCCDStreamMode set to: 0, success.
InitQHYCCD success.
GetQHYCCDOverScanArea:
Overscan Area startX x startY : 0 x 0
Overscan Area sizeX  x sizeY  : 10 x 4176
GetQHYCCDEffectiveArea:
Effective Area startX x startY: 0 x 0
Effective Area sizeX  x sizeY : 10 x 4176
GetQHYCCDChipInfo:
Effective Area startX x startY: 0 x 0
Chip  size width x height     : 23.613 x 15.830 [mm]
Pixel size width x height     : 3.760 x 3.760 [um]
Image size width x height     : 6280 x 4210
This is a mono camera.
SetQHYCCDParam CONTROL_USBTRAFFIC set to: 10, success.
SetQHYCCDParam CONTROL_GAIN set to: 10, success
SetQHYCCDParam CONTROL_GAIN set to: 140, success.
Default read mode: 0 
Default read mode name PhotoGraphic DSO 
Read mode name PhotoGraphic DSO 
GetQHYCCDChipInfo in this ReadMode: imageW: 6280 imageH: 4210 
Read mode name High Gain Mode 
GetQHYCCDChipInfo in this ReadMode: imageW: 6280 imageH: 4210 
Read mode name Extend Fullwell 
GetQHYCCDChipInfo in this ReadMode: imageW: 6280 imageH: 4210 
Read mode name Extend Fullwell 2CMS 
GetQHYCCDChipInfo in this ReadMode: imageW: 6280 imageH: 4210 
SetQHYCCDParam CONTROL_EXPOSURE set to: 1, success.
SetQHYCCDResolution roiStartX x roiStartY: 0 x 0
SetQHYCCDResolution roiSizeX  x roiSizeY : 6280 x 4210
SetQHYCCDBinMode set to: binX: 1, binY: 1, success.
SetQHYCCDParam CONTROL_GAIN set to: 10, success.
ExpQHYCCDSingleFrame(pCamHandle) - start...
ExpQHYCCDSingleFrame(pCamHandle) - end...
ExpQHYCCDSingleFrame success (0).
Allocated memory for frame: 109991200 [uchar].
GetQHYCCDSingleFrame: 6280 x 4210, bpp: 16, channels: 1, success.
CancelQHYCCDExposingAndReadout success.
Close QHYCCD success.
SDK resources released.


Read More...

Hi,

1st - again congrats on this project!

this is strange - I build right now both core, libs and 3rd party drivers from github.

All successful. Mounts, etc - all working but not the driver for the qhy cams. I'm using a qhy 5 iii 178c- When I run qhy_ccd_test, I got the following


qhy_ccd_test
QHY Test CCD using SingleFrameMode, Version: 1.00
-- qhyccd.cpp param
QHYCCD|QHYCCD.CPP|InitQHYCCDResource()|START
QHYCCD|QHYCCD.CPP|InitQHYCCDResource|auto_detect_camera:false,call InitQHYCCDResourceInside
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|START
QHYCCD|QHYCCD.CPP|libusb_version 1.0.23.11397
QHYCCD|QHYCCD.CPP|libusb_init(libqhyccd_context) called...
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|numdev set to 0
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|END
************************** config file path 22.5.11.7 svn: 12117 ************************************
QHYCCD|QHYCCD.CPP|InitQHYCCDResource|Load ini filePath = /home/fritz fileName = qhyccd.ini
SDK resources initialized.
Number of QHYCCD cameras found: 1
Application connected to the following camera from the list: Index: 1, cameraID = QHY5III178C-1524fa4faea64cc25
Open QHYCCD success.
SetQHYCCDStreamMode set to: 0, success.
InitQHYCCD success.
GetQHYCCDOverScanArea:
Overscan Area startX x startY : 0 x 0
Overscan Area sizeX x sizeY : 0 x 0
GetQHYCCDEffectiveArea:
Effective Area startX x startY: 0 x 0
Effective Area sizeX x sizeY : 0 x 0
GetQHYCCDChipInfo:
Effective Area startX x startY: 0 x 0
Chip size width x height : 9.993 x 8.431 [mm]
Pixel size width x height : 2.400 x 2.400 [um]
Image size width x height : 3056 x 2048
This is a color camera.
SetQHYCCDParam CONTROL_USBTRAFFIC set to: 10, success.
SetQHYCCDParam CONTROL_GAIN set to: 10, success
SetQHYCCDParam CONTROL_GAIN set to: 140, success.
Default read mode: 0
Default read mode name STANDARD MODE
Read mode name STANDARD MODE
GetQHYCCDChipInfo in this ReadMode: imageW: 3056 imageH: 2048
SetQHYCCDParam CONTROL_EXPOSURE set to: 1, success.
SetQHYCCDResolution roiStartX x roiStartY: 0 x 0
SetQHYCCDResolution roiSizeX x roiSizeY : 3056 x 2048
SetQHYCCDBinMode set to: binX: 1, binY: 1, success.
SetQHYCCDParam CONTROL_GAIN set to: 10, success.
ExpQHYCCDSingleFrame(pCamHandle) - start...
ExpQHYCCDSingleFrame(pCamHandle) - end...
ExpQHYCCDSingleFrame success (8193).
Allocated memory for frame: 27116352 [uchar].
Segmentation fault

I have seen that in some other - older - posts - any hint?

uname -a
Linux nanopim1astro1 5.15.25-sunxi #22.02.1 SMP Sun Feb 27 09:23:25 UTC 2022 armv7l armv7l armv7l GNU/Linux

lscpu
Architecture: armv7l
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
Vendor ID: ARM
Model: 5
Model name: Cortex-A7
Stepping: r0p5
CPU max MHz: 1368.0000
CPU min MHz: 480.0000
BogoMIPS: 22.85
Flags: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm


Thanks!
Joerg

Read More...

I must be a little thick today as I still cannot get this to install on 22.04.

I am using these steps:
sudo add-apt-repository ppa:mutlaqja/ppa
sudo apt update
sudo apt install indi-full kstars-bleeding

That gives the warning of unmet packages.....Unable to correct problems, you have held broken packages.

What am I missing?

Tom

Read More...

Colours on graph changed to order in the rainbow scheme. New test still running (crash point never certain, but shows same effect - cache increases as free decreases, and eventually swap gets used.
At this point, I've no idea how long the simulation will continue, other than at some point a crash and stop of acquisition WILL occur.
Also redone the previous text file to show the plots on the same colour scheme.
Without drop_cache:



With drop_cache:


Read More...