Where and how? On mine (downloaded a few days ago from stable) no option to show or use any tab bar.AstroNerd wrote: This is already available but only on a Linux machine, or on rpi, , you can have them all in separate windows on there, so should not be too hard to implement...on a Mac, or windows machine for that matter...
Excellent idea. I don't have the Indi Dev experience to contribute but a couple of ideas on the hardware:
1. Add an external Wi-Fi antenna (signal strength seems an issue for my RPi inside a case
2. Fan location/position: dew falls downwards so ensure the airflow is drawing in from underside and expelled ideally through a side?
Ian
Read More...
Pi 3 in a metal case (no fan) but only running mount (so probably not stretching it's processing power even for a 3)DerPit wrote:
Psamathe wrote: .
Re: Timeout Errors: It does not make much sense but playing around this morning (now using KStars in a Virtual Machine but RPi running remote IndiServer) and the timeout errors have disappeared. Previously loads of re-boots, etc. so only change is extended power off period - which makes no sense but it's working so all I can do is keep an eye on it.
Just a wild guess: Is this a Pi 4? Could it be temperature problems?
......
Yes, that is also what I'm using since years to have persistent names for my USB-to-Serial devices:
<code>
SUBSYSTEM=="tty", ACTION=="add", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", KERNEL=="ttyUSB*", SYMLINK="eqmod"
</code>
I have three of those lines, to discriminate eqmod, synscan and a Pegasus DMFC.
If you can connect, but get spurious errors now and then, that is for sure not related to the above symlink setup, I'm definitely sure you'd also get them using the native ttyUSBX name. So rather look for connection or baud rate issues, or other hardware stuff...[/quote]
Re: .rules file. Mine seems work fine (a few hrs playing around, few reboots all indoors) without the SUBSYSTEM== but with the KERNEL==
But yours "makes more sense" (to me - whilst I don't understand much Linux/udev, specifying the SUBSYSTEM as a tty seems a "safer bet"). So I experiemented and changed mine to
(hope above is correct, I had to retype as my VNC client does not seem to cut/paste nicely)SUBSYSTEM=="tty", KERNEL=="ttyUSB*", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="A104E4YQ"", MODE="0666", SYMLINK+="ttymount"
I'd previously tried both of those (got the usb-serial from a bit of search engine use) - but in both cases the symbolic persistent name was not created. Unfortunately my limited Linux knowledge is such that I don't know how to get any error logs.PDB wrote: Ok, I did a few tests.
Connecting the FTDI also creates a /dev/gpiochip device. I don't have to much knowledge on that, but I think that is a device file talking directly on USB level, nott via the usb-serial convertor which create a /dev/ttyUSB type device.
So your udev seems to link to the wrong one (which makes the ioctl go wrong, because it's not serial protocol)
I would try the SUBSYSTEM=="tty" or SUBSYSTEMS=='usb-serial' in the rules fike.
Don't forget to restart udev after every change: udevadm control --reload-rules && udevadm trigger
Paul
......
It's strange on your machine it point to a gpio (which I thought is the gpio pins on the raspberry, but I might be wrong here)
P.[/quote]
I agree. Although further down the "parent chain" it seemed to get to an FTDI device the start to gpio looked very wrong.
Do a bit more searching and I found a site suggesting
and it was the KERNEL bit (rather than SUBSYSTEMS) that interested me so I triedKERNEL=="ttyUSB[0-9]*", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{bcdDevice}=="0400", SYMLINK+="gps_int"
I don't understand this stuff so I'm just repeating bits of what others are suggesting and it looks like that seems to work - starting Ekos (with ttymount set as the serial port) seeks to not report issues and I can drive the mount (N/S/E/W - issues with everything "below the horizon" at the moment but GPS can't work indoors and still investigating cause ... but that's another issue).KERNEL=="ttyUSB[0-9]*", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="A104E4YQ", MODE="0666", SYMLINK+="ttymount"
I'm using RPi3 running Raspbian (latest version, recent update)
Tried changing MODE= to be 0777 (in case execute made any difference) - no change
Tried changing SYSTEMS to SYSTEM and error reported was
2020-09-30T15:30:15: [WARNING] Communication with /dev/ttymount @ 9600 failed. Starting Auto Search...
2020-09-30T15:30:15: [ERROR] Failed to connect to port (/dev/ttymount). Error: Port failure Error: Inappropriate ioctl for device. Check if device is connected to this port.
Full output in attached file (in case something further down is relevant), But (recognising bt beginner experience with Linux) that suggests the ttymount does link to the physical device (the FDTI USB serial adapter).Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/gpiochip3':
KERNEL=="gpiochip3"
SUBSYSTEM=="gpio"
DRIVER==""
looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0':
KERNELS=="1-1.5:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="ftdi_sio"
ATTRS{supports_autosuspend}=="1"
ATTRS{bInterfaceSubClass}=="ff"
ATTRS{interface}=="FT232R USB UART"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceClass}=="ff"
ATTRS{authorized}=="1"
ATTRS{bNumEndpoints}=="02"
ATTRS{bInterfaceProtocol}=="ff"
ATTRS{bInterfaceNumber}=="00"
PDB wrote: Hi,
on my system I use subsystem=tty and that works. (I dont use MODE parameter either but that shouldn't harm anything)
so try changing to:
SUBSYSTEMS=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="A104E4YQ", MODE="0666", SYMLINK+="ttymount"
Regards,
Paul
picciux wrote: Try to post the output of
ls -l /dev/ttymount
lrwxrwxrwx 1 root root 9 Sep 29 15:49 /dev/ttymount -> gpiochip3
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Using IndiLib on RPi, KStars/Ekos on Mac and an iEQ45 mount, I can't get persistent serial port mapping to work.
Setup rules.d as described in
https://indilib.org/support/tutorials/157-persistent-serial-port-mapping.html
astronomy.rules:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="A104E4YQ", MODE="0666", SYMLINK+="ttymount"
Although on the screen most other devices (and all other tty devices) are in yellow text but the "ttymount" is in turquoise text (so something different.tty7
tty8
tty9
ttyAMA0
ttymount
ttyprintk
ttyUSB0
uhid
uinput
020-09-29T14:19:10: [INFO] iOptron iEQ45 is online.
2020-09-29T14:19:10: [WARNING] Communication with /dev/ttymount @ 9600 failed. Starting Auto Search...
2020-09-29T14:19:10: [ERROR] Failed to connect to port (/dev/ttymount). Error: Port failure Error: Invalid argument. Check if device is connected to this port.
(Beginner question, sorry)
I'm setting up an RPi to run IndiServer components to communicate with connected hardware all driven/controlled by KStars/Ekos on a remote (LAN) connected Mac (so I can be warm indoors). I'm NOT running KStars/Ekos on the RPi (not using VNC ...).
To use offline astronomy.net for plate solving, polar alignment, etc. do I have to:
1. Add the "Astronomy" module to the Ekos IndiServer profile ?
2. Setup (python, etc) on the RPi and download the astronomy data to the RPi ? (I've enough space but processor is only a RPi3.
i.e. is the plate solving etc. carried out in the Ekos client or on the IndiServer or is there a config choice necessary.
Sorry if it's a basic question (I have searched around and played around - but fr testing I've installed astronomy stuff on the Mac to run using the simulators).
Thanks
Ian
Read More...
As I understand it, imminent macOS release 10.15 will require all apps are "notarized" in order to be installed.
Is KStars/Ekos for Mac currently notarised or plans to make it notarized (or are there ways round it)?
I'm uncertain what notarization involves and to me it sounds like a retrograde step. There are rumours that the requirement might be slipping and wont be introduced immediately on 10.15 release but I've no idea as to the reliability of these rumours.
Read More...
Thank you (and others) for providing such an amazing suit of software.
It might be overkill to change the INDIWebManager template .service file, particularly if it's specific to Raspbian and if the GSC instructions make it clear.
I was previously on UbuntuMate but for a rebuild became worried about the slow/delayed update release timescales for RPi versions and as the underlying OS is pretty much the sam and as it's a tool (small black box) Raspbian would undoubtedly "do the job".
I'm probably unusual in wanting totally headless, but I'm very aware of how limited RPi RAM is (and I'm open to suggestions from others).
Anyway, thanks for your time and assistance.
Read More...