The ASI294 can work in two ADC depth modes , 14 bits or 12 bits, changing that mode changes the "gray level" of depth and you can get 16386 or 4096 respectively, then the RAW16 format scales those levels to 16Bits (0 - 655536).
The ADC mode of 14 or 12 Bits can be selected with certain parameters in the ASCOM driver, my question is if in the INDI driver it can also be modified or it always uses the ADC 16? Mode.
I have an ASI294 too. I'm using offset of 8 (default for the ASI294 in ASCOM platform) and works fine.
Changing the subject.... Have you notice that in the information tab Image of the Ekos windows when you camera is connected, that the ADC depth parameter is 12 BITS? Is it normal for a 14 bits camera? Does this affect in some way the bit depth of the raw image?
Only by the standar apt-get update and apt-get upgrade.
Hi Kaczorek. I has updated and upgrated from version 1.1.0 and now many things stoped work. I can't start VAP, hwclock and bind the serial port to the Bluetooth adapter anymore from rc.local. When I run the commands in the terminal I get the messages "permission denied".
Any suggestion? Thanks
That's it!!! Just adding '&' at the end of the hwclock -s makes work it!
I'm having problems with my RTC too. I bought a ds3231 and I can not do system synchronization with RTC.
I tried everything, every tutorial you share on these topics and nothing.
Now my RTC keeps the time correctly, but I can not synchronize with the system, even if I use hwclock -s in the rc.local file. In fact, I think that by adding the two lines to the rc.local file, this cause stops working rc.local or something like that since the VAP stopped working after that (there is a line of code to activate the VAP in rc. local).
The only way to synchronize RTC with the system time is by typing sudo hwclock -s in the terminal: /
Ihoujin, I changed the MAC Address to my EQ-BT in the rc.local and now everything is running perfectly, even using the on board BT device en my RPi3B+!!!!
I don't have to use a BT dondle.
I think the key is to uninstall modemmanager as you told me.
I'm very happy, my mount can be run wirelessly now, one less cable to worry about.
THANKS THANKS THANKS!!
Thanks for the tips Ihoujin.
I unistalled modemmanger and then I tried to connect mi BT device and works fine binding to rfcomm0. Thats was great!
To automatize the connection after boot I added the entry in my rc.local file and restart the Astroberry but it doesn't work, the BT doen't connect automatically and I have to bind manualy to a rfcomm to get work it.
Question: The MAC address in the entry is the MAC of my BT adapter (connected via USB to astroberry) or the MAC of the BT device? (connected to mount)
Hi Kaczorek, I'm using a RPi3B+ and yes, I've already paired the devices, but I can't connect to the mount and an error message appears when I check the information of the connected serial port in the bluetooth manager "blueman exception: can't connect rfcomm socket".
Hi, I'm trying to connect my Synta mount using EQMOD via bluetooth but it´s impossible! I tried with a dondle and the on board bluetooth but still can't connect.
Anyone had has success with this?