hi!

as said before, i have up to three cameras mounted on the same scope. the idea is to take images of the same object at different scales, for instance for improving RGB. the 13" f/4 has almost the same FOV with the 1600 MM as the semi apo with the 178, so it might be worth a try. still, i need a second instance of EKOS to control it. i could as well start a second instance on the main computer, but i thought it would be charming to have a minimalistic displayless astroberry. the only problem is that i can catch the wrong SSID, and the i have trouble getting in there ...
yours wolfi

Read More...

this is what it looks like ...
yours wolfi



Read More...

hi!
i have an idea. i have a wlan spawn by my controller - TSC- in my observatory. this access point acts as the central network for retrieving camera images and so on. by now, I have a asi 1600 mm on the main scope, an as 120 MM for guiding, a canon DSLR with an old mamiya 210 mm lens and a little semi-apo with 400 mm and an asi 178 MC. the canon and the apo are mounted on the main scope. however, i cannot schedule two or three cameras independently using EKOS, right? or did i miss something?

what i did now is i installed astroberry server on a 2 GB raspi 4 and i attached the 178MC to it. on this raspi, i can run a second local instance of EKOS. however, i do not want a display on that one, so here is what i did:
- attached an e-paper that just displays the SSID and the address of the raspi 4 via a little c-program - just for feedback ...
- attached a hwclock - DS3231
- attached a momentary switch that is monitored by the c-program mentioned above. if it is pressed for 5 seconds, the raspi shuts down.

this is a very cheap solution, and if i want to see what EKOS does on that one, i can dial in via VNC.

is that something of interest for anyone else? i am in the process of making a PCB, so just let me know ...
yours wolfi

Read More...

hi!
after developing a full INDI client for my telescope controller project TSC (which uses INDI for direct control of cameras for guiding and astrometry), i have a question. i start the INDI server on the raspberry that does the telescope control, and i use it as a remote INDI server subsequently. for this purpose it would be nice to start also drivers that are not directly needed by the controller - is there a list of all available driver names in text/html format. i honestly speaking don’t want to pick each name from the Devices-pages here :D
yours wolfi

Read More...

hi!
just to close the topic - yes, i was stuck in a total rut. i did not understand that properties can be dynamically attached ... sorry for molesting you guys ...
yours wolfi

Read More...

Max13 wrote: Hi, it is my first experience with INDI system and I have a problem with guide camera (ASI120MM-S) when the mount (CEM40) is connected ttyUSB0......
Could be the same problem ?
Could be the same problem ?
I don't manage to resolve it....


hi!
let me guess. you get an error stating that exposure was started 3 times and cannot be finished?

this is a problem i know from the 120 MM. there is a workaround.
- use a USB 2 cable, NOT a USB 3 cable
- try the first exposure with 0.01 s exposure time. after that, you can do longer exposures.
- you can also try to set the camera to 8 bit depth.

maybe that helps ...
yours wolfi

Read More...

hi pep!
well - ttySx is he standard UART, the old style miniDIN 9 COM1 port hardly to be found on any computer anymore (the pi still ha it via dedicated GPIO pins, but no direct connector). the ttyACMx thing - well - i don't think that this is the problem as your cp2102/9 hooks up to ttyUSB0. maybe a try with the pi3+ might shed more light on that problem ...
yours wolfi

Read More...

hi!
i checked the doc - USB 1.1 seems to be the response from this converter, which is apparently an older model.
as far as i can tell, all is fine with your converter. so it is either a hardware failure (scarce) or a software problem ...

i am running out of suggestions, maybe someone with a better understanding of udev rules might be able to help.
... i still see the focuser as a separate device here - which is suspicious.

one idea:
- move the udev rules file to a different location so that they are not executed at startup
- reboot
- now, you cannot access /dev/ttyUSB0 UNLESS you are root OR - i hope that works - you give everyone else access to the device by typing

sudo chmod a+rw /dev/ttyUSB0

in the terminal. start kstars in the same terminal. if this works (unless i typed some BS, which is always possible), then the udev rules are the problem. this is not a remedy, by the way. next time you reboot, access is gone again ...

yours wolfi

Read More...

Wolfgang Birkfellner replied to the topic 'ASI183MM PRO Offset' in the forum. 8 months ago

hi!
true, but basically, this is the offset, isn't it? for the zwo cameras, it is reported correctly as 32xxx and if subtracted, this allows for rescaling of the 16 bit data from the raw BLOB as received by INDI ...
yours wolfi

Read More...

hi!
USB devices can also be set in the dev rules, i think ... but i have a more important question: why are you running on USB 1.1????

it should work, i am just wondering.
yours wolfi

Read More...

hi!
worth a try as well - but the dmesg log pep posted clearly states that the adapter connects to ttyUSB0 ...
yours wolfi

Read More...

Wolfgang Birkfellner replied to the topic 'ASI183MM PRO Offset' in the forum. 8 months ago

Hi! Sure?

KEYWORD: BZERO
REFERENCE: FITS Standard
STATUS: reserved
HDU: image
VALUE: real
DEFAULT: 0.0
COMMENT: zero point in scaling equation
DEFINITION: This keyword shall be used, along with the BSCALE keyword,
when the array pixel values are not the true physical values, to
transform the primary data array values to the true values using the
equation: physical_value = BZERO + BSCALE * array_value. The value field
shall contain a floating point number representing the physical value
corresponding to an array value of zero. The default value for this
keyword is 0.0.
Yours wolfi

Read More...