There is a question that came in to support, regarding Smart ED. Can someone with experience of that car have a look, and help answer?
https://www.openvehicles.com/node/2335 <https://www.openvehicles.com/node/2335>
Battery display in the App
I have the smart ED 451. It has a 18 KWh battery and charges very slowly with max 3,7 KW. The display of the battery In the OVMS app is not quite right.
- In the green to the left it says 8 KWh. I assume this is the used power from full. So it should be on the other side, as the green area with 70% represents around 13 KWh of power remaining. However, the numbers don’t add up.
- to recharge fully I will need over 1 hr. But the app only estimates 16 mins. How can I change that?
Thanks, Mark.
I get a new computer with macOS Catalina. Now I want't to install the
developer environment. I use the following commands:
- sudo easy_install pip
- download :
https://dl.espressif.com/dl/xtensa-esp32-elf-osx-1.22.0-80-g6c4433a-5.2.0.t…
- mkdir -p ~/esp
- cd ~/esp
- tar -xzf ~/Downloads/xtensa-esp32-elf-osx-1.22.0-80-g6c4433a-5.2.0.tar.gz
- add this: “export PATH=$HOME/esp/xtensa-esp32-elf/bin:$PATH” to
~/.profile without quotes ””
Git clone the OVMS ESP IDF repository:
- git clone *https://github.com/openvehicles/esp-idf.git*
<https://github.com/openvehicles/esp-idf.git>
- cd esp-idf
- git submodule update --init –recursive
-add this: “export IDF_PATH=~/esp/esp-idf” to ~/.profile without quotes ””
Git clone the OVMS v3 repository and init the build configuration:
- git clone
*https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3.git*
<https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3.git>
- cd Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3
- git submodule update --init --recursive
- cp support/sdkconfig.default.hw31 sdkconfig
- make menuconfig
If I run the make app command I get the following error:
make app
Toolchain path: /Users/kommykt/esp/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc
Toolchain version: crosstool-ng-1.22.0-80-g6c4433a
Compiler version: 5.2.0
App "ovms3" version: 3.2.005-81-g00ab9db0
Generating esp32.project.ld
Traceback (most recent call last):
File "/Users/kommykt/esp/esp-idf/tools/ldgen/ldgen.py", line 113, in
<module>
main()
File "/Users/kommykt/esp/esp-idf/tools/ldgen/ldgen.py", line 88, in main
sections_infos.add_sections_info(sections_info_file_obj)
File "/Users/kommykt/esp/esp-idf/tools/ldgen/generation.py", line 618, in
add_sections_info
raise ParseException("File " + sections_info_file.name + " is not a
valid sections info file. " + p.message)
pyparsing.ParseException: File
/Users/kommykt/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/build/app_trace/libapp_trace.a.sections_info
is not a valid sections info file. (at char 0), (line:1, col:1)
make: ***
[/Users/kommykt/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/build/esp32/esp32.project.ld]
Error 1
Hi All,
I've been lurking here for a while still debating wether to ditch my autopi in favour of OVMS.
One thing thats held me back is to find a way to use the wifi hotspot as a NAT router - this is
useful to allow my sat nav to get traffic and charging point updates. As far as I can see on
the web page this isn't currently supported.
However I did see a couple of projects that adds NAT support to lwip :
https://github.com/martin-ger/lwip_nat_arduinohttps://github.com/jonask1337/esp-lwip
Does anyone know if adding NAT has a fighting chance ?
Cheers,
Pete
Hello all,
I've been wanting to have a bit more configurable notification system on my
mobile phone compared to the OVMS mobile app (quiet hours, different
message priority levels, override quiet hours with emergency priority,
custom sounds, persistent notifications demanding acknowledgment etc). I
already use Pushover as notification platform for my home automation system
and it has worked nicely for these two past years so I decided to port
Pushover client to OVMS as well.
For those who don't know, Pushover is a notification platform that has apps
for iOS and Android. They also have a desktop (actually web) application as
well. You create an account and then register your application. There's a 5
USD per platform one-time fee, which I find quite reasonable. Message limit
is 7500 messages / month / application. So if you have multiple cars, you
could register them as individual applications. I'm not affiliated with
the company, just a happy customer.
There are now commits for Pushover support on my fork (
https://github.com/mjuhanne/Open-Vehicle-Monitoring-System-3) It's up to
date with the main branch, and has the SWCAN commits as well. I would
appreciate if others could test it before making a pull request, since
there are now quite many changes. I didn't want to add another http
client, so I used Mongoose. But then after enabling SSL support using
mbedssl I found out that there's this client space "struct mg_connect_opts"
that will be too small (and causes crash) if MG_ENABLE_SSL is not enabled
also in every component that uses Mongoose.
To configure Pushover, there's a new Config/Notifications page on OVMS. You
can filter which notifications and events will be relayed and select their
priority levels accordingly. I thought about using web config pluging, but
maybe we could integrate this page to configure notifications for OVMS
mobile apps as well?
Best regards,
Marko Juhanne
Any objection to the new updated text be used as the into page in the
docs? If not I'll make a PR:
http://docs.openvehicles.com/en/latest/introduction.html
On Mon, 21 Oct 2019 at 05:00, <ovmsdev-request(a)lists.openvehicles.com> wrote:
>
> Send OvmsDev mailing list submissions to
> ovmsdev(a)lists.openvehicles.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
> or, via email, send a message with subject or body 'help' to
> ovmsdev-request(a)lists.openvehicles.com
>
> You can reach the person managing the list at
> ovmsdev-owner(a)lists.openvehicles.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OvmsDev digest..."
>
>
> Today's Topics:
>
> 1. Readme rework (Michael Balzer)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 20 Oct 2019 17:50:18 +0200
> From: Michael Balzer <dexter(a)expeedo.de>
> To: ovmsdev(a)lists.openvehicles.com
> Subject: [Ovmsdev] Readme rework
> Message-ID: <334227c9-584e-56e8-b032-fae880531e73(a)expeedo.de>
> Content-Type: text/plain; charset=utf-8
>
> Everyone,
>
> I felt it was about time to polish our readme. Please have a look:
>
> https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3
>
> If I missed something that should be there, tell me.
>
> Thanks to Glyn for the flyer image :-)
>
> Regards,
> Michael
>
> --
> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev(a)lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
>
> ------------------------------
>
> End of OvmsDev Digest, Vol 93, Issue 19
> ***************************************
--
All the best,
Glyn Hudson
+44(0)1248672607
https://openenergymonitor.orghttps://zerocarbonadventures.co.uk
I made a change to the ovms v2 server code (remember, the repository moved) and added support for client specific commands.
Previously, if an App sent a command to the car, the reply from the car is transmitted to all connected Apps. The change is to try to keep track (a queue) of outstanding commands and who sent them - then when the reply comes in we direct it to the specific App that sent the original command (and not the others). If the queue messes up, and we lose track, we revert to the old behaviour.
It seems to work well, but was non-trivial. In particular, the command functions 1 and 3 (feature and parameter lists) complicate things as they have multiple replies to a single command - so specific support had to be added for those.
It is live on the api.openvehicles.com <http://api.openvehicles.com/> server now. Hopefully there won’t be any issues, but please let me know if you see any issues running commands - send me the vehicle ID and time, and I can check.
Regards, Mark.
Hi all,
I was wondering if the OVMS scripting support already includes some kind of http -client. I would like to be able to do something like this:
function stopCharging() {
var xhttp = new XMLHttpRequest();
xhttp.onreadystatechange = function() {
if (this.readyState == 4 && this.status == 200) {
var resp = JSON.parse(xhttp.responseText);
var status = resp.response.status;
print('status: ' + status);
}
};
xhttp.open("POST", "https://<url to charge box manufacturer>/<my deviceId>/stop-charge", true);
xhttp.setRequestHeader('Authorization', '<some magic token>');
xhttp.send( '<some magic json struct>');
}
I've got a proof-of-concept javascript running on my pc, including some preparation http calls to get the right magic token and the charge-box indeed receives the command and stops charging.
But am now having trouble translating this in javascript that is accepted by the OVMS module...
I also have the beginning of a OVMS script, triggered by ticker.60, that basically does:
var charging = OvmsMetrics.Value("v.c.charging");
var bat_soc = OvmsMetrics.AsFloat("xnl.v.b.soc.instrument");
if (charging === "yes" && bat_soc >= 80) {
stopCharging(); // <-- this still fails...
// Note: OvmsVehicle.StopCharge(); is not possible on Nissan Leaf (only StartCharge is)
}
It would be really nice if I could get the OVMS module to trigger the stop charging command by itself. That would give me similar functionaliy as what this guy did using a CarLoop device (https://www.mynissanleaf.com/viewtopic.php?t=23741)
If it is not possible, then I need to revert to running a script somewhere on a server, that will periodically keep an eye on the OVMS metrics and then triggers the stop.
OKidoki,
Anko
That's good to hear, you power readings were very similar to mine. I
pessimistically rounded up when the values were fluctuating.
Where would be the best place to publish these readings in the
documentation? Prior to measuring the power readings myself I tried to
search for OVMS power consumption in the docs but could not find any
results.
How about adding a new section to readthedocs called "technical specs"?
On Wed, 23 Oct 2019 at 18:32, <ovmsdev-request(a)lists.openvehicles.com> wrote:
>
> Send OvmsDev mailing list submissions to
> ovmsdev(a)lists.openvehicles.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
> or, via email, send a message with subject or body 'help' to
> ovmsdev-request(a)lists.openvehicles.com
>
> You can reach the person managing the list at
> ovmsdev-owner(a)lists.openvehicles.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OvmsDev digest..."
>
>
> Today's Topics:
>
> 1. Re: OVMS V3 power consumption readings (Mark Webb-Johnson)
> 2. Re: Kona electric and http routing (Peter Lord)
> 3. Re: Kona electric and http routing (Michael Balzer)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 23 Oct 2019 21:31:16 +0800
> From: Mark Webb-Johnson <mark(a)webb-johnson.net>
> To: OVMS Developers <ovmsdev(a)lists.openvehicles.com>
> Subject: Re: [Ovmsdev] OVMS V3 power consumption readings
> Message-ID: <29BFF543-9FDC-4EF7-A8B8-1F8ED92FCDD8(a)webb-johnson.net>
> Content-Type: text/plain; charset="utf-8"
>
> Glyn,
>
> Powered exclusively by ext12v, @12v, I get:
>
> Wifi off/sleeping: 25mA
> Wifi only: 49mA
> Wifi + 3G: 85mA
>
> Powered exclusively by USB, @5v, I get:
>
> Wifi off/sleeping: 46mA
> Wifi only: 104mA
> Wifi + 3G: 180mA
>
> Note that in areas of low signal, the 3G power consumption can be higher. Similarly, if GPS is enabled that can have an affect as well. I?ve never seen it go over about 220mA (and even that was just for short bursts).
>
> If I power it from both USB and 12V simultaneously, I get:
>
> Wifi off/sleeping: 8mA (USB 5v) and 19mA (ext 12v)
> Deep sleep: 8mA (USB 5v) and <1mA (ext 12v)
>
> (The 8mA is mostly from the CP2102 which is powered off when not in use)
>
> Regards, Mark
>
> > On 22 Oct 2019, at 2:41 AM, Glyn Hudson <glyn.hudson(a)openenergymonitor.org> wrote:
> >
> > I've just measured the power consumption of the OVMS V3 module using a
> > bench power supply set to exactly 12.0V.
> >
> > OVMS consumed:
> >
> > 60mA = 0.72W with WiFi on (AP active) and GSM/GPS modem off
> > 100mA = 1.2W with everything switched on.
> >
> > This is less than I was expecting, I would take weeks for OVMS to
> > drain a healthy lead acid battery.
> >
> > --
> > All the best,
> >
> > Glyn Hudson
> > +44(0)1248672607
> >
> > https://openenergymonitor.org
> > https://zerocarbonadventures.co.uk
> > _______________________________________________
> > OvmsDev mailing list
> > OvmsDev(a)lists.openvehicles.com
> > http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
>
I've just measured the power consumption of the OVMS V3 module using a
bench power supply set to exactly 12.0V.
OVMS consumed:
60mA = 0.72W with WiFi on (AP active) and GSM/GPS modem off
100mA = 1.2W with everything switched on.
This is less than I was expecting, I would take weeks for OVMS to
drain a healthy lead acid battery.
--
All the best,
Glyn Hudson
+44(0)1248672607
https://openenergymonitor.orghttps://zerocarbonadventures.co.uk
