Thomas Mason created a new topic ' how not to debayer guide camera' in the forum. 2 weeks ago

I am using a QHY5III562c as a guide camera with an IR pass filter to try and reduce my sensitivity to seeing. This camera is designed with good IR sensitivity and the bayer filter passes IR to all pixels (ie it is monochrome in IR and color in visible. Using the internal ekos guider is there a way to disable debayering so as to preserve full resolution of the monochrome image? Is there something I can put into the Bayer info setting in the camera control panel that will cause it to skip debayering?

Read More...

Thomas Mason created a new topic ' weather module source of data' in the forum. 1 month ago

I have setup weewx and am pulling weather data from my netatmo which has rain, wind, plus the usuals temperature, pressure, humidity as well. I also have a pegasus powerbox advance which has a temperature and humidity sensor to use for controlling dew heaters, The weather module seesm to toggle between the two source and the temperatures don't always agree so it is a bit of an annoyance. Is there a way to tell ekos to only use one data source?

Read More...

This is now doable using weewx:

indilib.org/forum/development/11922-new-weewx-json-driver.html

Install weewx following the very thorough documentation at www.weewx.com/

When configuring select simulator for sensor type. Stop the process:

sudo /etc/init.d/weewx stop

delete the initial setup:

thomas@plutoniborg:~/Downloads$ sudo rm -r /var/lib/weewx
thomas@plutoniborg:~/Downloads$ sudo rm -r /var/www/html/weewx

Install the netatmo driver following the instructions at github.com/bricebou/weewx-netatmo

You will need to setup an app at dev.netatmo.com to get the needed keys etc.

You can then restart weewx:

sudo /etc/init.d/weewx start

I installed apache and setup to serve weewx per the weewx instructions.

Once the web page is working you can install the json plugin which writes the file the indi driver needs

I had to tweak netatmo.py because I have two main units so replaced the wildcard * in the sensor map with the appropriate device ID numbers.

I also didn't get barometric pressure initially because the [min,max] in weewx.conf was set to to high a min value.

checking the syslog gave the needed info for both of theses issues.

Read More...

Thomas Mason replied to the topic 'New WeeWX JSON driver' in the forum. 1 month ago

the xml file doesn't exist which I guess reflects the absence of the driver. Not sure how the timing fits for ppa

Read More...

Thomas Mason replied to the topic 'New WeeWX JSON driver' in the forum. 1 month ago

I am setting up to use weewx for my netatmo weather station. I have the netatmo setup working with weewx and can view the data correctly formatted on the weewx webpage. Installed the weewx-json plugin and it is generating a json file, first bit is:

thomas@plutoniborg:~/Downloads$ cat /var/www/html/weewx/weewx.json
{
"station":
{
"location": "Santa Fe, NM",
"latitude": 35.67415,
"longitude": -105.92701,
"altitude (meters)": 2200.0,
"link": ""
},
"generation":
{
"time": "Sat, 20 Aug 2022 13:00:00 MDT",
"generator": "weewx 4.8.0"
},
"current":
{
"temperature": {"value": 15.799999999999999, "units": "°C"},
"dewpoint": {"value": 12.916316531130608, "units": "°C"},
"humidity": {"value": 83.0, "units": "%"},
"heat index": {"value": 15.602777777777774, "units": "°C"},
"wind speed": {"value": 8.000019883927573, "units": "km/h"},
"wind gust": {"value": 23.000057166291775, "units": "km/h"},
"wind direction": {"value": 244.0, "units": "°"},
"wind chill": {"value": 15.799999999999999, "units": "°C"},
"rain rate": {"value": 0.08080000000000001, "units": "cm/h"},
"inside temperature": {"value": 23.7, "units": "°C"},
"inside humidity": {"value": 46.0, "units": "%"},
"void_end": null
},
However when I try and add the weather device it doesn't appear as an option. I can add it as an Aux both it doesn't seem to work.

[2022-08-20T13:10:35.374 MDT INFO ][ org.kde.kstars.ekos] - "Starting INDI services..."
[2022-08-20T13:10:35.394 MDT WARN ][ org.kde.kstars.indi] - Driver "WeewxJSON" failed to start. Retrying in 5 seconds...
[2022-08-20T13:10:40.146 MDT WARN ][ org.kde.kstars.indi] - Driver "WeewxJSON" failed to start. Retrying in 5 seconds...
[2022-08-20T13:10:45.105 MDT WARN ][ org.kde.kstars.indi] - Driver "WeewxJSON" failed to start. Retrying in 5 seconds...

Read More...

It seems to work OK when I bring it inside - maybe a temperature issue?

Read More...

I rebuild indi and redid setup and now camera does connect but after a few images it stops:

Aug 13 12:55:41 allsky [INFO] MainProcess allsky.run() #741: Total time since last exposure 15.0057 s
Aug 13 12:55:45 allsky [INFO] MainProcess indi.newMessage() #218: new Message 2022-08-13T18:55:45: [ERROR] Exposure failed after 3 attempts.
Aug 13 12:55:49 allsky [INFO] MainProcess allsky.run() #607: Camera last ready: 22.3s
Aug 13 12:55:49 allsky [INFO] MainProcess allsky.run() #608: Exposure state: ALERT
Aug 13 12:55:49 allsky [INFO] MainProcess allsky.detectNight() #853: Sun altitude: 68:37:59.4
Aug 13 12:55:49 allsky [INFO] MainProcess allsky.detectMoonMode() #870: Moon altitide: -54:51:10.5, phase 95.7%
Aug 13 12:55:49 allsky [INFO] MainProcess indi.getCcdTemperature() #422: Sensor temperature: 46.6
Aug 13 12:55:49 allsky [INFO] MainProcess allsky._queueManualTasks() #1441: Checking for manually submitted tasks
Aug 13 12:55:59 allsky [INFO] MainProcess allsky.run() #607: Camera last ready: 32.3s
Aug 13 12:55:59 allsky [INFO] MainProcess allsky.run() #608: Exposure state: ALERT
Aug 13 12:55:59 allsky [INFO] MainProcess allsky.detectNight() #853: Sun altitude: 68:38:17.1
Aug 13 12:55:59 allsky [INFO] MainProcess allsky.detectMoonMode() #870: Moon altitide: -54:52:39.1, phase 95.7%
Aug 13 12:55:59 allsky [INFO] MainProcess indi.getCcdTemperature() #422: Sensor temperature: 46.6
Aug 13 12:55:59 allsky [INFO] MainProcess allsky._queueManualTasks() #1441: Checking for manually submitted tasks
Aug 13 12:56:09 allsky [INFO] MainProcess allsky.run() #607: Camera last ready: 42.3s

Read More...

I updated in order to get the new focus model and now it seems to crash when trying to connect to my ASI290mm mini camera:

Aug 13 10:27:06 allsky [INFO] MainProcess allsky._initialize() #335: Found 1 CCDs
Aug 13 10:27:06 allsky [WARNING] MainProcess allsky._initialize() #338: Connecting to device ZWO CCD ASI290MM Mini
Aug 13 10:27:07 allsky [INFO] MainProcess indi.newMessage() #218: new Message 2022-08-13T16:27:06: [ERROR] Error connecting to the CCD (ASI_ERROR_CAMERA_REMOVED).
Aug 13 10:27:07 allsky [INFO] MainProcess miscDb.addCamera() #44: Camera DB ID: 1
Aug 13 10:27:07 allsky [INFO] MainProcess indi.configureDevice() #404: Setting switch DEBUG
Aug 13 10:27:07 allsky [INFO] MainProcess indi.newSwitch() #205: new Switch CONNECTION for device ZWO CCD ASI290MM Mini
Aug 13 10:27:07 allsky [INFO] MainProcess indi.newSwitch() #205: new Switch DEBUG for device ZWO CCD ASI290MM Mini
Aug 13 10:27:08 allsky [INFO] MainProcess indi.updateCcdBlobMode() #228: Set BLOB mode
Aug 13 10:27:09 allsky [INFO] MainProcess indi.configureDevice() #404: Setting switch CCD_FRAME_TYPE
Aug 13 10:28:14 allsky [ERROR] MainProcess allsky.unhandled_exception() #36: An uncaught exception occurred:
Aug 13 10:28:14 allsky [ERROR] MainProcess allsky.unhandled_exception() #37: Type: <class 'indi_allsky.exceptions.TimeOutException'>
Aug 13 10:28:14 allsky [ERROR] MainProcess allsky.unhandled_exception() #38: Value: Timeout finding control CCD_FRAME_TYPE
Aug 13 10:28:14 allsky [ERROR] MainProcess allsky.unhandled_exception() #43: ' File "/home/thomas/indi-allsky/allsky.py", line 128, in <module>\n action_func(*args_list, **kwargs_dict)\n'
Aug 13 10:28:14 allsky [ERROR] MainProcess allsky.unhandled_exception() #43: ' File "/home/thomas/indi-allsky/indi_allsky/allsky.py", line 588, in run\n self._initialize()\n'
Aug 13 10:28:14 allsky [ERROR] MainProcess allsky.unhandled_exception() #43: ' File "/home/thomas/indi-allsky/indi_allsky/allsky.py", line 363, in _initialize\n self.indiclient.setFrameType(self.ccdDevice, \'FRAME_LIGHT\') # default frame type is light\n'
Aug 13 10:28:14 allsky [ERROR] MainProcess allsky.unhandled_exception() #43: ' File "/home/thomas/indi-allsky/indi_allsky/indi.py", line 266, in setFrameType\n self.configureDevice(ccd_device, frame_config)\n'
Aug 13 10:28:14 allsky [ERROR] MainProcess allsky.unhandled_exception() #43: ' File "/home/thomas/indi-allsky/indi_allsky/indi.py", line 405, in configureDevice\n self.set_switch(device, k, on_switches=v[\'on\'], off_switches=v.get(\'off\', []))\n'
Aug 13 10:28:14 allsky [ERROR] MainProcess allsky.unhandled_exception() #43: ' File "/home/thomas/indi-allsky/indi_allsky/indi.py", line 670, in set_switch\n c = self.get_control(device, name, \'switch\')\n'
Aug 13 10:28:14 allsky [ERROR] MainProcess allsky.unhandled_exception() #43: ' File "/home/thomas/indi-allsky/indi_allsky/indi.py", line 644, in get_control\n raise TimeOutException(\'Timeout finding control {0}\'.format(name))\n'

Read More...

Thomas Mason replied to the topic 'Esatto on new ubuntu linux' in the forum. 2 months ago

The boot log was the key. I removed brltty (which is braille display) and /dev/ttyUSB1 now became visible and connects me to the esatto. Now if only I could figure out why the pegasus port often won't connect with the:

2022-07-26T02:26:53: [WARNING] Port /dev/serial/by-id/usb-Pegasus_Astro_PPBADV_revB_PPBA5UXVM0-if00-port0 is already used by another driver or process.

error I would be all set.

This was probably similar to the cases observed by others where gpsd and vantage were conflicting.

Read More...

Thomas Mason replied to the topic 'Esatto on new ubuntu linux' in the forum. 2 months ago

Here is what I get in the boot log:

Jul 24 21:26:03 mele kernel: usb 1-1.4: new full-speed USB device number 6 using xhci_hcd
Jul 24 21:26:03 mele kernel: mc: Linux media interface: v0.10
Jul 24 21:26:03 mele kernel: videodev: Linux video capture interface: v2.00
Jul 24 21:26:03 mele systemd-udevd[341]: Using default interface naming scheme 'v249'.
Jul 24 21:26:03 mele kernel: usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
Jul 24 21:26:03 mele kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 24 21:26:03 mele kernel: usb 1-1.4: Product: CP2102N USB to UART Bridge Controller
Jul 24 21:26:03 mele kernel: usb 1-1.4: Manufacturer: Silicon Labs
Jul 24 21:26:03 mele kernel: usb 1-1.4: SerialNumber: 286da66d47a6e9118cc0dda44458cd37
Jul 24 21:26:03 mele kernel: mei_me 0000:00:16.0: enabling device (0000 -> 0002)
Jul 24 21:26:03 mele mtp-probe[362]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.1"
Jul 24 21:26:03 mele mtp-probe[362]: bus: 1, device: 4 was not an MTP device
Jul 24 21:26:03 mele systemd-udevd[352]: mmcblk1boot0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/de>
Jul 24 21:26:03 mele systemd-udevd[343]: mmcblk1boot1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/de>
Jul 24 21:26:03 mele kernel: usbcore: registered new interface driver usbserial_generic
Jul 24 21:26:03 mele kernel: usbserial: USB Serial support registered for generic
Jul 24 21:26:03 mele kernel: usbcore: registered new interface driver ftdi_sio
Jul 24 21:26:03 mele kernel: usbserial: USB Serial support registered for FTDI USB Serial Device
Jul 24 21:26:03 mele kernel: ftdi_sio 1-1.1:1.0: FTDI USB Serial Device converter detected
Jul 24 21:26:03 mele kernel: usb 1-1.1: Detected FT-X
Jul 24 21:26:03 mele kernel: proc_thermal 0000:00:04.0: enabling device (0000 -> 0002)
Jul 24 21:26:03 mele systemd-udevd[330]: mmcblk1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/m>
Jul 24 21:26:03 mele kernel: Intel(R) Wireless WiFi driver for Linux
Jul 24 21:26:03 mele kernel: iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
Jul 24 21:26:03 mele systemd-udevd[327]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvm>
Jul 24 21:26:03 mele systemd-udevd[345]: mmcblk1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/m>
Jul 24 21:26:03 mele systemd-udevd[339]: mmcblk1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/m>
Jul 24 21:26:03 mele kernel: iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
Jul 24 21:26:03 mele kernel: iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
Jul 24 21:26:03 mele kernel: iwlwifi 0000:00:14.3: loaded firmware version 66.f1c864e0.0 QuZ-a0-hr-b0-66.ucode op_mode iw>
Jul 24 21:26:03 mele systemd[1]: Found device /dev/disk/by-uuid/DE87-8E65.
Jul 24 21:26:03 mele systemd-udevd[343]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/n>
Jul 24 21:26:03 mele kernel: usb 1-1.1: FTDI USB Serial Device converter now attached to ttyUSB0
Jul 24 21:26:04 mele mtp-probe[405]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.1"
Jul 24 21:26:04 mele mtp-probe[405]: bus: 1, device: 4 was not an MTP device
Jul 24 21:26:04 mele kernel: usbcore: registered new interface driver cp210x
Jul 24 21:26:04 mele kernel: usbserial: USB Serial support registered for cp210x
Jul 24 21:26:04 mele kernel: cp210x 1-1.4:1.0: cp210x converter detected
Jul 24 21:26:04 mele kernel: usb 1-1.4: cp210x converter now attached to ttyUSB1
Jul 24 21:26:05 mele brltty[532]: USB configuration set error 16: Device or resource busy
Jul 24 21:26:05 mele brltty[532]: brltty: USB configuration set error 16: Device or resource busy
Jul 24 21:26:05 mele brltty[532]: USB interface in use: 0 (cp210x)
Jul 24 21:26:05 mele brltty[532]: brltty: USB interface in use: 0 (cp210x)
Jul 24 21:26:05 mele kernel: usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1
Jul 24 21:26:05 mele kernel: fbcon: i915drmfb (fb0) is primary device
Jul 24 21:26:05 mele kernel: cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1
Jul 24 21:26:05 mele kernel: cp210x 1-1.4:1.0: device disconnected
Jul 24 21:26:05 mele brltty[532]: USB control transfer error 32: Broken pipe
Jul 24 21:26:05 mele brltty[532]: brltty: USB control transfer error 32: Broken pipe
Jul 24 21:26:05 mele brltty[532]: unexpected CP2101 baud divisor size: 0
Jul 24 21:26:05 mele brltty[532]: brltty: unexpected CP2101 baud divisor size: 0
Jul 24 21:26:05 mele brltty[532]: USB control transfer error 32: Broken pipe
Jul 24 21:26:05 mele brltty[532]: brltty: USB control transfer error 32: Broken pipe
Jul 24 21:26:05 mele brltty[532]: brltty: unable to set CP2101 baud divisor: Broken pipe
Jul 24 21:26:05 mele brltty[532]: unable to set CP2101 baud divisor: Broken pipe
Jul 24 21:26:05 mele systemd-logind[625]: Watching system buttons on /dev/input/event6 (BRLTTY 6.4 Linux Screen Driver Ke>
Jul 24 21:26:05 mele dbus-daemon[569]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.ser>
Jul 24 21:26:05 mele kernel: Console: switching to colour frame buffer device 240x67
Jul 24 21:26:05 mele kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
Jul 24 21:26:05 mele ModemManager[683]: <info> [base-manager] port ttyUSB1 released by device '/sys/devices/pci0000:00/0>
Jul 24 21:26:05 mele ModemManager[683]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00>
Jul 24 21:26:05 mele audit[680]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=680 comm="cu

so it looks like it sets up /dev/ttyUSB1 but then runs into trouble - I don't see the device when I log in.

Read More...

Thomas Mason replied to the topic 'Esatto on new ubuntu linux' in the forum. 2 months ago

I have a 12V power connected since I found USB alone was not sufficient. I also tried direct connection to mini pc without going through pegasus. It looks like the kernel isn't recognizing it and setting up a /dev/ even through it enumerates properly as CP210x and the kernel mod is present?

Read More...

Thomas Mason replied to the topic 'Esatto on new ubuntu linux' in the forum. 2 months ago

Nothing here that looks like that:

thomas@mele:~$ ls -l /dev | grep USB
crw-rw-rw- 1 root dialout 188, 0 Jul 24 21:33 ttyUSB0
thomas@mele:~$ ls -l /dev/vantage
ls: cannot access '/dev/vantage': No such file or directory

Read More...

Thomas Mason replied to the topic 'Esatto on new ubuntu linux' in the forum. 2 months ago

gpsd not installed so nothing removed

Read More...

Thomas Mason created a new topic ' Esatto on new ubuntu linux' in the forum. 2 months ago

I have been using an Esatto focuser successfully on stellarmate for quite sometime. I am migrating to ekos/kstars on a new mele mini pc running ubuntu 22.04 and am having trouble sorting out port/connection. It shows up if i lsusb:

Bus 001 Device 005: ID 10c4:ea60 Silicon Labs CP210x UART Bridge

and that comes and goes as I unplug the cable. If is lsub all I see is:

usb-Pegasus_Astro_PPBADV_revB_PPBA5UXVM0-if00-port0

nothing for the esatto. The Pegasus astro has connected although it often seems to think another device is using the port?

Read More...