Radek,

I've been using dd to backup and restore SD cards, and I've seen, e.g. 30minutes to save a 32Gb SD card to disk and 2-3 hours to write a 32Gb SD card from disk. I've also noticed that when I download an Ubuntu .iso, Etcher can write that to an SD card in a minute (though it's true that the dd backups are 32Gb, and the Ubuntu .iso files are a few GB). Still, the write speed of Etcher seems an order of magnitude faster--though it won't write these dd backups. Any idea why Etcher is so much faster at writing SD cards, and is there a way to get dd to write that fast, or get Etcher to write these dd backups?

Hy

The timing comes from SD is much faster to read than to write. Another thing is that dd makes a real bit copy of a SD card, which means it copies parts of SD which are not used too. The resulting file's size equals SD card size, no matter what space is actually used on SD card. You can write an image back to SD card with any software. No need to stick to dd. Etcher should be fine. I have no idea if it's going to be faster. You can try it out
One more note... writing to SD card means that lots of data is buffered in your RAM before it actually is written to SD card. For a user this seems fast write (because it's fast read from HDD and fast write to RAM), but in reality it takes much longer (read from RAM and write to SD). Make sure you ALWAYS disconnect/unmount SD card properly, don't just unplug it. Otherwise it will be corrupted write (not all data from RAM will be written to SD card).

yeah I use etcher - faster.

So running tests all afternoon. Managed to set park3 as normal. I edited my location again since the long as been off.
After I set it. It changed back to 274 and should be -85.
???

Sounds about right. Kstars works on 360 degrees for longitude. So 360-85= 275

Yesterday I did a lot of kstars/ekos testing. It really shows promise. Though I can't use it yet. I think I need to downgrade my firmware to nexdome 1.1 (I think that is what the indi driver was written for). It connects but doesn't move. I may try flashing the two units today.

I also can't get the snapcap to connect or the cloudwatcher or the optic rotator. Is it possible to run out of ports? Upon connecting I get a lot of errors that a driver is already using this port - it tries about 4-5 ports and stops. What is my next step on those issues?

This is what I see when booting Ekos.

PYXIS:
2019-03-08T14:50:48: [WARNING] Port /dev/ttyUSB2 is already used by another driver or process.
2019-03-08T14:50:45: [INFO] Trying connecting to /dev/ttyUSB2 @ 9600 ...
2019-03-08T14:50:44: [WARNING] Port /dev/ttyUSB0 is already used by another driver or process.
2019-03-08T14:50:41: [INFO] Trying connecting to /dev/ttyUSB0 @ 9600 ...
2019-03-08T14:50:41: [WARNING] Port /dev/ttyACM1 is already used by another driver or process.
2019-03-08T14:50:38: [INFO] Trying connecting to /dev/ttyACM1 @ 9600 ...
2019-03-08T14:50:36: [WARNING] Port /dev/ttyUSB1 is already used by another driver or process.
2019-03-08T14:50:33: [INFO] Trying connecting to /dev/ttyUSB1 @ 9600 ...
2019-03-08T14:50:32: [WARNING] Communication with /dev/ttyACM0 @ 9600 failed. Starting Auto Search...
2019-03-08T14:50:32: [INFO] Error retreiving data from Pyxis, please ensure Pyxis controller is powered and the port is correct.
2019-03-08T14:50:32: [ERROR] Cannot establish communication. Check power is on and homing is complete.
2019-03-08T14:50:32: [INFO] Session log file /home/ron/.indi/logs/2019-03-08/indi_pyxis_rotator/indi_pyxis_rotator_14:50:32.log
2019-03-08T14:50:32: [INFO] Debug is enabled.

SNAPCAP:
2019-03-08T14:50:51: [WARNING] Port /dev/ttyUSB2 is already used by another driver or process.
2019-03-08T14:50:48: [INFO] Trying connecting to /dev/ttyUSB2 @ 9600 ...
2019-03-08T14:50:47: [WARNING] Port /dev/ttyACM1 is already used by another driver or process.
2019-03-08T14:50:44: [INFO] Trying connecting to /dev/ttyACM1 @ 9600 ...
2019-03-08T14:50:44: [ERROR] Device ping failed.
2019-03-08T14:50:44: [ERROR] >V000: Read overflow.
2019-03-08T14:50:44: [ERROR] >V000: Read overflow.
2019-03-08T14:50:44: [INFO] Trying connecting to /dev/ttyACM0 @ 9600 ...
2019-03-08T14:50:42: [WARNING] Port /dev/ttyUSB0 is already used by another driver or process.
2019-03-08T14:50:39: [INFO] Trying connecting to /dev/ttyUSB0 @ 9600 ...
2019-03-08T14:50:38: [WARNING] Communication with /dev/ttyUSB1 @ 9600 failed. Starting Auto Search...
2019-03-08T14:50:38: [ERROR] Device ping failed.
2019-03-08T14:50:38: [ERROR] >V000: Timeout error.
2019-03-08T14:50:35: [ERROR] >V000: Timeout error.
2019-03-08T14:50:32: [INFO] Session log file /home/ron/.indi/logs/2019-03-08/indi_snapcap/indi_snapcap_14:50:32.log
2019-03-08T14:50:32: [INFO] Debug is enabled.

CLOUDWATCHER:
2019-03-08T14:50:32: [INFO] Device configuration applied.
2019-03-08T14:50:32: [INFO] Loading device configuration...
(HOWEVER connection is YELLOW) ?

SHOOT Also the mount wasn't connecting, then was... now isn't.
ASTRO PYHS EXPERIMENTAL:
2019-03-08T14:50:32: [INFO] Session log file /home/ron/.indi/logs/2019-03-08/indi_lx200ap_experimental/indi_lx200ap_experimental_14:50:32.log
2019-03-08T14:50:32: [INFO] Debug is enabled.
(But connection is YELLOW?)

I'll see if the logs help. digging in.

well the mount's log is no help.

INFO 0.048181 sec : Session log file /home/ron/.indi/logs/2019-03-08/indi_lx200ap_experimental/indi_lx200ap_experimental_14:50:32.log
DEBUG 0.060113 sec : Active Snoop, driver: Dome Simulator, property: DOME_PARK
DEBUG 0.130341 sec : Active Snoop, driver: Dome Simulator, property: DOME_PARK
DEBUG 0.813336 sec : Connecting to /dev/ttyUSB0
DEBUG 0.813562 sec : Port FD 8
DEBUG 0.813579 sec : Connection successful, attempting handshake...
SCOPE 0.813604 sec : CMD <#:Br 00:00:00#>

Apparently now response from handshake. (previous log says handshake successful) and continued to load and work.
???

Each issue needs to be diagnosed individually. What the problem with nexdome? Did you turn Dome logging on? If yes, please share the logs.

/edit\edit


I have come to ignore that message, not having found an action that generates a "mount is now initialized" message. In the documentation there is the following.

"The mount will automatically be initialized by the driver - the user is not required to do anything extra."

indilib.org/devices/telescopes/astrophys...cs-experimental.html

This is normal, it takes the scenic route. from the documentation.
Location: Latitude and Longitude must be set for proper operation of the driver upon connection. The longitude range is 0 to 360 degrees increasing eastward from Greenwich.

indilib.org/devices/telescopes/astrophys...cs-experimental.html

I had no idea that these exsisted. indilib.org/devices/telescopes/astrophys...cs-experimental.html !!!!!!!!!!!!!

thanks I'll check it out.

"Each issue needs to be diagnosed individually. What the problem with nexdome? Did you turn Dome logging on? If yes, please share the logs. "

sounds good - I assumed I didn't get responses because I was over whelming. = )

On the dome. It connects but doesn't run. I suspect it's because I have PDM's firmware. (I have been using the PDM nexdome driver under windows). I will try and downgrade my firmware today. (but that will trash my windows option). Still kstars/ekos looks like it's worth the transition pains. I'll try firmware change before I get more into dome connection. (it all seems connected fine, just doesn't repond).

