Ah, thanks. I hadn't seen that one before.
Is that the only time that the mount would attempt to auto-park? Is so, then that's the only option I need.
I have an iOptron CEM25p and I can never get parking to work reliably.
Once or twice it has worked, but usually it doesn't and any time the mount attampts to park (like after a polar alignment) I have to be there poised over the stop button to prevent the mount from being driven into the tripod legs.
I'm starting to leave sessions running when I go to bed now, but I'm worried that at some point something may try to park the mount and it might spend hours grinding the gears as it smashes the mount into the tripod before I'd realise it had happened.
Would it be possible to add a "Disable Parking" option that would prevent a park command from ever being issued?
Or better yet an option to "Use Goto Home instead of park" as that does work properly?
dmnkhhn wrote: Do you know any kernel version that supports the USB-C port on the RockPro64? I might not need a hub if this one it's usable.
No, sorry the USB-C on my NanoPi is only for power, not data.
dmnkhhn wrote: I don't think this other issue is directly related to my problem but I have debugged it further.
The same error occured with Ubuntu Mate so I dug even deeper and I came across a topic on the official ZWO ASI forums where they were talking about different kernel versions (see bbs.astronomy-imaging-camera.com/viewtopic.php?t=8253 )
The error message I got from _dmesg_ was
Ring expansion failed
usbfs: usb_submit_urb returned -12
My kernel version was 4.4.189-1230-rockchip-ayufan-gafadea9477b7 so I upgraded to 5.0.0-1092-ayufan-g58b7aac480ae and my issues were gone.
Now the USB-C port isn't working but the camera connected to the regular USB 3.0 port works without any problems and as a big plus the amp glow got better.
Yep, that's the same error that I had. I can't find a v4 kernel that fixes the problem, but v5 works fine
It's just stock armbian, so it's root and 1234
The image that I downloaded was
And the exact kernel version is "Linux nanopim4 5.3.0-rc4-rk3399 #5.93.190815"
It was already marked in Synaptic with an upgrade available, so I just selected it to do the upgrade
I will as soon as I can get to a desktop rather than being on mobile.
Basically though, I downloaded the dev build from January using the wayback machine.
Install the desktop using armbian_config.
Reboot to the desktop.
Use synaptic package manager to install the rk3399 5.3 kernel image.
I'll post links when I can.
Yep, that's what I've found. If I upgrade the kernel the machine doesn't reboot afterwards.
I have found a way to do it though, the dev image based on 4.19 has working wifi, if I upgrade the kernel through the package manager to a 5.3 rk3399 it works.
The machine can reboot and the usb and wifi work.
El Corazon wrote: Check out the synaptic package manager after installing Ubuntu MATE on the Nano-Pi. I skimmed over it quickly last night and I though kernels 4.15 and 4.18 were listed there.
I may be wrong, will have to check again tonight. If downgrading were possible, that would solve a lot of problems.
How do you install Ubuntu Mate on the M4? I can't see an image for it, just the RPi3 one and that doesn't work.
I bet it's all the same issue as I'm seeing with an ASI183MM and a NanoPi M4.
The problem is Linux kernel related, I see errors reported in dmesg when the camera fails to download the image.
I can find later kernel versions that fix the problem with USB3 cameras, but (so far) break the WiFi at the same time.
El Corazon wrote: Have you considered downgrading the kernel to 4.15?
I know that the cameras work without a hitch with that kernel on a different mini-PC.
I'd love to, but the only images I can find are either stable branch 4.4 or dev branch 5.3 ones.
FriendlyARM haven't released anything later than 4.4 for the NanoPi M4 and that's where Armbian pull the kernel from.
On the dev branch USB works fine, but I can't get WiFi to work. I can mostly live without it, maybe a USB WiFi stick will work for the few occasions that I need it. I'll try that out over the next few days.
I did find (using wayback machine) an old Armbian dev branch based on 4.19, but I haven't had a chance to try that one out yet. Maybe that will be OK, but as the kernel hasn't come from FriendlyARM, I bet there will be features missing
I don't think so, I built the OS by following the Armbian instructions. That uses a desktop Ubuntu 18.04 image to cross-compile for ARM.
I built it in a VirtualBox VM.
I had nighmares with VNC too, nothing I tried would work properly. I think I tried every single package available with VNC in the name.
In the end I got it got it working fairly easily using tigervnc-standalone-server and a systemd unit file to start the service