What is the logic behind the order of the devices in the indi control panel please? Just curious ,it is random or else?
Read More...
Here are my rules for the AF3 / FR1 / FP1
AF3= autofocuser
FR1 = Field Rotator
FP1 = Flat panelSUBSYSTEM=="tty", ATTRS{idVendor}=="2341", ATTRS{product}=="Arduino Nano Every", ATTRS{idProduct}=="0058", ATTRS{serial}=="CDF0B4D451514746304B2020FF0A0328", SYMLINK+="FR1", KERNEL=="ttyACM*", MODE="0666"SUBSYSTEM=="tty", ATTRS{idVendor}=="2341", ATTRS{product}=="Arduino Nano Every", ATTRS{idProduct}=="0058", ATTRS{serial}=="902AE657515146544E4B2020FF0B3646", SYMLINK+="FP1", KERNEL=="ttyACM*", MODE="0666"SUBSYSTEM=="tty", ATTRS{idVendor}=="2341", ATTRS{product}=="Arduino Nano Every", ATTRS{idProduct}=="0058", ATTRS{serial}=="C4B1A01151514746304B2020FF0A1317", SYMLINK+="AF3", KERNEL=="ttyACM*", MODE="0666"
You will get in /dev :
root@heidenrod-obs:/dev# ll
total 4
drwxr-xr-x 16 root root 4860 Jul 1 17:38 ./
drwxr-xr-x 23 root root 4096 Mar 19 17:43 ../
lrwxrwxrwx 1 root root 7 Jul 1 17:38 AF3 -> ttyACM1
lrwxrwxrwx 1 root root 7 Jul 1 17:38 FP1 -> ttyACM0
lrwxrwxrwx 1 root root 7 Jul 1 17:38 FR1 -> ttyACM2
Read More...
OK update:
Previously I had "Weather Radio"@localhost:7625 in the Remote Driver box, now I need to have "Weather Radio"@192.168.8.124:7625
If I use localhost, the profile will not start but will do if I specify the IP address.
Read More...
It turned out that from looking at the /tmp/indiserver.log I should have noticed the following:
FIFO: start "Weather Radio"@localhost:7625
FIFO: Starting driver Weather Radio@localhost:7625
connect(localhost,7625): Connection refused
2021-06-29T21:39:06: good bye
Basically, as the weather radio wasn't running (I need to figure out why this is the case), you cannot start the profile. I have "Weather Radio"@localhost:7625 in the Remote Drivers option.
Read More...
I'm working with Jasem, we're going to try to understand what's going on and hopefully fix it. I'll keep you informed, hold on...
Read More...
OK so this is a very interesting one, an odd one really... I am now able to connect and this is how I've done it:
First I tried all kind of combinations, auto search, specified the serial-id, the ports etc... nothing would work so I decided to check again my Odroid and the Pegasus was symlinked to /dev/ttyUSB1 so I decided to use this in the 'ports' and hit 'save' in the indi panel.
Right after I hit the save button, I was able to connect. I've have now disconnected and reconnected multi times and no further issues.
Could you please try from your side the above "trick"
Read More...
Here's another issue, after updating to 1.9.1 indi-web is unable to start my save profile. I have restarted the service, tried to remove drivers, no go. Only the "simulator" profile works.
Read More...
Well at the moment my brand new Pegasus PBM is just paper weight until this gets resolved. I would hate having to roll back the indilib packages.
Read More...
After updating indilib yesterday, I can no longer connect to my Pegasus Power Box Advance.
All I get is the following error messages:and if I turn on the auto-detect:
It's detected as per dmesg output:lsusb:
/dev/serial
Read More...
I have received a few days ago a few items from Pavle (DeepSky Dad)
The camera rotator:
The focuser:
After I took the picture I realised that the connectors were on the wrong side, I corrected it
The flap led panel:
And this is what it looks like all attached:
I am awaiting the Pegasus Powerbox Advance to connect everything neatly, it should arrive in the next few days.
Back to DeepSky Dad products, I am seriously impressed by the quality of the 3D printing. I owned a 3D printer (now sold) and I know how tedious it can be to produce something good.
Everything went on the Redcat without issues, the fit is perfect and you can see he has done some research.
In fact, the way my focuser is mounted was my request so this product is brand new and should be available on his website soon. I didn't want to add the block under the Redcat.
Read More...