×
INDI Library v1.8.1 Released (09 Sep 2019)

Monthly maintenance release INDI v1.8.1

Indi on the rocks (a Rock64 to be exact)

1 year 9 months ago
rlancaste
Platinum Boarder
Platinum Boarder
Posts: 1897
Karma: 19
More
Indi on the rocks (a Rock64 to be exact) #21402
Nevermind, I figured out the last one. I had to add the armhf architecture because phd2 doesn't have a 64 bit version
The following user(s) said Thank You Casaro68

Please Log in or Create an account to join the conversation.

1 year 9 months ago 1 year 9 months ago by Casaro68.
Casaro68
Fresh Boarder
Fresh Boarder
Posts: 12
More
Indi on the rocks (a Rock64 to be exact) #21472
Hi

I installed the ayufan 5.15 mate xenial and vnc4server ... I managed to make it work with the monitor connected ... but clearly without monitor, the desktop don't start and so nothing vnc ...
Sifting through the system folders I found the hdmi-toggle file under / usr / local / bin which seems to check the physical state of the monitor connections ...
I do not have the ability to understand if it can serve us or not ...
Perhaps at the end of the check you can tell, if there is no physical connection, to load "xorg video dummy", so if there is an attached monitor, use the monitor, otherwise use "xorg video dummy"
If you want to take a look ...
ps sorry for the english-google.... :-)
Paolo

Please Log in or Create an account to join the conversation.

1 year 9 months ago
HelgeMK
Gold Boarder
Gold Boarder
Posts: 303
Karma: 1
More
Indi on the rocks (a Rock64 to be exact) #21474
Hi, I just made another attempt to install wiringPi-Pine64, but was not succesful. Could someone more knowledgable than me have a look on what went wrong? Problems started after executing the step: make -C gpio - maybe already before, not sure what to make out of the warning messages.

