Differences

This shows you the differences between two versions of the page.

--- doc:appunti:hardware:sjcam-8pro [2022/04/29 09:45] – [Web References] niccolo
+++ doc:appunti:hardware:sjcam-8pro [2023/06/09 10:21] (current) – [SJCAM SJ8 Pro Review] niccolo
@@ Line 1: / Line 1: @@
-====== SJCAM SJ8 Pro ======
+====== SJCAM SJ8 Pro Review ======
-See also my other page about **[[ambarella_custom_firmware]]**.
 The **SJCAM SJ8 Pro** action camera was introduced in **2018**, it features **4k video** at **60 fps** and **gyroscope image stabilization**. I purchaesd it in 2021 to work alongside my old [[xiaomi_yi|Xiaomi Yi]], mainly because I was interested in image stabilization.
+{{.:sjcam:sjcam-sj8pro-backpack-mount.jpg?direct&600|The SJCAM SJ8 Pro mounted on the shoulder strap of a backpack}}
 Unfortunately SJCAM does not support this camera very much: the latest **firmware upgrade** is from September 2020, despite there are some evident bugs and several aspects of the user interface which should be improved. Thirdy part support is poor: there is no **waterproof case** except the original one, which unfortunately has a plastic window. There is not much documentation about **customizing the firmware** or scripting using the **Ambarella Scripting**.
+See also my other page about this camera:
+  * **[[sjcam-8pro-ambarella-firmware-modding]]**
+  * **[[sjcam-8pro-ambarella-wifi-api]]**
+  * **[[sjcam-8pro-custom-firmware]]**
+===== Specs, Pros and Cons =====
 **Pros**
@@ Line 118: / Line 126: @@
 ===== Color profiles =====
-The SJCAM SJ8 Pro has two **color profiles** selectable from the **Current Mode Settings** menu: **SJCAM - Vivid** and **Flat**. There is a firmware bug that prevent you changing the color profile if the Gyro Stabilizer is enabled, and the color profile choiche is not remebered after power off. In my opinion the vivid profile is too much saturated, specially it **enhances too much** the contrast from the **blue sky** and the **white clouds**, even when the sky is mainly gray and cloudy (as in the frames below). On the contrary the flat profile is **too much washed out** that you will hardly want to use it.
+The SJCAM SJ8 Pro has two **color profiles** selectable from the **Current Mode Settings** menu: **SJCAM - Vivid** and **Flat**. At bootstrap the camera select another profile, let's call it **Default**, which is identical to SJCAM -Vivid, but it is stored in a different place into the firmware, so it can be customized separately.
+There is a firmware bug that prevent you changing the color profile if the Gyro Stabilizer is enabled, and the color profile choiche is not remebered after power off. In my opinion the vivid profile is too much saturated, specially it **enhances too much** the contrast from the **blue sky** and the **white clouds**, even when the sky is mainly gray and cloudy (as in the frames below). On the contrary the flat profile is **too much washed out** that you will hardly want to use it.
 {{.:sjcam:color-profile-sjcam-vivid.jpg?direct&400|Color Profile SJCAM - Vivid}}
 {{.:sjcam:color-profile-flat.jpg?direct&400|Color Profile Flat}}
-You can edit the color profiles using the BitrateEditor software. But be careful that the profile selected at bootstrap is neither //SJCAM - Vivid// nor //Flat//, but another one stored in some other part of the firmware that I was unable to locate.
+You can edit the three color profiles //SJCAM - Vivid//, //Flat// and //Default// using BitrateEditor (required version 10.7 - Nov 3, 2021).
 ==== Flat vs SJCAM - Vivid ====
@@ Line 261: / Line 271: @@
 There are many hackers who produce modified versions of the original firmware. In general they distribute the original firmware patched in several places, mainly to customize framerates, exposure parameters, etc.
+I created a custom firmware to improve some video codec settings and to improve image quality (mainly color balance and saturation). You can find it here: **[[sjcam-8pro-custom-firmware]]**.
 Generally there is **no access to the source code**, so **patching the firmware binary** is a rather delicate task, requiring to know the exact offset of the data into that **specific version of the firmware**, the structure and the lenght of the data and eventually how to **update the embedded checksums**. SJCAM does not facilitate the task, because it distribute different versions of the firmares marked with the same version number.
