search

PiInTheSky / pits

Pi In The Sky Telemetry Software
GNU General Public License v2.0
87 stars 49 forks source link

Updating PITS software..? #29

Closed labjg closed 6 years ago

labjg commented 6 years ago

Not really an issue, but a request..

I have a PITS-Zero board here, which was purchased earlier in the year and comes pre-assembled and with Raspbian Jessie Lite & PITS software pre-loaded onto the SD card.

I wanted to update PITS to get the latest features, so renamed the ~/pits directory and cloned and built the latest repo as per the PITS manual.

I also did an apt-get update and apt-get dist-upgrade, but have since recreated at least some of the issues below without doing this (after restoring old SD card image and going through the process again).

Running the tracker in the terminal gave errors concerning wiringPi and PIGPIO, so re-installed those and cloned/built the PITS software again. Things then seemed to work on reboot, but killing the startup tracker and instead running ./tracker in the terminal seems to stop images being sent (not clear why). Also I noticed that the telemetry strings don't contain the internal temp data any more.

It would appear that I've upset something and might be best rolling back to my backup of the shipped SD card software, or starting from scratch with Stretch.

So really I'd just like to know how to properly update the PITS software in future. I can't find any guidance on this. Maybe an addition to the README would help others..?

I'd also welcome more explicit instructions on doing a fresh install for the Zero, as currently the manual just states that 'you don't need to do this because it's pre-installed'. Is any of the Serial port and/or PiV3 bluetooth fussing applicable to the Zero?

Thanks folks.

labjg commented 6 years ago

Update: Did a fresh install of Stretch Lite and followed PITS manual to install everything else (ignored PiV3 bluetooth stuff).

Same issues. Startup process transmits image frames, but 'sudo ./tracker' does not. No temperature measurement in telemetry string.

daveake commented 6 years ago

sudo ./tracker just runs the tracker, and not the camera script. If you view the startup script you'll see what it does.

Pi Zero (as supplied in the kits) does not have bluetooth; Pi Zero W does.

For updating see the section on that subject at the bottom of http://www.pi-in-the-sky.com/index.php?id=sd-card-image-from-scratch. I'll get that added to the manual.

labjg commented 6 years ago

Ok, thanks. Could have sworn I used to see things like 'sending image packet x of y' on the ./tracker terminal output. Ho hum, no worries then.

Still not sure why the telemetry string internal temp measurement was showing on the old version but now is not. I don't usually have GPS lock at my desk, but I can't imagine that's why. Any ideas?

daveake commented 6 years ago

It'll still show "sending image packet..." from the tracker if there's a leftover image from before the camera script was stopped;l once that image is sent then it'll revert to telemetry only.

Looks like the temperature code isn't being loaded if the software detects it's running on a Zero; I'll get that sorted. The temperature comes from the GPU as there's no separate sensor on the PITS Zero board, but as the code isn't being loaded then it's not measuring that either.

Dave

On 14 September 2017 at 11:53, James Gilbert notifications@github.com wrote:

Ok, thanks. Could have sworn I used to see things like 'sending image packet x of y' on the ./tracker terminal output. Ho hum, no worries then.

Still not sure why the telemetry string internal temp measurement was showing on the old version but now is not. I don't usually have GPS lock at my desk, but I can't imagine that's why. Any ideas?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/PiInTheSky/pits/issues/29#issuecomment-329446860, or mute the thread https://github.com/notifications/unsubscribe-auth/ABBodIfccNBNlbjyHuEdZkyLVu38CZL0ks5siQW-gaJpZM4PXEwp .

labjg commented 6 years ago

Righto; thanks Dave.

emdeex commented 6 years ago

I'm trying to update my Pi Zero from Uputronics as well. It appears to have shipped (Jan 2018) with version "25/09/2016", which seems odd, considering the multiple updates since then.

The main problem I'm having is actually getting a terminal on the Pi Zero... I finally got a mini-HDMI convertor, but plugging it in to my display is getting a blank screen.

Is there is a SSH daemon running on the Pi by default, I can't see any details of it. Getting a network adaptor running, considering not having a display working yet will be tricky.

Perhaps it would be a good idea to put a WiFi AP credentials section in the /boot/piesky.txt, so the tracker can connect to the local network and be accessible via ssh?

daveake commented 6 years ago

We don't disable HDMI output by default, so that should work as on any Pi. Be sure to have the monitor connected before you apply power.

ssh should be enabled on the supplied SD card, so if you connect a USB LAN adapter can get the IP address from your router and connect that way.

Or you can put your WiFi details on the card. I've not done yet myself but it's standard Raspbian (and nothing to do with pisky.txt).

The supplied pits software is fully functional and there have been no significant changes since then for pits zero.

Dave

On 10 Feb 2018 7:17 a.m., "emdeex" notifications@github.com wrote:

I'm trying to update my Pi Zero from Uputronics as well. It appears to have shipped (Jan 2018) with version "25/09/2016", which seems odd, considering the multiple updates since then.

The main problem I'm having is actually getting a terminal on the Pi Zero... I finally got a mini-HDMI convertor, but plugging it in to my display is getting a blank screen.

Is there is a SSH daemon running on the Pi by default, I can't see any details of it. Getting a network adaptor running, considering not having a display working yet will be tricky.

Perhaps it would be a good idea to put a WiFi AP credentials section in the /boot/piesky.txt, so the tracker can connect to the local network and be accessible via ssh?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/PiInTheSky/pits/issues/29#issuecomment-364632245, or mute the thread https://github.com/notifications/unsubscribe-auth/ABBodHmYmAwdSk9rdGGdEpC4-cAXYjjHks5tTUKFgaJpZM4PXEwp .

emdeex commented 6 years ago

thanks Dave, not sure why the display is not working... I'll keep trying.

I'll try the USB LAN adapter... what's the credentials required for SSH?

With the WiFi details, any hints on getting that working without being able to log in yet? Are there settings on the /boot/ directory I can tweak?

OK, I see in regards to the pits version... if the changes are not required for successful flights, I'll might just leave it as is... thanks!

daveake commented 6 years ago

We've not changed the normal pi/raspberry login.

I don't know how the WiFi stuff is done as I've never set it up that way.

Dave

On 10 Feb 2018 8:58 a.m., "emdeex" notifications@github.com wrote:

thanks Dave, not sure why the display is not working... I'll keep trying.

I'll try the USB LAN adapter... what's the credentials required for SSH?

With the WiFi details, any hints on getting that working without being able to log in yet? Are there settings on the /boot/ directory I can tweak?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/PiInTheSky/pits/issues/29#issuecomment-364637257, or mute the thread https://github.com/notifications/unsubscribe-auth/ABBodDTc1s9KoXtRHXbO-FXVY1U67KTXks5tTVongaJpZM4PXEwp .