Tom Gibson replied to the topic 'Re:Installing INDI/KSTARS-EKOS on a NanoPC-T4' in the forum. 1 month ago

tightvnc seems popluar, I run vnc4server, but I couldn't find any thing specific for your combination.
This is a bit off the wall, but this blog might be a resource for you.
tech.scargill.net/nanopc-t4-from-friendlyarm/#more-9931
He just got his nanopc-t4 & install lubuntu and last post had run into your dbus issue.
Could let him know the fix and ask him which vnc server he is using.
/Tom

Read More...

Tom Gibson replied to the topic 'Installing INDI/KSTARS-EKOS on a NanoPC-T4' in the forum. 1 month ago

Is the basic setup as you think it is and getting through any firewall?
If you have something like telnet on the MAC client.
[tg@tcup]$ telnet obs 5905
Trying 192.168.1.108...
Connected to obs.
Escape character is '^]'.
RFB 003.008
Also some clients only need the last digit of the port #.
/Tom

Read More...

Tom Gibson thanked Jim in topic Upgrade INDI Web Manager Now 2 months ago
the.cakemaker thanked Tom Gibson in topic Moon-tracking 2 months ago
Tom Gibson replied to the topic 'Moon-tracking' in the forum. 2 months ago

Any documentation on the EQ6-R mount?
A outline from the Losmandy Gemini controller doc
- The modeling information is stored in the controllers non-volatile memory.
- Powering on offers different startup options. Powering on for the first time or after a CMOS reset
only Cold Start is offered.
- Cold Start Required if was mount moved. Deletes any stored model & positional info. Requires
New location and time be entered.
- Warm Start Mount same position, perhaps clutches released, OTA moved. retains model but resets
position to CWD & polar orientation.
- Warm Restart Mount & OTA same. Modeling & position information retained, mount ready for use.

Read More...

Tom Gibson replied to the topic 'Installing INDI/KSTARS-EKOS on a NanoPC-T4' in the forum. 2 months ago

Worth a post if not already a known problem.
Search Results
Web results
Lubuntu - Ubuntu Forums
ubuntuforums.org/tags.php?tag=lubuntu

Tom

Read More...

Tom Gibson replied to the topic 'Losing stars when guiding' in the forum. 2 months ago

Running on Fedora, these are the packages that got picked up yesterday evening.
Upgraded:
indi-gpsd-bleeding.x86_64 1.7.3-7.1
kstars-bleeding.x86_64 2.9.6-8.1
libapogee.x86_64 3.1-15.1
Did not see any change in the results, but the log captures guiding calibration.
Just to repeat, images are good without any guiding, The first attachment is a 2 minute exposure
unguided. After attempting pulse guiding 10 second exposures are streaked.
I could attempt installing PHD2 if that would help isolate.

Read More...

Tom Gibson replied to the topic 'Losing stars when guiding' in the forum. 2 months ago

Setting up for the first time and also having some guiding issue. My problem appears related to pulse guiding. Tried changing just the via setting in the guider and the pulse yes/no in the indi mount control and it works well. Using the same settings with pulse guiding and things go badly wrong.
Take 15 second exposures without guiding, and the stars are fine.
Start guiding calibration which usually fails and after that just, streaks in subsequent 15 second images.
The stop button in guiding does not help, it seems almost as if the mount is now tracking at a different rate.
I have been parking the mount and restarting to reset back to the unguided state and being able to obtain an image again.
When calibrating it logs a message related to RA and the star stays in the box.
After logging the DE message the stars start drifting by and the box position seems unrelated to the stars.
It has managed to calibrate a couple of times somehow but with the same result regarding the image not being usable.

I assumed it was my setup/settings, then thought it might be related to the mount driver after discovering the ST-4 cable worked well but seeing the above reports we might have something in common. I'll attach a log to see if it helps.
/Tom

Read More...

Tom Gibson replied to the topic 'Help communicating with focuser' in the forum. 5 months ago