rock64@rock64:~$ ls
astroberry-diy Documents Light Pictures Templates wiringPi-Pine64
Desktop Downloads Music Public Videos
rock64@rock64:~$ cd wiringPi-Pine64
rock64@rock64:~/wiringPi-Pine64$ make -C wiringPi clean
make: Entering directory '/home/rock64/wiringPi-Pine64/wiringPi'
[Clean]
make: Leaving directory '/home/rock64/wiringPi-Pine64/wiringPi'
rock64@rock64:~/wiringPi-Pine64$ make -C wiringPi
make: Entering directory '/home/rock64/wiringPi-Pine64/wiringPi'
[Compile] wiringPi.c
wiringPi.c: In function ‘analogRead’:
wiringPi.c:2304:20: warning: pointer targets in passing argument 1 of ‘atoi’ differ in signedness [-Wpointer-sign]
return atoi(value);
^
In file included from /usr/include/features.h:367:0,
from /usr/include/stdio.h:27,
from wiringPi.c:54:
/usr/include/stdlib.h:278:1: note: expected ‘const char *’ but argument is of type ‘unsigned char *’
__NTH (atoi (const char *__nptr))
^
wiringPi.c: In function ‘waitForInterrupt’:
wiringPi.c:2486:1: warning: label ‘wait’ defined but not used [-Wunused-label]
wait:
^
wiringPi.c: In function ‘interruptHandler’:
wiringPi.c:2523:14: warning: return makes pointer from integer without a cast [-Wint-conversion]
return wiringPiFailure (WPI_FATAL, "wiringPiISR: wiringPi has not been in
^
wiringPi.c: In function ‘wiringPiSetup’:
wiringPi.c:2889:9: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
if ((int32_t)gpio == -1)
^
wiringPi.c:2910:9: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
if ((int32_t)gpio == -1)
^
wiringPi.c:2925:9: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
if ((int32_t)gpio == -1)
^
wiringPi.c:2930:9: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
if ((int32_t)gpio1 == -1)
^
wiringPi.c:2955:9: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
if ((int32_t)gpio == -1)
^
wiringPi.c:2961:9: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
if ((int32_t)pwm == -1)
^
wiringPi.c:2967:9: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
if ((int32_t)clk == -1)
^
wiringPi.c:2973:9: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
if ((int32_t)pads == -1)
^
wiringPi.c: In function ‘piBoardRev’:
wiringPi.c:1339:3: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
read (fd, buf, sizeof(buf));
^
wiringPi.c: In function ‘digitalRead’:
wiringPi.c:2117:7: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
read (sysFds [fd_pos], &c, 1) ;
^
wiringPi.c: In function ‘digitalWrite’:
wiringPi.c:2201:11: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
write (sysFds [fd_pos], "0\n", 2) ;
^
wiringPi.c:2203:11: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
write (sysFds [fd_pos], "1\n", 2) ;
^
wiringPi.c: In function ‘analogRead’:
wiringPi.c:2303:7: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
read (adcFds [pin], &value[0], 4);
^
wiringPi.c: In function ‘waitForInterrupt’:
wiringPi.c:2493:3: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
(void)read (fd, &c, 1) ;
^
wiringPi.c: In function ‘wiringPiISR’:
wiringPi.c:2665:7: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
read (sysFds [fd_base], &c, 1) ;
^
wiringPi.c:2692:7: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
read (sysFds [fd_base], &c, 1) ;
^
wiringPi.c:2709:7: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
read (sysFds [bcmGpioPin], &c, 1) ;
^
[Compile] wiringSerial.c
wiringSerial.c: In function ‘serialPutchar’:
wiringSerial.c:146:3: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
write (fd, &c, 1) ;
^
wiringSerial.c: In function ‘serialPuts’:
wiringSerial.c:158:3: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
write (fd, s, strlen (s)) ;
^
[Compile] wiringShift.c
[Compile] piHiPri.c
[Compile] piThread.c
[Compile] wiringPiSPI.c
[Compile] wiringPiI2C.c
[Compile] softPwm.c
[Compile] softTone.c
[Compile] mcp23008.c
[Compile] mcp23016.c
[Compile] mcp23017.c
[Compile] mcp23s08.c
[Compile] mcp23s17.c
[Compile] sr595.c
[Compile] pcf8574.c
[Compile] pcf8591.c
pcf8591.c: In function ‘myAnalogWrite’:
pcf8591.c:44:3: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
write (node->fd, b, 2) ;
^
[Compile] mcp3002.c
[Compile] mcp3004.c
[Compile] mcp4802.c
[Compile] mcp3422.c
mcp3422.c: In function ‘myAnalogRead’:
mcp3422.c:62:7: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
read (node->fd, buffer, 4) ;
^
mcp3422.c:68:7: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
read (node->fd, buffer, 3) ;
^
mcp3422.c:74:7: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
read (node->fd, buffer, 3) ;
^
mcp3422.c:80:7: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result]
read (node->fd, buffer, 3) ;
^
[Compile] max31855.c
[Compile] max5322.c
[Compile] sn3218.c
[Compile] drcSerial.c
[Link (Dynamic)]
make: Leaving directory '/home/rock64/wiringPi-Pine64/wiringPi'
rock64@rock64:~/wiringPi-Pine64$ ls
build devLib Makefile postinstall-pak
COPYING.LESSER examples newVersion README.TXT
debian gpio People VERSION
debian-template INSTALL pins wiringPi
rock64@rock64:~/wiringPi-Pine64$ gpio readall
Oops: Unable to determine board revision from /proc/cpuinfo
-> No "Hardware" line
-> You'd best google the error to find out why.
rock64@rock64:~/wiringPi-Pine64$ make -C wiringPi install
make: Entering directory '/home/rock64/wiringPi-Pine64/wiringPi'
[Install Headers]
install: cannot remove '/usr/local/include/wiringPi.h': Permission denied
Makefile:93: recipe for target 'install-headers' failed
make: *** [install-headers] Error 1
make: Leaving directory '/home/rock64/wiringPi-Pine64/wiringPi'
rock64@rock64:~/wiringPi-Pine64$ sudo make -C wiringPi install
[sudo] password for rock64:
make: Entering directory '/home/rock64/wiringPi-Pine64/wiringPi'
[Install Headers]
[Install Dynamic Lib]
make: Leaving directory '/home/rock64/wiringPi-Pine64/wiringPi'
rock64@rock64:~/wiringPi-Pine64$ gpio readall
Oops: Unable to determine board revision from /proc/cpuinfo
-> No "Hardware" line
-> You'd best google the error to find out why.
rock64@rock64:~/wiringPi-Pine64$ make -C devLib
make: Entering directory '/home/rock64/wiringPi-Pine64/devLib'
[Compile] ds1302.c
[Compile] maxdetect.c
[Compile] piNes.c
[Compile] gertboard.c
[Compile] piFace.c
[Compile] lcd128x64.c
[Compile] lcd.c
[Compile] piGlow.c
[Link (Dynamic)]
make: Leaving directory '/home/rock64/wiringPi-Pine64/devLib'
rock64@rock64:~/wiringPi-Pine64$ sudo make -C devLib install
make: Entering directory '/home/rock64/wiringPi-Pine64/devLib'
[Install Headers]
[Install Dynamic Lib]
make: Leaving directory '/home/rock64/wiringPi-Pine64/devLib'
rock64@rock64:~/wiringPi-Pine64$ make -C gpio
make: Entering directory '/home/rock64/wiringPi-Pine64/gpio'
[Compile] gpio.c
gpio.c: In function ‘doEdge’:
gpio.c:569:3: warning: implicit declaration of function ‘doUnexport’ [-Wimplicit-function-declaration]
doUnexport(3, argv); // unexport argc == 3
^
gpio.c: At top level:
gpio.c:642:6: warning: conflicting types for ‘doUnexport’
void doUnexport (int argc, char *argv [])
^
gpio.c:569:3: note: previous implicit declaration of ‘doUnexport’ was here
doUnexport(3, argv); // unexport argc == 3
^
gpio.c: In function ‘doLoad’:
gpio.c:225:11: warning: ignoring return value of ‘system’, declared with attribute warn_unused_result [-Wunused-result]
system (cmd) ;
^
gpio.c:248:11: warning: ignoring return value of ‘system’, declared with attribute warn_unused_result [-Wunused-result]
system (cmd) ;
^
gpio.c:252:11: warning: ignoring return value of ‘system’, declared with attribute warn_unused_result [-Wunused-result]
system (cmd) ;
^
gpio.c:303:7: warning: ignoring return value of ‘system’, declared with attribute warn_unused_result [-Wunused-result]
system (cmd) ;
^
gpio.c:309:7: warning: ignoring return value of ‘system’, declared with attribute warn_unused_result [-Wunused-result]
system (cmd) ;
^
[Compile] extensions.c
[Compile] readall.c
[Compile] pins.c
[Link]
/usr/local/lib/libwiringPi.so: undefined reference to `crypt'
/usr/local/lib/libwiringPi.so: undefined reference to `shm_open'
collect2: error: ld returned 1 exit status
Makefile:48: recipe for target 'gpio' failed
make: *** [gpio] Error 1
make: Leaving directory '/home/rock64/wiringPi-Pine64/gpio'
rock64@rock64:~/wiringPi-Pine64$ sudo make -C gpio
make: Entering directory '/home/rock64/wiringPi-Pine64/gpio'
[Link]
/usr/local/lib/libwiringPi.so: undefined reference to `crypt'
/usr/local/lib/libwiringPi.so: undefined reference to `shm_open'
collect2: error: ld returned 1 exit status
Makefile:48: recipe for target 'gpio' failed
make: *** [gpio] Error 1
make: Leaving directory '/home/rock64/wiringPi-Pine64/gpio'
rock64@rock64:~/wiringPi-Pine64$ make -C gpio clean
make: Entering directory '/home/rock64/wiringPi-Pine64/gpio'
[Clean]
make: Leaving directory '/home/rock64/wiringPi-Pine64/gpio'
rock64@rock64:~/wiringPi-Pine64$ sudo make -C gpio
make: Entering directory '/home/rock64/wiringPi-Pine64/gpio'
[Compile] gpio.c
gpio.c: In function ‘doEdge’:
gpio.c:569:3: warning: implicit declaration of function ‘doUnexport’ [-Wimplicit-function-declaration]
doUnexport(3, argv); // unexport argc == 3
^
gpio.c: At top level:
gpio.c:642:6: warning: conflicting types for ‘doUnexport’
void doUnexport (int argc, char *argv [])
^
gpio.c:569:3: note: previous implicit declaration of ‘doUnexport’ was here
doUnexport(3, argv); // unexport argc == 3
^
gpio.c: In function ‘doLoad’:
gpio.c:225:11: warning: ignoring return value of ‘system’, declared with attribute warn_unused_result [-Wunused-result]
system (cmd) ;
^
gpio.c:248:11: warning: ignoring return value of ‘system’, declared with attribute warn_unused_result [-Wunused-result]
system (cmd) ;
^
gpio.c:252:11: warning: ignoring return value of ‘system’, declared with attribute warn_unused_result [-Wunused-result]
system (cmd) ;
^
gpio.c:303:7: warning: ignoring return value of ‘system’, declared with attribute warn_unused_result [-Wunused-result]
system (cmd) ;
^
gpio.c:309:7: warning: ignoring return value of ‘system’, declared with attribute warn_unused_result [-Wunused-result]
system (cmd) ;
^
[Compile] extensions.c
[Compile] readall.c
[Compile] pins.c
[Link]
/usr/local/lib/libwiringPi.so: undefined reference to `crypt'
/usr/local/lib/libwiringPi.so: undefined reference to `shm_open'
collect2: error: ld returned 1 exit status
Makefile:48: recipe for target 'gpio' failed
make: *** [gpio] Error 1
make: Leaving directory '/home/rock64/wiringPi-Pine64/gpio'
rock64@rock64:~/wiringPi-Pine64$ sudo make -C gpio install
make: Entering directory '/home/rock64/wiringPi-Pine64/gpio'
[Install]
cp: cannot stat 'gpio': No such file or directory
Makefile:67: recipe for target 'install' failed
make: *** [install] Error 1
make: Leaving directory '/home/rock64/wiringPi-Pine64/gpio'
rock64@rock64:~/wiringPi-Pine64$ gpio readall
Oops: Unable to determine board revision from /proc/cpuinfo
-> No "Hardware" line
-> You'd best google the error to find out why.
rock64@rock64:~/wiringPi-Pine64$

