×

INDI Library v1.9.6 Released (21 May 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

RPI4 experience - Not so good

  • Posts: 211
  • Thank you received: 26
Hi,

Been working some time with Nina under W10 but because of the bulky pc was looking for something smaller. Having used Indi with success in the past got myself an RPi4, installed Astroberry, disabled wireless 5Ghz (usb!) and happily started.

Good chance to test the Peg. UBP V2 driver I am currenly hoping to get bugfree.

Setup is:
Rpi 4 - Kstars - Ekos / Phd2
Ioptron mount connected to USB2 on Rpi
Peg. Powerbox V2 connected on USB3 on Rpi
SX Filterweel - ASI178 - Atik314 - Pegasus DMFC Focuser

Goes wel for a while although the ASI178 (or any other ASI, tested that later) generates a line in messages and syslog with Reset of the device every time a exposure is done. (PHD2 as well as Ekos) (Reset SuperSpeed Gen 1 device ...)

At a certain moment USB disconnects the Atik.

Syslog / Messages -> show a disconnect of the device and it connects as a new device with different number.

Ekos now gets confused and does not see the device anymore
[2020-05-07T00:31:02.065 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:31:02: Driver indi_atik_ccd: libusb: error [udev_hotplug_event] ignoring udev action bind"
[2020-05-07T00:31:02.066 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2020-05-07T00:31:02.741 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[ERROR] Cooling Info inquiry failed (3) "
[2020-05-07T00:31:03.742 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[ERROR] Cooling Info inquiry failed (3) "
[2020-05-07T00:31:04.743 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[ERROR] Cooling Info inquiry failed (3) "
[2020-05-07T00:31:05.744 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[ERROR] Cooling Info inquiry failed (3) "
[2020-05-07T00:31:06.744 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[ERROR] Cooling Info inquiry failed (3) "
[2020-05-07T00:31:07.744 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[ERROR] Cooling Info inquiry failed (3) "
[2020-05-07T00:31:08.745 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[ERROR] Cooling Info inquiry failed (3) "
[2020-05-07T00:31:09.746 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[ERROR] Cooling Info inquiry failed (3) "



This goes on until I reset the USB port with the powerbox controller.
Then the drivers crashes, restarts and connects again

[2020-05-07T00:34:53.381 CEST INFO ][ org.kde.kstars.ekos.capture] - "Cooler is on"
[2020-05-07T00:34:53.385 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[INFO] Camera cooler is on. "
[2020-05-07T00:34:53.386 CEST INFO ][ org.kde.kstars.ekos.capture] - "Cooler is on"
[2020-05-07T00:34:53.391 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[ERROR] Cooling Info inquiry failed (3) "
[2020-05-07T00:34:56.706 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[ERROR] Failed to set temperature (4). "
[2020-05-07T00:34:56.706 CEST INFO ][ org.kde.kstars.ekos.capture] - "Cooler is on"
[2020-05-07T00:34:56.711 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[ERROR] Cooling Info inquiry failed (3) "
[2020-05-07T00:35:07.127 CEST INFO ][ org.kde.kstars.ekos.capture] - "Capturing 60.000-second L image..."
[2020-05-07T00:35:29.667 CEST INFO ][ org.kde.kstars.ekos.capture] - "CCD capture aborted"
[2020-05-07T00:35:59.309 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[ERROR] Failed to set temperature (4). "
[2020-05-07T00:35:59.315 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[ERROR] Cooling Info inquiry failed (3) "
[2020-05-07T00:36:28.450 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[INFO] Taking a 60 seconds frame... "
[2020-05-07T00:36:28.457 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[ERROR] Cooling Info inquiry failed (3) "
[2020-05-07T00:36:28.547 CEST DEBG ][ org.kde.kstars.indi] - INDI server disconnected from BLOB manager for Device: "Atik 414ex" Property: "CCD1" Exit code: 0
[2020-05-07T00:36:28.548 CEST DEBG ][ org.kde.kstars.indi] - INDI server disconnected from BLOB manager for Device: "Atik 414ex" Property: "CCD1" Exit code: 0
[2020-05-07T00:36:28.553 CEST INFO ][ org.kde.kstars.indi] - Atik 414ex : "[INFO] Camera is offline. "
[2020-05-07T00:36:28.554 CEST DEBG ][ org.kde.kstars.ekos] - "Atik 414ex" is disconnected.
[2020-05-07T00:36:28.554 CEST INFO ][ org.kde.kstars.ekos] - "Atik 414ex is disconnected."
[2020-05-07T00:36:28.559 CEST DEBG ][ org.kde.kstars.indi] - Removing device "Atik 414ex"
[2020-05-07T00:36:28.576 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:28: Client 19: read EOF"
[2020-05-07T00:36:28.577 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:28: Client 19: shut down complete - bye!"
[2020-05-07T00:36:28.577 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:28: Driver indi_atik_ccd: stderr EOF"
[2020-05-07T00:36:28.577 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "<delProperty device=\"Atik 414ex\"/>"
[2020-05-07T00:36:28.577 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "Child process 6192 died"
[2020-05-07T00:36:28.578 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:28: Driver indi_atik_ccd: Terminated after #0 restarts."
[2020-05-07T00:36:28.578 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2020-05-07T00:36:28.578 CEST CRIT ][ org.kde.kstars.indi] - INDI driver "indi_atik_ccd" crashed!
[2020-05-07T00:36:28.610 CEST DEBG ][ org.kde.kstars.indi] - INDIListener: Removing device "Atik 414ex"
[2020-05-07T00:36:28.611 CEST INFO ][ org.kde.kstars.ekos] - "Atik 414ex is offline."
[2020-05-07T00:36:34.628 CEST DEBG ][ org.kde.kstars.indi] - Stopping INDI Driver "indi_atik_ccd"
[2020-05-07T00:36:34.629 CEST DEBG ][ org.kde.kstars.indi] - Removing managed driver "Atik"
[2020-05-07T00:36:34.646 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: stop indi_atik_ccd"
[2020-05-07T00:36:34.647 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "dp->name: indi_ieq_telescope - tDriver: indi_atik_ccd"
[2020-05-07T00:36:34.647 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "dp->name: indi_atik_ccd - tDriver: indi_atik_ccd"
[2020-05-07T00:36:34.647 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "dp->name: indi_sx_wheel - tDriver: indi_atik_ccd"
[2020-05-07T00:36:34.648 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "dp->name: indi_dmfc_focus - tDriver: indi_atik_ccd"
[2020-05-07T00:36:34.648 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "dp->name: indi_pegasus_upb - tDriver: indi_atik_ccd"
[2020-05-07T00:36:34.648 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2020-05-07T00:36:35.630 CEST DEBG ][ org.kde.kstars.indi] - Adding managed driver "Atik"
[2020-05-07T00:36:35.630 CEST DEBG ][ org.kde.kstars.indi] - Starting INDI Driver "indi_atik_ccd"
[2020-05-07T00:36:35.631 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: start indi_atik_ccd"
[2020-05-07T00:36:35.631 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: Starting driver indi_atik_ccd"
[2020-05-07T00:36:35.632 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2020-05-07T00:36:35.633 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:35: Driver indi_atik_ccd: pid=11380 rfd=5 wfd=19 efd=23"
[2020-05-07T00:36:35.633 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2020-05-07T00:36:36.760 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD"
[2020-05-07T00:36:36.762 CEST DEBG ][ org.kde.kstars.indi] - Received new device Atik 414ex
[2020-05-07T00:36:36.763 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on Telescope Simulator.TELESCOPE_INFO"
[2020-05-07T00:36:36.764 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD"
[2020-05-07T00:36:36.764 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on Telescope Simulator.TELESCOPE_PIER_SIDE"
[2020-05-07T00:36:36.764 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2020-05-07T00:36:36.773 CEST DEBG ][ org.kde.kstars.indi] - INDIListener: New device Atik 414ex
[2020-05-07T00:36:36.773 CEST INFO ][ org.kde.kstars.ekos] - Ekos received a new device: "Atik 414ex"
[2020-05-07T00:36:36.774 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on Rotator Simulator.ABS_ROTATOR_ANGLE"
[2020-05-07T00:36:36.775 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on Focuser Simulator.ABS_FOCUS_POSITION"
[2020-05-07T00:36:36.775 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on CCD Simulator.FILTER_SLOT"
[2020-05-07T00:36:36.775 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on CCD Simulator.FILTER_NAME"
[2020-05-07T00:36:36.775 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on SQM.SKY_QUALITY"
[2020-05-07T00:36:36.776 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on iOptron CEM60.EQUATORIAL_EOD_COORD"
[2020-05-07T00:36:36.776 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on iOptron CEM60.TELESCOPE_INFO"
[2020-05-07T00:36:36.776 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on iOptron CEM60.GEOGRAPHIC_COORD"
[2020-05-07T00:36:36.777 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on Pegasus DMFC.FOCUS_ABSOLUTE_POSITION"
[2020-05-07T00:36:36.777 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on SX Wheel.FILTER_SLOT"
[2020-05-07T00:36:36.777 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2020-05-06T22:36:36: Driver indi_atik_ccd: snooping on SX Wheel.FILTER_NAME"
[2020-05-07T00:36:36.778 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""


So is this really crap USB ports on the Rpi or still interference with Wifi. I will do another try with network cable when weather permits, but have no real hope.

Really like Indin but if I can't get the cam working reliabel then there is no reason to continue with the Rpi, and I will have to go back to NINA.


Paul



And another thing although it says it is snooping on my focuser, focus position in Fits files are always 0 (instead of the current focus position)
2 years 2 weeks ago #53350

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

  • Posts: 379
  • Thank you received: 113
Two immediate thoughts to your post. First, you shouldn't disable 5Ghz! It's 2.4Ghz wireless that interferes with USB3. Use a (separately) powered USB3 hub for ALL devices, and don't have anything but the data cable from that hub going back to the Pi4. Second, you'll want to make sure your power supply is up to the task. I have a 15W buck converter (12V from my PPB to 5V) to power the PI, and I use a 10A power supply (overkill but it gives confidence) to power everything else. A couple of luxuries makes a difference; an SSD (which I find is invaluable over the SD card), and a micro switch (so I don't have to plug/unplug the PI4 connector). Look at my signature below....I've got a pretty similar setup to what you're trying, and it works great. I wouldn't go back to a windows config. Good luck... Doug

Edit: If you still struggle after isolating your PI4, and you KNOW your power situation is ok, then try the ethernet for sure. I don't have the option of 5Ghz at my location, so I use an ethernet cable and it works great.
RASA11, Celestron CGX-L, ASI183mc Pro, 60mm guider + ASI290mm mini, ASI EAF focuser, PPB, Rpi4-4Gb+SSD, Powered USB3 hub, hardwire Ethernet.
Last edit: 2 years 2 weeks ago by Doug S.
2 years 2 weeks ago #53356

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

  • Posts: 211
  • Thank you received: 26

Replied by PDB on topic RPI4 experience - Not so good

Yes you are right, not enough sleep, it the other wifi. I am now testing with the config (except the mount) and an plain 1gbit ethernet cable to see how that works. The resets on the ASI are stil there seems to be the way the library works. (in video mode, FireCapture there is no reset but lost frames, not abnormal with an 178, you need a real good USB3 and fast processor to handle that)
As for the power supply, using the 3A Raspi one. And there is not that much load on USB since the Pegasus Box powers the hub. If I get everything to work it will probably over cable and not really using Kstars on rpi, but remotely from my machine inside. (Then the network must be stable, since loosing the connection quits the session)
I was thinking of powering the Rpi over pin 4 & 6 on the GPIO, done that with older Pi's because of the crappy powerconnector. Just a jack and 5.2 V to the GPIO. The new connectors are a lot better.

There are a few things in Nina that probably be in Indi as wel (or I did not see them) Timed cool down and warm-up time of the CCD (Indi cools very fast, and warm-up is fast as well). Better in Indi is the flat wizzard. Much faster and better than in Nina. Focus on multistar better in Nina, but more hardware in Indi.

Regards,

Paul
What I woul really see in Indi is that Ekos would be separated from Kstars (less crashes? Yes they still exists) but would have a link to planetarium program of choice. Also missing are FLATDARKS. Both are lacking a filter setting for Darks (I use a dark filter as shutter for the ccd; so I have to manually set the filter before starting the darks)

Let you know my re
Last edit: 2 years 2 weeks ago by PDB.
2 years 2 weeks ago #53359

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

  • Posts: 379
  • Thank you received: 113
The PI4 can run kstars fine (a bit slower than the PC, but you don't use the planetarium function all that much....it's Ekos that gets the workout). For the exact reason you mentioned, I use Kstars/Ekos on the Pi4 and not the PC. I agree that having Ekos separate from Kstars would be nice (I'd then run Kstars on the laptop and Ekos&INDI on the Pi4, but that's not an option). So, it's not that much of a sacrifice in performance to run Kstars&Ekos on the PI (along with INDI).

Ok, back to your config....you really do need to have a separately powered USB3 hub for EVERYTHING. The PI4 entices you with all those USB ports, but trust me....you won't have the power you need. You only have a 3amp power supply to the PI4, and a single USB3 port alone can require (by spec) almost 1amp. It's most likely not the ASI driver that's having a problem, it's the PI4 power output. You get REALLY funky results once the power to the PI4 starts to falter from draw to the USB ports. Two USB3 ports + two USB2 ports would require 2+1 = 3amps by themselves, and then there would be ZERO left for the PI4's processor, WIFI, HDMI, etc. I have a much bigger format camera (183), and it functions fine, but not by the PI4....by the USB3 hub. So your problems with what you think are the ASI driver are probably not what you think.....

Edit: One more thought....I recommend not going direct to the GPIO pins for power, as you'll want to save those for a fan (and maybe an RTC). The PI4 WILL run hot, and I'd consider a fan a necessity. If you try to go without and it gets too warm, it will auto CPU throttle and then performance will really suffer.
RASA11, Celestron CGX-L, ASI183mc Pro, 60mm guider + ASI290mm mini, ASI EAF focuser, PPB, Rpi4-4Gb+SSD, Powered USB3 hub, hardwire Ethernet.
Last edit: 2 years 2 weeks ago by Doug S.
2 years 2 weeks ago #53361

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

  • Posts: 211
  • Thank you received: 26

Replied by PDB on topic RPI4 experience - Not so good

Well the fans are indeed now connected to those pins that why I still use the normal power supply for now. (and cooler blocks) Normal temp reported by vcgencmd is ~35°
Latest test everything was on the powered hub. The pegasus UPBV2 has a powered hub (And I feed that by a PS capable of giving 12A, but the box is secured at 10A)
So the ASI and ATIK are not directly on the PI. In theory the ports should not consume much. Yesterday had the box + the mount, but a serial usb convertor should not draw much on a USB2 port, but I can move that to the box as wel. (did not do it because of a moving cable from box to mount, but i can tie that one nicely so it doen't "float") Nothing else connected, so no hdmi, no keyboard, no mouse ... But 2 fans, so maybe these take all the energy.
I know how much current USB3 (and USB2) can use, so that why I got that UPB box. (and to get all power and usb nicely together. It not cheap, but it works great)

But still I see the resets on the ASI cams. Think I will dig in the code to see wat sequence of commands is give to the ASI SDK.

So still some testing to do.

P.
2 years 2 weeks ago #53363

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

  • Posts: 379
  • Thank you received: 113
Ah...didn't realize the V2 had a powered USB on-board. I'd use that for everything possible. Once you figure out the ASI resets, please post so we'll all know. It's a mystery to me given that I have 3 ASI devices (simultaneous use of 2 cams + focuser) and I don't see any resets. Good luck...
RASA11, Celestron CGX-L, ASI183mc Pro, 60mm guider + ASI290mm mini, ASI EAF focuser, PPB, Rpi4-4Gb+SSD, Powered USB3 hub, hardwire Ethernet.
2 years 2 weeks ago #53364

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

  • Posts: 211
  • Thank you received: 26

Replied by PDB on topic RPI4 experience - Not so good

the reset seems "normal" see ZWO forum bbs.astronomy-imaging-camera.com/viewtop...lit=usb+reset#p34296
so no problem only large logging files. Next time you image check /var/log/messages (do a tail -f) to see if you don't get that message.

Regards,

Paul

Now extensive testing with 5Ghz wifi. So far no problems with the Atik. So starts looking good.
2 years 2 weeks ago #53367

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

  • Posts: 981
  • Thank you received: 374

I have experienced myself the problem with Atik cooling error in the past. Very annoying indeed, but I believe it is related to lousy USB cables. The issue is gone after I changed mines.
--
Radek Kaczorek
Astroberry Server | Orion CT8 | Askar FRA 400 | NEQ6 (hypermod) | Atik 460EX | ASI 1600 | ASI 120MM | Atik EFW2
2 years 2 weeks ago #53380

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

  • Posts: 211
  • Thank you received: 26

Replied by PDB on topic RPI4 experience - Not so good

USB cables can be a pain but in this case the exact same hardware combination runs for hours without problems from W10 on an AMD cpu. So probably the 2.4 GHz interference. With cabled network seems to be ok (tested 100x60sec images without problems, but stil need to test with cooler on). 5Ghz network, seems to loose connection with the router now and then, but the Netgear Genie is not the best Wifi router I had. (fine on 2.4 but the 5Ghz band ?)

USB an Linux are not the best friends. For my solar I had to switch back to Linux. On the same PC (AMD CPU, not the Pi) there was a huge difference in USB speed and lost frames with an ASI178. Booting with Ubuntu the cam was loosing frames all the time an speeds jumping frol 5 to 25fps. Under w10 same PC same cam, a stable 30fps.
(both tested with FireCapture, but othe capture programs unde Ubuntu showed the same behaviour) So either the ASI lib or the USB implementation in Linux. For deep sky of course this is no problem, those high transfer rates are not needed, and there I really prefer the small size of the PI over an big PC.


Paul
2 years 2 weeks ago #53391

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

  • Posts: 22
  • Thank you received: 4
The PI4 is picky on the power. The official PI4 power adapter is 5.1 V. I have an adjustable power brick set to 5.2V, and the PI is connected to both asi294mc, asi120mm, and eqdir directly without hub. I just keep the WiFi active. WiFi performance is poor due to USB3 interference, so I have cabled Ethernet to my windows laptop running kstars. Pi 4 is running astroberry. Very stable setup.
2 years 2 weeks ago #53399

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

  • Posts: 379
  • Thank you received: 113
On 2.4Ghz vs 5Ghz, and the surprising result that your 5Ghz isn't quite as stable (dropped connections), it's likely just a distance (or obstruction) thing. 5Ghz range isn't as good as 2.4Ghz. On power, I think it would be wise for you to at least run an experiment where all your devices (except the Pegasus V2 data connect) are not on the Pi's USB ports. Then you'll have the best sense of true stability. Even though the run-time power draw from 3 devices might be low, the transients might be interesting enough to cause instability at awkward moments (boot). To know for sure, it probably warrants an isolation test to be sure that the Pi4's power supply is only powering the core Pi4 as you make final conclusions. Just a thought...
RASA11, Celestron CGX-L, ASI183mc Pro, 60mm guider + ASI290mm mini, ASI EAF focuser, PPB, Rpi4-4Gb+SSD, Powered USB3 hub, hardwire Ethernet.
Last edit: 2 years 2 weeks ago by Doug S.
2 years 2 weeks ago #53416

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

  • Posts: 211
  • Thank you received: 26

Replied by PDB on topic RPI4 experience - Not so good

The Pi isnt cooperating. After several test with the network now working as expected, doing the compilation of my new version of the UPB2 on the pi, Astroberry NOVNC suddenly disconnected. First Ithinking it was the wireless again, switched to cable, no luck. But could still access via ssh. So reboots or shutdownn and restart, no way to get the vnc connection running again. Tried a monitor, black screen (but that could be normal with astroberry settings). Via ssh no problem accessing, via VNC or the web noVNC no connection. Luckally I made a backup of the SD card with the "final" config on friday, so restoring that. Might be a problem with the SD card. (the 11th commandment "Thou shall make backups")

P
2 years 1 week ago #53603

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

Time to create page: 0.865 seconds