I never did solve it. Sent them a few email asking for advice including logs showing failing mid test under Windows using their test program. Asked for a RMA to return it but no response to that. I really was left thinking the device might be defective but since you're having a similar issue perhaps it is worth trying again. I put mine in a bag out of sight. Instead I built a controller with a stepping motor using Robert Brown's 1st gen Arduino focusPro for linux , excellent project and support.
If you are able to, downloading and run their Windows test program might show something, I could pull mine out and compare with you.
Regards
Tom

Read More...

Tom Gibson replied to the topic 'First light INDI Driver for ES PMG-Eight/G11' in the forum. 8 months ago

I have a PMC-Eight EX02S setup using ascom over wifi, stuck indoors for a while. So could only do limited testing,
but if it would be of use for basic slew and track rates.

Read More...

Tom Gibson replied to the topic 'Help communicating with focuser' in the forum. 8 months ago

Looking to see if getting cdc_acm to unbind from ttyACM0 after connecting would be an approach. Have not yet found a working method, will pick up again later.

Read More...

Tom Gibson replied to the topic 'Help communicating with focuser' in the forum. 8 months ago

You are correct. This morning the reboot was around 10AM, prior to that there were ModemManager messages but not after making the rules.d change. ModemManager might also have been having trouble grabbing the device.
Jan 16 14:35:42 chai ModemManager[762]: <warn> Could not grab port (tty/ttyACM1): 'Cannot add port 'tty/ttyACM1', unhandled serial type'
Jan 16 14:38:16 chai ModemManager[762]: <info> (tty/ttyACM1): released by modem /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1
Another party is:
Jan 17 10:14:29 chai kernel: cdc_acm 1-1:1.0: ttyACM0: USB ACM device
Jan 17 10:14:29 chai /usr/libexec/gdm-x-session[2850]: (II) config/udev: Adding input device (unnamed) (/dev/ttyACM0)

lsof indicates it might be related to the gnome virtual file system:
[root@chai tg]# lsof /dev/ttyACM0
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
While issuing lsof as user provides no output, no error

Read More...

Tom Gibson replied to the topic 'Help communicating with focuser' in the forum. 8 months ago

Thank you.
I created the entry and rebooted with the same results. Confirmed that the
connection does seem to be on ttyACM0 as indicated in the INDI Control Panel and
as shown below. I want to look into if I can associate the cdc_acm driver in the
dmesg log with the control panel's Exec: indi_usbfocusv3_focus. If that seems okay
might try locating some kind of diagnostic to see if that provides any insight as to
whether or not the focuser is responsive.

[root@chai tg]# dmesg -C

[tg@chai ~]$ dmesg |grep tty
[tg@chai ~]$ dmesg |grep usb

Plug in ASI071 camera:

[tg@chai ~]$ dmesg |grep tty
[tg@chai ~]$ dmesg |grep usb
[ 457.597776] usb 1-2: new high-speed USB device number 9 using xhci_hcd
[ 457.726127] usb 1-2: New USB device found, idVendor=04b4, idProduct=6572
[ 457.726133] usb 1-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 457.726138] usb 1-2: Product: USB2.0 Hub
[ 458.217790] usb 2-2: new SuperSpeed USB device number 6 using xhci_hcd
[ 458.231163] usb 2-2: New USB device found, idVendor=03c3, idProduct=071b
[ 458.231169] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 458.231173] usb 2-2: Product: ASI071MC Pro
[ 458.231176] usb 2-2: Manufacturer: ZWO

Plug in USB Focuser:

[tg@chai ~]$ dmesg |grep tty
[ 483.893829] cdc_acm 1-1:1.0: ttyACM0: USB ACM device

[tg@chai ~]$ dmesg |grep usb
[ 457.597776] usb 1-2: new high-speed USB device number 9 using xhci_hcd
[ 457.726127] usb 1-2: New USB device found, idVendor=04b4, idProduct=6572
[ 457.726133] usb 1-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 457.726138] usb 1-2: Product: USB2.0 Hub
[ 458.217790] usb 2-2: new SuperSpeed USB device number 6 using xhci_hcd
[ 458.231163] usb 2-2: New USB device found, idVendor=03c3, idProduct=071b
[ 458.231169] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 458.231173] usb 2-2: Product: ASI071MC Pro
[ 458.231176] usb 2-2: Manufacturer: ZWO

