BlueOS manual upload failed

Blue Robotics Software BlueOS
1

Hi everyone,

The running BlueOS is 1.3.1, uploaded manually 1 years ago(remote upload is not working). i try to upload the lastest 1.4.2 for extensions installation as it alwars said pull extensions failed, arm-v7.tar docler image was downloaded for the Pi 4B, after decompressing files, it always displays loading local version, after restart, the running version is still 1.3.1. do you have any advice to upload the lastest BlueOS and get the extension what i need? many thanks.

2

one more thing, i can download code from github

3

Hi @Alexu,

There was a known memory management issue with extracting manually uploaded BlueOS updates which has been largely resolved in the BlueOS 1.5 betas, but that’s unhelpful for systems on older / stable releases.

The simplest instructions are to flash the relevant Raspberry Pi image of the BlueOS version you want to use onto the SD card, but that loses any configuration and data you currently have saved on the vehicle (assuming it isn’t already backed up elsewhere).

If keeping that configuration is important, you can try the following steps:

  1. Turn on Pirate Mode
  2. Go to the BlueOS Terminal page
  3. Type red-pill and press Enter, to access the underlying Raspberry Pi hardware
  4. Type sudo nano /etc/dphys-swapfile and press Enter
  5. Check that CONF_SWAPSIZE=1024 (or larger)
  6. If not, you can navigate with your arrow keys and change it
  7. Press CTRL+x to close the editor (and Y to save your change, if you made one)
  8. If you changed the swap, you’ll need to reboot your Raspberry Pi for it to take effect, then open the Terminal page again - otherwise you can just type exit and press Enter to return to the BlueOS core docker container
  9. Next press CTRL+b then s, to access the terminal windows for the BlueOS core services
  10. Use the up/down arrows to navigate to the versionchooser window option, and press Enter to select it
  11. Press CTRL+c to kill the running service
  12. Press the up arrow (once) to see the command it was running from, then change the 250 to a 0 and press Enter to re-run the version chooser (without its default memory limit)
  13. Go to the BlueOS Version page via the sidebar, and try your manual upload again (which will hopefully complete this time)

If that doesn’t help you can try getting your latest system logs (from the settings icon at the bottom of the BlueOS sidebar) and uploading them here for us to look into, but it might take a while to investigate, and we may not be able to resolve the issue.

4

Hi Eliot,

Thank you, it is working, i got the 1.4.2 BlueOS. just in case someone like me not good at command to go right way, please add ‘sudo’ before nano /etc/dphys-swapfile

unlucky, pull extentsion is still failed, the button Get changed to INSTALLED when pulling. DWE USB 2.0 camera MJPG encoding is on vehicle, but no video stream came out in BlueOS, i plan to install DWE OS to get the stream and dashcam to record the video on board. beside Flash, any way to get them quickly? as we not only require both of them, more entensions is required.

5

Nice!

Added - thanks :slight_smile:

I missed that you were trying to install extensions - how is it failing? It would be helpful if you can provide any relevant error messages, and/or your latest system logs (from a session where you’ve tried to install extensions).

What do you mean by this? What do you see in the BlueOS Video Streams page, and how are you trying to receive/view the video stream?

BlueOS 1.5 adds manual extension installation capabilities (and currently automatically performs onboard video recording of available streams while the vehicle is armed), which might be worth trying if the normal installation process doesn’t work (but you’ll need to update to a beta software version to access that, with pirate mode enabled).

6

Default camera on video2 is working well, MJPG on video0 always display the stream of video2, while BlueOS is 1.3.1, the first time MJPG USB 2.0 camera is plugged, it display well, more information for your reference.

7

image
image748×612 84 KB

please see the notice, the system logs is more than 20M, can’t be uploaded. what exactly you need?

8

thanks, will try this tomorrow.

9

668dd06c4ba0b15dd1737820f07b8dce
668dd06c4ba0b15dd1737820f07b8dce838×725 75.2 KB

244278031a005edbd27bf4bc1269b835
244278031a005edbd27bf4bc1269b835828×705 68.9 KB

please see above, try different port, UDP or RTSP alsway get the same stream.

10

Those endpoints seem to be two endpoints for the same camera. It is not uncommon for a camera with H264 encoding capabilities to present itself as two separate devices, one which provides the H264 stream, and the other which provides the less heavily encoded YUYV and MJPG stream options.

With pirate mode disabled only the H264-encoded streams get shown, as they are more efficient for transport bandwidth and better supported by receivers/display software. If pirate mode is enabled then we show all detected streams, with the idea that a “pirate” user either knows what they’re doing, or is willing to play around and break things.

Are there any other devices / stream options being shown in the Video Streams page? If not it’s possible your other camera is not being detected (so maybe there’s an issue with its connection to the Raspberry Pi, or its power supply).