Please Log in or Create an account to join the conversation.

1 year 9 months ago
HelgeMK
Gold Boarder
Gold Boarder
Posts: 303
Karma: 1
More
Indi on the rocks (a Rock64 to be exact) #21484
First, apologies for my previous, excessively long post - should have copied into a file.

In the meantime I found a library for the GPIOs that I was able to install on the Rock64. Need to think how to test / verify that it works - a test script is provided, I need to do the wiring.

github.com/swkim01/RPi.GPIO-PineA64

Best, Helge

Please Log in or Create an account to join the conversation.

1 year 9 months ago
HelgeMK
Gold Boarder
Gold Boarder
Posts: 303
Karma: 1
More
Indi on the rocks (a Rock64 to be exact) #21531
Just to come of an issue discussed in the past, which is “inverted colors” for the program windows. I did some more analysis and swapped the colors, using the theme settings/customizing. That actually revealed that it is not the entire program window of EKOS that has inverted colors (black instead of white), but just the content, see screenshot. So, maybe there is nothing wrong with the window color settings, but a conflict that KStars/Ekos runs into on the rock64 - either due to its architecture or operating system (I am using the ayufan-Mate os)

@ Jasem, can you kindly have a look and let me know what is your opinion?
Attachments:

Please Log in or Create an account to join the conversation.