If you could - can we narrow down the mount issue first? The reason is - I have a log that WORKED last night. And one that doesn't work (today) and before yesterday. Let me attach the working and unworking log. Seemed to be a handshake issue.

here is last nights (working log) well the top part).

INFO 0.013698 sec : Session log file /home/ron/.indi/logs/2019-03-08/indi_lx200ap_experimental/indi_lx200ap_experimental_02:16:16.log
DEBUG 0.019797 sec : Active Snoop, driver: Dome Simulator, property: DOME_PARK
DEBUG 0.022741 sec : Active Snoop, driver: Dome Simulator, property: DOME_PARK
DEBUG 0.070003 sec : Connecting to /dev/ttyUSB0
DEBUG 0.070431 sec : Port FD 8
DEBUG 0.070480 sec : Connection successful, attempting handshake...
SCOPE 0.070505 sec : CMD <#:Br 00:00:00#>
SCOPE 0.093871 sec : CMD <#:Br 00:00:00#> successful.
SCOPE 0.093912 sec : CMD <#:V#>
SCOPE 0.125973 sec : RES <VCP4-E01-11A>
INFO 0.126079 sec : Servo Box Controller: GTOCP4.
INFO 0.126095 sec : Firmware Version: 'V' - E01-11A
INFO 0.126108 sec : Firmware level 'V' detected - driver loaded.
INFO 0.126122 sec : This is an _EXPERIMENTAL_ driver for Astro-Physics mounts - use at own risk!
INFO 0.126141 sec : BEFORE USING PLEASE READ the documentation at:
INFO 0.126155 sec : indilib.org/devices/telescopes/astrophysics.html
SCOPE 0.126173 sec : CMD <:GR#>
SCOPE 0.141864 sec : RES <00:00.0>
SCOPE 0.141906 sec : Detected low precision format, attempting to switch to high precision.
SCOPE 0.141935 sec : CMD <:GR#>
SCOPE 0.173991 sec : RES <00:00:00>
SCOPE 0.174093 sec : Coordinate format is high precision.
INFO 0.174124 sec : AstroPhysics Experimental is online.
DEBUG 0.176287 sec : Configuration successfully saved for DEVICE_PORT.
DEBUG 0.423450 sec : Configuration successfully saved for DEVICE_BAUD_RATE.
DEBUG 0.424073 sec : Configuration successfully saved for CONNECTION_MODE.
SCOPE 0.425895 sec : CMD <:GR#>
SCOPE 0.445910 sec : RES <00:00:00>
SCOPE 0.446132 sec : Coordinate format is high precision.
DEBUG 0.447439 sec : Park to pos set to (3).
INFO 0.447568 sec : Computing PARK3 position...
INFO 0.447606 sec : calcParkPosition: parkPos=3 parkAlt=0.000000 parkAz=180.000000
DEBUG 0.447659 sec : Setting Park Axis1 to 180.00
DEBUG 0.447711 sec : Setting Park Axis2 to 0.00
DEBUG 0.447774 sec : Set predefined park position 3 to az=0.000000 alt=180.000000
DEBUG 0.448000 sec : park position = 3
SCOPE 0.449639 sec : CMD <#:Sg 085*40:12#>
SCOPE 0.449704 sec : CMD <#:Sg 085*40:12#>
SCOPE 0.477554 sec : CMD <#:Sg 085*40:12#> successful.
SCOPE 0.477589 sec : CMD <#:St +42*58:03#>
SCOPE 0.477600 sec : CMD <#:St +42*58:03#>
SCOPE 0.509515 sec : CMD <#:St +42*58:03#> successful.
INFO 0.509565 sec : Site location updated to Lat 42:58:03 - Long 274:19:48
INFO 0.509670 sec : Mount is parked.
DEBUG 0.509695 sec : InitPark Axis1 0.00 Axis2 42.97
DEBUG 0.509715 sec : Setting Default Park Axis1 to 0.00
DEBUG 0.509727 sec : Setting Default Park Axis2 to 0.00
INFO 0.509739 sec : Computing PARK3 position...
INFO 0.509752 sec : calcParkPosition: parkPos=3 parkAlt=0.000000 parkAz=180.000000


