Crash_Override
/
OVMS3
2
0
Fork 0
Code Issues 5 Pull Requests Projects Releases 4 Wiki Activity

Update readme

This commit is contained in:
Carsten Schmiemann 2022-04-20 20:52:29 +02:00
parent 6f87132aee
commit 77e7740e1b
1 changed files with 19 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
README.MD
View File

@ -10,11 +10,13 @@ The fork is fixed at Version 3.3.002 with their provided modified ESP-IDF
## To-Do List
- [X] Integrate my server to assistant and server recommendation and add CA as well
- [ ] Integrate PIDs for reading values like odometer, battery cell voltage and so on, via OBD connector (because of gateway read-only)
- [X] Integrate PIDs for reading values like odometer, battery cell voltage and so on, via OBD connector (because of gateway read-only)
- [ ] Stable working firmware with reliable readings
- [ ] Create a custom dashboard, for more car status informations
- [ ] Accessing CAN bus after gateway to get full access to controllers use all available CAN bus interfaces OVMS hardware has
- [ ] Get more useful PIDs with direct access of CAN busses
- [ ] Try to control things like wake-up, charge control
- [ ] Implement own control routines like stopping charge after certain soc, try to control Cabine heaters to heat while charging (use debug commands to enable them)
- [ ] Try to control things like wake-up and charge control
- [ ] Implement own control routines like control cabine ptc heaters to heat while charging (use UDS test commands to enable them)
## Releases
@ -24,7 +26,7 @@ I will maintain main and edge version tag, please only flash main versions if yo
### Version numbers
Firmware versions will be named like openvehicles ones. I will add a dash with a counting number so I can signal if an update is available. If I push my fork to newest version from openvehicles, I increase original Firmware number.
Firmware versions will be named like openvehicles ones. I will add a dash with a counting number so I can signal if an update is available. If I push my fork to newest version from openvehicles, I increase original Firmware number. I will integrate changes from openvehicles if there is a code change in the main firmware only.
Example
> Version string: 3.3.002-cs131 <br>
@ -44,6 +46,7 @@ sudo python2.7 get-pip.py
## Build
Clone my repository and init submodules
```
git clone https://git.bit-cloud.de/carsten.schmiemann/OVMS3.git
cd OVMS3/
@ -72,13 +75,14 @@ source export.sh
```
Go to OVMS Folder copy sdkconfig for your hardware and build firmware
In this example for hardware 3.1 and above. You can customize it via make menuconfig
In this example for hardware 3.1 and above. You can customize it via make menuconfig.
```
cd OVMS.V3/
cp support/sdkconfig.default.hw31 sdkconfig
make -jX
```
X = number of cpu cores to speed up build process
Then upload built firmware to your webserver and flash it via OTA function in OVMS webinterface.
@ -87,7 +91,7 @@ Then upload built firmware to your webserver and flash it via OTA function in OV
## Security concerns
The OVMS3 project use an outdated and modified IDF, there are many security problems with them. Major problem is missing firewall so your webinterface and services like SSH is open to public ip of 3G/LTE interface. Most providers use an CG-NAT, but this is no a reliable protection at all.
The OVMS3 project use an outdated and modified IDF, there are many security problems with them. Major problem is missing firewall so your webinterface and services like SSH is open to public ip of 3G/LTE interface. Most providers use an CG-NAT, but this is not a reliable protection at all.
Many of used libraries are outdated too. For example mongoose webserver has a lot of security problems fixed with newer versions.
@ -97,14 +101,17 @@ I hope original project maintainers will fix them in the future, I know it is no
## OVMS Server
I use my own OVMS server, because I love privacy. So there are no push available only E-Mail for notifications.
I use my own OVMS server, because I love privacy. So there are no push messages available, only E-Mail for notifications.
You can use it too if you want, just register a account and vehicle at https://ovms.bit-cloud.de and point your OVMS module at https://ovms-server.bit-cloud.de Port 6870 with TLS enabled.
You need to insert my CA into your OVMS3, because I cannot proxy it with nginx and letsencrypt certificates so I used self signed certs.
You can use it too if you want, just register a account and vehicle at https://ovms.bit-cloud.de and point your OVMS module at https://ovms-server.bit-cloud.de Port 6870 (default) with TLS enabled or choose it at initial config wizard.
~~You need to insert my CA into your OVMS3, because I cannot proxy it with nginx and letsencrypt certificates so I used self signed certs.~~
My server ca is now included in this firmware.
~~Create a file called ovms-ca at /store/trustedca with bult in editor in the webinterface. (Create folder if not exist)~~
~~Paste content of ovms-ca.crt file to it and save it.~~
~~The go to the web shell or ssh and typ in ~~
Create a file called ovms-ca at /store/trustedca with bult in editor in the webinterface. (Create folder if not exist)
Paste content of ovms-ca.crt file to it and save it.
The go to the web shell or ssh and typ in
```
tls trust reload
```