1 year 9 months ago
HelgeMK
Gold Boarder
Gold Boarder
Posts: 303
Karma: 1
More
Indi on the rocks (a Rock64 to be exact) #21543
Hi Jasem,

Just wondering about the following: concerning the issue reported below (pls see also screenshot) - could it potentially make a difference to install KStars / Ekos from source, instead of ppa?

Thanks, Helge

Please Log in or Create an account to join the conversation.

1 year 8 months ago
wimvb
Expert Boarder
Expert Boarder
Posts: 99
More
Topic Author
Indi on the rocks (a Rock64 to be exact) #21881
I'm veeeery happy to announce that phd2 now also works on the Rock64 under ubuntu mate.

This is the way to it set up:

sudo add-apt-repository ppa:pch/phd2

sudo apt-get update
sudo apt-get install phd2



Previously, there was no arm64 build for phd2 on ubuntu. But with tremendous help from Patrick Chevalley, I managed to build phd2 from source. Patrick then added the arm64 architecture to the ppa build.



On the downside: I'm completely clouded in (no surprise there), so I can't test it.

Wim

Opticron Oregon 15*70, Skywatcher 150PDS + ST80, AZ-EQ6 GT + EQ3-2 Goto, ZWO ASI174MM-Cool + Pentax K20D (retired) + ZWO ASI120MM, homemade ditherbox, PixInsight, Rock64 x 2 with INDI & PHD2, cloud cover