@@ Line 266: / Line 278: @@
 The best approach is to use the **[[https://github.com/vmax1145/BitrateEditor|BitrateEditor]]**, a graphical Java program which facilitates the task of editing various parameters in form of **easy readable tables**. The program contains several configuration files, so it can check that you are actually editing the proper version of the firmware (it can do check of particular strings at particular offset, calculate regions checksums, etc.). The program has the capability to re-pack the firmware image after the edits, **updating the checksums** so that the file will be **flashable** into the camera.
-You can refer to the page **[[ambarella_custom_firmware]]** with my notes about customizing the SJ8 Pro firmware using BitrateEditor. You can also refer to the program I wrote which can extract files and partitions from the firmware files: **[[https://github.com/RigacciOrg/ambarella-h22-firmware-tools|ambarella-h22-firmware-tools]]**.
+You can refer to the page **[[sjcam-8pro-ambarella-firmware-modding]]** with my notes about customizing the SJ8 Pro firmware using BitrateEditor. You can also refer to the program I wrote which can extract files and partitions from the firmware files: **[[https://github.com/RigacciOrg/ambarella-h22-firmware-tools|ambarella-h22-firmware-tools]]**.
 ===== SD Card partitioning and formatting with GNU/Linux =====
@@ Line 637: / Line 649: @@
-===== TCP API =====
+===== The TCP API =====
-The camera offers an **API** over the **TCP protocol** on port **7878**. When the WiFi is on, you can open a telnet connection with it and exchange JSON messages to control the camera. This is the interface used by the official app.
+See the page **[[sjcam-8pro-ambarella-wifi-api]]** about the programming interface (API) offered by the SJCAM SJ8 Pro over the WiFi connection or even in localhost. The interface is offered on port **TCP/7878**.
-The protocol was at least partially **reversed engineered** (see the [[#web_references|web references]] below). I was able to **create a script** to select the Color Profile automatically at boot. Remember that, due a firmware bug, the color profile choiche is not preserved across reboots, and you have to disable the Gyro Stabilizer before selecting the Color Profile.
+The interface is based on **JSON messages**: you can exchange them over the WiFi connection as the official app **[[https://play.google.com/store/apps/details?id=org.jght.sjcam.zone|SJCAM Zone]]** does between the Android device and the camera. You can also **connect a PC** to the camera via WiFi and use any programming language supporting TCP sockets.
-Executing that script at camera startup is a rather convoluted process:
+You can also send messages from the camera itself: the **RTOS** operating system provides the **telnet** command which can ben used to talk to the **GNU/Linux** operating system running on the same camera, which handles the API requests (the camera actually runs two operating system simultaneusly: RTOS and Linux). In this scenario I was able to talk to the API but with no interaction: I used ''telnet'' to only send messages but I did not find any way to read the answers.
-  * At bootstrap, the RTOS executes the **autoexec.ash** Ambarella Script.
+===== Connecting to GNU/Linux via USB =====
-  * Using the command **t ipc rpc clnt exec2** it is possible to execute a script into the **GNU/Linux** operating system.
-  * The GNU/Linux environment has the **busybox** software, so it is possible to use the **telnet** command to establish a TCP connection with the API server at **localhost:7878**.
-  * The required **JSON commands** are sent to the API server to disable Gyro Stabilizer, select the Color Profile and then re enable Gyro Stabilizer.
-**WARNING**: It seems that the API implementation is rather buggy. I experienced several problems ranging from **commands not aknowledged** if sent with bad timing (not waiting enough time from one command to the next), even to suddenly **reboot**!
+If you connect the SJ8 Pro camera to a GNU/Linux computer using an USB cable, the Linux kernel will detect it, this is the **lsusb** output:
-Here there are the three files that must be created on the root directory of the SD card:
-**autoexec.ash**
 <code>
-sleep 5000
+Bus 001 Device 006: ID 070a:4026 Oki Electric Industry Co., Ltd A9 Platform
-t ipc rpc clnt exec2 '/tmp/SD0/autoexec.rc'
 </code>
-**autoexec.rc**
+The kernel inform also that the device is available as **USB Mass Storage**:
 <code>
-#!/bin/sh
+usb 1-1.1: new high-speed USB device number 6 using ehci-pci
-/tmp/SD0/api-set-options
+usb 1-1.1: New USB device found, idVendor=070a, idProduct=4026, bcdDevice= 0.01
-</code>
+usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
+usb 1-1.1: Product: A9 Platform
-**api-set-options**
+usb 1-1.1: Manufacturer: AmbarellaInc
+usb 1-1.1: SerialNumber: 0001
-<code>
+usb-storage 1-1.1:1.0: USB Mass Storage device detected
-#!/bin/sh
+scsi host6: usb-storage 1-1.1:1.0
-#
+scsi 6:0:0:0: Direct-Access     SJCAM    SJ8PRO           1000 PQ: 0 ANSI: 0
-# Send some commands to the TCP:7878 API.
+sd 6:0:0:0: Attached scsi generic sg3 type 0
-# Set the color profile to "SJCAM - Vivid" and enable Gyro Stabilizer.
-# We should get the token number from msg_id 257, but this script
-# is executed at boot, so the token should be always "1".
-T=1
-# A pause of 0.5 is required for each command to be completed.
-# By trial we discovered that a pause of 0.4 is not sufficient.
-S=0.52
-{
-  echo '{"msg_id": 257, "token": 0}'; sleep 1.5;
-  echo '{"msg_id": 2, "type": "Gyro Stabilizer", "param": "Off",           "token": '$T'}'; sleep $S;
-  echo '{"msg_id": 2, "type": "Color Profile",   "param": "Flat",          "token": '$T'}'; sleep $S;
-  echo '{"msg_id": 2, "type": "Color Profile",   "param": "SJCAM - Vivid", "token": '$T'}'; sleep $S;
-  echo '{"msg_id": 2, "type": "Gyro Stabilizer", "param": "On",            "token": '$T'}'; sleep $S;
-  sleep 1.0;
-} | telnet localhost 7878
-echo
 </code>