[ 483.714576] usb 1-1: new full-speed USB device number 10 using xhci_hcd
[ 483.842751] usb 1-1: New USB device found, idVendor=0461, idProduct=0033
[ 483.842757] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 483.842761] usb 1-1: Product: USB_Focus
[ 483.842764] usb 1-1: Manufacturer: USB̔USB_F
[ 483.894344] usbcore: registered new interface driver cdc_acm

Read More...

Tom Gibson created a new topic ' Help communicating with focuser' in the forum. 8 months ago

Just received a USB Focuser and am having difficulty communicating with it, any ideas on what I can try?
It is a local KStars/indilib on a Intel NUC box running Fedora 27.
The focuser has the power cord connected although it didn't make any difference.
The USB 2 connection cable has been changed and I have tried with the different connection speeds.
I do not know how to associate the USB port with the lsusb Bus/Device id but it appears to change between /dev/ttyACM0 and ACM1 as I change the usb connection between the box and the powered hub.
The information in the INDI Control Panel seems reasonable and I've added myself to the dialout group and tried running under root.
From the debug log it connects to the focuser but fails the handshake.

Tpm

$ lsusb
Bus 002 Device 008: ID 05e3:0612 Genesys Logic, Inc. Hub
Bus 002 Device 007: ID 05e3:0612 Genesys Logic, Inc. Hub
Bus 002 Device 009: ID 03c3:071b
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 023: ID 04f2:0909 Chicony Electronics Co., Ltd
Bus 001 Device 022: ID 2516:0017
Bus 001 Device 020: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 019: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 025: ID 04b4:6572 Cypress Semiconductor Corp.
Bus 001 Device 029: ID 0461:0033 Primax Electronics, Ltd <======
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[tg@chai]$ ls -l /dev/tty* |grep ACM
crw-rw----. 1 root dialout 166, 0 Jan 16 14:55 /dev/ttyACM0

/home/tg/.local/share/ks…18-01-16/log_14-44-17.txt
[2018-01-16T14:50:41.426 EST INFO ][ org.kde.kstars.indi] - USBFocusV3 : "[INFO] Scan complete. Found 1 port(s). "
[2018-01-16T14:50:41.426 EST DEBG ][ org.kde.kstars.indi] - < USBFocusV3 >: < SYSTEM_PORTS >
[2018-01-16T14:50:58.627 EST DEBG ][ org.kde.kstars.indi] - USBFocusV3 : "[DEBUG] Connecting to /dev/ttyACM0 "
[2018-01-16T14:50:58.627 EST DEBG ][ org.kde.kstars.indi] - USBFocusV3 : "[DEBUG] Port FD 15 "
[2018-01-16T14:50:58.628 EST DEBG ][ org.kde.kstars.indi] - USBFocusV3 : "[DEBUG] Connection successful, attempting handshake... "
[2018-01-16T14:50:58.628 EST DEBG ][ org.kde.kstars.indi] - USBFocusV3 : "[DEBUG] CMD: SWHOIS. "
[2018-01-16T14:51:01.658 EST INFO ][ org.kde.kstars.indi] - USBFocusV3 : "[ERROR] Error reading focuser ID: Timeout error. "
[2018-01-16T14:51:01.663 EST INFO ][ org.kde.kstars.indi] - USBFocusV3 : "[INFO] Error retreiving data from USB Focus V3, please ensure USB Focus V3 controller is powered and the port is correct. "
[2018-01-16T14:51:01.664 EST DEBG ][ org.kde.kstars.indi] - USBFocusV3 : "[DEBUG] Handshake failed. "
[2018-01-16T14:51:01.664 EST DEBG ][ org.kde.kstars.ekos] - USBFocusV3 is disconnected.