www.astrobin.com/users/wimvb/

Please Log in or Create an account to join the conversation.

1 year 8 months ago
rlancaste
Platinum Boarder
Platinum Boarder
Posts: 1897
Karma: 19
More
Indi on the rocks (a Rock64 to be exact) #21882
That’s good news and it’s a little better than my solution. I had just built it in 32 bit. But it should be better in 64 bit. If phd2 now supports aarch64 aka arm64 then I can update the 64 bit build script

Please Log in or Create an account to join the conversation.

1 year 8 months ago
maudy
Platinum Boarder
Platinum Boarder
Posts: 353
Karma: 2
More
Indi on the rocks (a Rock64 to be exact) #21888
Wow! this is progress. What is performance like compared to the RPI3?
I have been watching this thread, and not ordering a rock64 - my mount is a problem enough at the moment. One problem at time.
I wondering how rock64 is working out for the ASI EFW, two ASI cameras, Nightcrawler driver, and mount, phd2, and VNC to the rock64. Also using SMB for file transfers, as well as ssh. The RPI3 with the above does work with zram config, and I am hoping the extra RAM 2~4GB helps. Also, I would be using a wifi dongle since I do not want to always be running CAT45 unless debugging things.

Please Log in or Create an account to join the conversation.

1 year 8 months ago 1 year 8 months ago by wimvb.
wimvb
Expert Boarder
Expert Boarder
Posts: 99
More
Topic Author
Indi on the rocks (a Rock64 to be exact) #21897

maudy wrote: Wow! this is progress. What is performance like compared to the RPI3?
I have been watching this thread, and not ordering a rock64 - my mount is a problem enough at the moment. One problem at time.
I wondering how rock64 is working out for the ASI EFW, two ASI cameras, Nightcrawler driver, and mount, phd2, and VNC to the rock64. Also using SMB for file transfers, as well as ssh. The RPI3 with the above does work with zram config, and I am hoping the extra RAM 2~4GB helps. Also, I would be using a wifi dongle since I do not want to always be running CAT45 unless debugging things.

I would love to say that all is fine now and that it works splendidly. Unfortunately, not so.
I now have essentially two identical setups, one on a raspberry pi, and the other on a rock64:
Ubuntu Mate 16.04
xrdp installed
full indi & ekos/kstars install (from the ppa)
all the necessary drivers installed (yes, the ZWO efw now works on both RPi and Rock)
phd2 installed from the ppa (Patrick made the arm64 build)

Astronomy hardware:
AZEQ6GT mount (eqmod mount)
ZWO ccd's: ASI174MM cool with ZWO efw mini for imaging, and ASI120MM (old usb2 version) for guiding
DIY Moonlite compatible arduino focuser

1. the setup on Raspberry Pi works flawlessly. I can run indi, phd and ekos/kstars on the Pi from a remote desktop (windows 8 on laptop)
2. running indiserver on the Pi and Rock and controlling from ekos/kstars on my windows laptop works. This is with the camera connected to a powered usb2 hub.