Here I connected this morning. Nothing changed other than a reboot. And this is the full log. = (

INFO 0.048181 sec : Session log file /home/ron/.indi/logs/2019-03-08/indi_lx200ap_experimental/indi_lx200ap_experimental_14:50:32.log
DEBUG 0.060113 sec : Active Snoop, driver: Dome Simulator, property: DOME_PARK
DEBUG 0.130341 sec : Active Snoop, driver: Dome Simulator, property: DOME_PARK
DEBUG 0.813336 sec : Connecting to /dev/ttyUSB0
DEBUG 0.813562 sec : Port FD 8
DEBUG 0.813579 sec : Connection successful, attempting handshake...
SCOPE 0.813604 sec : CMD <#:Br 00:00:00#>

CONNECTION button is YELLOW?

I disconnected and reconnected. Here is the log from the display window. I thought I should share it since this is a beta driver and something is saying I have a OLD firmware. (the mount is quite new) so might be a bug?

2019-03-08T16:03:37: [WARNING] Port /dev/ttyUSB2 is already used by another driver or process.
2019-03-08T16:03:34: [INFO] Trying connecting to /dev/ttyUSB2 @ 9600 ...
2019-03-08T16:03:33: [WARNING] Port /dev/ttyACM1 is already used by another driver or process.
2019-03-08T16:03:30: [INFO] Trying connecting to /dev/ttyACM1 @ 9600 ...
2019-03-08T16:03:29: [ERROR] Firmware version is not 'V' - too old to use the experimental driver! <

---

?
2019-03-08T16:03:29: [INFO] Trying connecting to /dev/ttyACM0 @ 9600 ...
2019-03-08T16:03:28: [WARNING] Port /dev/ttyUSB1 is already used by another driver or process.
2019-03-08T16:03:25: [INFO] Trying connecting to /dev/ttyUSB1 @ 9600 ...
2019-03-08T16:03:24: [WARNING] Communication with /dev/ttyUSB0 @ 9600 failed. Starting Auto Search...
2019-03-08T16:03:24: [WARNING] Port /dev/ttyUSB0 is already used by another driver or process.
2019-03-08T16:03:21: [INFO] Session log file /home/ron/.indi/logs/2019-03-08/indi_lx200ap_experimental/indi_lx200ap_experimental_16:03:21.log
2019-03-08T16:03:21: [INFO] Debug is enabled.

only 3 tabs appear?

I would start by disconnecting _everything_ else and just keeping the mount USB connected. I suggest you try to assign permanent designations for your ports otherwise the driver will keep searching all over the ports trying to find which one responds. While I tried to improve this recently, it can lead to conflict among driver trying to compete for access to the ports.