~/.indi/USBFocusV3_config.xml

<INDIDriver>
<newSwitchVector device='USBFocusV3' name='DEBUG'>
<oneSwitch name='ENABLE'>
On
</oneSwitch>
<oneSwitch name='DISABLE'>
Off
</oneSwitch>
</newSwitchVector>
<newSwitchVector device='USBFocusV3' name='CONNECTION_MODE'>
<oneSwitch name='CONNECTION_SERIAL'>
On
</oneSwitch>
<oneSwitch name='CONNECTION_TCP'>
Off
</oneSwitch>
</newSwitchVector>
<newTextVector device='USBFocusV3' name='DEVICE_PORT'>
<oneText name='PORT'>
/dev/ttyACM0
</oneText>
</newTextVector>
<newSwitchVector device='USBFocusV3' name='DEVICE_BAUD_RATE'>
<oneSwitch name='9600'>
On
</oneSwitch>
<oneSwitch name='19200'>
Off
</oneSwitch>
<oneSwitch name='38400'>
Off
</oneSwitch>
<oneSwitch name='57600'>
Off
</oneSwitch>
<oneSwitch name='115200'>
Off
</oneSwitch>
<oneSwitch name='230400'>
Off
</oneSwitch>
</newSwitchVector>
<newSwitchVector device='USBFocusV3' name='DEVICE_AUTO_SEARCH'>
<oneSwitch name='ENABLED'>
Off
</oneSwitch>
<oneSwitch name='DISABLED'>
On
</oneSwitch>
</newSwitchVector>
<newSwitchVector device='USBFocusV3' name='DEBUG_LEVEL'>
<oneSwitch name='DBG_ERROR'>
On
</oneSwitch>
<oneSwitch name='DBG_WARNING'>
On
</oneSwitch>
<oneSwitch name='DBG_SESSION'>
On
</oneSwitch>
<oneSwitch name='DBG_DEBUG'>
Off
</oneSwitch>
</newSwitchVector>
<newSwitchVector device='USBFocusV3' name='LOGGING_LEVEL'>
<oneSwitch name='LOG_ERROR'>
On
</oneSwitch>
<oneSwitch name='LOG_WARNING'>
On
</oneSwitch>
<oneSwitch name='LOG_SESSION'>
On
</oneSwitch>
<oneSwitch name='LOG_DEBUG'>
Off
</oneSwitch>
</newSwitchVector>
<newSwitchVector device='USBFocusV3' name='LOG_OUTPUT'>
<oneSwitch name='CLIENT_DEBUG'>
On
</oneSwitch>
<oneSwitch name='FILE_DEBUG'>
Off
</oneSwitch>
</newSwitchVector>
<newNumberVector device='USBFocusV3' name='Presets'>
<oneNumber name='PRESET_1'>
0
</oneNumber>
<oneNumber name='PRESET_2'>
0
</oneNumber>
<oneNumber name='PRESET_3'>
0
</oneNumber>
</newNumberVector>
<newSwitchVector device='USBFocusV3' name='USEJOYSTICK'>
<oneSwitch name='ENABLE'>
Off
</oneSwitch>
<oneSwitch name='DISABLE'>
On
</oneSwitch>
</newSwitchVector>
<newTextVector device='USBFocusV3' name='JOYSTICKSETTINGS'>
<oneText name='Focus In'>
BUTTON_1
</oneText>
<oneText name='Focus Out'>
BUTTON_2
</oneText>
<oneText name='Abort Focus'>
BUTTON_3
</oneText>
</newTextVector>
</INDIDriver>

Read More...

Tom Gibson replied to the topic 'First light INDI Driver for ES PMG-Eight/G11' in the forum. 9 months ago

Mike
I recently ordered a EXOS2-GT with PMC-Eight (no handset) from Explore Scientific. I'd like to use it with Kstars if the mount driver is available and can also accomodate that mount. I think I read that it is mechanically like the Bresser Exos-2, Meade LXD-75.

Tom

Read More...

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!