However:

3. on the Rock64, I can't use both cameras at the same time. Apparantly having two zwo cameras creates a conflict. This issue was solved a long time ago on the Pi, but persists on the Rock. (have to investigate this further, see point 6)
4. Ekos/kstars on the rock doesn't recognise my keyboard (laptop, using xrdp). Only in ekos are the letters of my keyboard mixed up, E.g. pressing 'q' results in a 'c'. Doing anything outside ekos works fine.
5. connected to the usb3 port, the ASI174 takes about 40 seconds to connect in ekos, independent of where ekos runs (local or on windows). The "control" tab takes another 15 seconds to load.
6. Connected to usb3, the ASI174 is slow to respond, and won't take exposures. I will have to investigate this further and get proper logs. Since the camera worked under usb2, connected to a powered usb hub, maybe this is a power issue.

So, there's still a lot to fix until I can "go live". I will keep updating here when I sort out the issues.

Wim

Opticron Oregon 15*70, Skywatcher 150PDS + ST80, AZ-EQ6 GT + EQ3-2 Goto, ZWO ASI174MM-Cool + Pentax K20D (retired) + ZWO ASI120MM, homemade ditherbox, PixInsight, Rock64 x 2 with INDI & PHD2, cloud cover

www.astrobin.com/users/wimvb/

Please Log in or Create an account to join the conversation.

1 year 8 months ago
wimvb
Expert Boarder
Expert Boarder
Posts: 99
More
Topic Author
Indi on the rocks (a Rock64 to be exact) #21924
Issue 6 in my previous post is fixed. This was a power issue. I have now invested in a powered usb3 hub (Plexgear Desktop 400 pro). Connecting the ASI174 to this powered hub solved its problems. Connection is faster than on Raspberry Pi. Imaging from ekos/kstars on Rock64 also works, and image download is superfast.

But I still can't guide with phd2 and the ZWO ASI120MM (usb2 version).
And at the moment the most annoying part is that when I run ekos/kstars directly on the rock64, the keyboard gets garbled.
I will probably work around this by trying to set up phd and using the windows version of ekos.

Wim

Opticron Oregon 15*70, Skywatcher 150PDS + ST80, AZ-EQ6 GT + EQ3-2 Goto, ZWO ASI174MM-Cool + Pentax K20D (retired) + ZWO ASI120MM, homemade ditherbox, PixInsight, Rock64 x 2 with INDI & PHD2, cloud cover

www.astrobin.com/users/wimvb/

Please Log in or Create an account to join the conversation.

1 year 8 months ago
wimvb
Expert Boarder
Expert Boarder
Posts: 99
More
Topic Author
Indi on the rocks (a Rock64 to be exact) #21928
First off: solving issue 6 in a previous post, also solved issue 5. A powered usb3 hub is necessary to get the most out of the camera.

Now I also figured out a very annoying workaround for issues 3 and 4:

I set up the rock64 with just the ASI174 and EFW connected to the usb3 port
Then I set up my raspberry pi with the mount, focuser (simulator at the moment), and ASI120 (which is my guide camera)

I used the indi tutorial about configuring indi on multiple devices:

indilib.org/support/tutorials/159-indi-on-multiple-devices.html

The annoying part is that it's a complicated setup, and that guiding is now on the slower device.

The good part is of course that it works.
Btw, I save images locally, which is on the faster rock64. So at least, images captured with the ASI174 over usb3 don't have to be transmitted over wifi before they get stored.

Wim

Opticron Oregon 15*70, Skywatcher 150PDS + ST80, AZ-EQ6 GT + EQ3-2 Goto, ZWO ASI174MM-Cool + Pentax K20D (retired) + ZWO ASI120MM, homemade ditherbox, PixInsight, Rock64 x 2 with INDI & PHD2, cloud cover

www.astrobin.com/users/wimvb/
The following user(s) said Thank You maudy, tkottary

Please Log in or Create an account to join the conversation.

Time to create page: 0.860 seconds