- OvmsDev - Open Vehicles

Smart ED
by Mark Webb-Johnson 10 Feb '19

10 Feb '19

Can someone working on Smart ED help to update this forum post with current status: https://www.openvehicles.com/node/2097 Thanks, Mark

1 0

User guide update for Nissan Leaf
by Anko Hanse 06 Feb '19

06 Feb '19

With the inclusion of fix #170, "Fix for 0% SOH on 30KWh models with Nissan BMS update" in the new 3.2.001 firmware, the user guide needs updating. I do not seem to have the right to do that, so can someone do it for me? It concerns the "OVMS v3 Advanced User Guide", Chapter "NL Nissan Leaf", section "Configuration": - The former [2016] section title should be updated to [2016-2017] - The section about the 30 kwh models should be taken out of the [2016-2017] section and into its own section (there are 2015 30 kwh models, I own one...) - The new section about the 30kwh models needs an extra command to also update the "newCarAh" setting to 79 (from 66) Full new text: [2011-2015 models] To enable remote commands, either Unplug any CARWINGS, Nissan Connection or TCU units or on Generation 1 Cars, wire the RC3 to TCU pin 11 (see MyNissanLeaf post) [2016-2017 models] Set the model year as follows config set xnl modelyear 2016 or config set xnl modelyear 2017 [30 kwh models] For models with a 30 kwh battery pack, set the capacity manually as follows config set xnl maxGids 356 config set xnl newCarAh 79

4 5

Mitsubishi i-MiEV and clones
by Tamás Kovács 05 Feb '19

05 Feb '19

I want to add support for 80 cell cars , the i-Miev has 88 cell all model year, but the clones are 80 cell from 2013 model year. What's the good implement for this. 1) Create a config, and user can set it 2) Automatically get from VIN number and set it. And a nother question, where set the BmsSetCellArrangementVoltage() and BmsSetCellArrangementTemperature(); Now set in OvmsVehicleMitsubishi::OvmsVehicleMitsubishi() I now created the first for testing. I added BmsSetCellArrangementVoltage(80,8) BmsSetCellArrangementTemperature(60, 6) in: void OvmsVehicleMitsubishi::ConfigChanged(OvmsConfigParam* param) if checkbox checked, but in dasboard show all the 88 cell data if set to 80 cell. This is because the vestor has 88 values, or because 80/88 cell cars delivers 88 cell values? I don't understand why send 80 cell cars 88 cell data (8 fake?) If i add "MyConfig.GetParamValueBool("vehicle", "bms.alerts.enabled", false);" to OvmsVehicleMitsubishi::OvmsVehicleMitsubishi() i can disable bms alerts for default?

2 1

Leaf SOH
by Dean MacGregor 05 Feb '19

05 Feb '19

The SOH did come back the next time I started the car. Thanks. On Tue, Feb 5, 2019 at 12:23 PM, ovmsdev-request(a)lists.openvehicles.com<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. LEAF SOH (was: OvmsDev Digest, Vol 85, Issue 5) (Robin O'Leary) 2. Re: LEAF SOH (Robin O'Leary) 3. Re: Collecting information on the Fiat 500e (Guenther Huck) 4. Re: Collecting information on the Fiat 500e (Guenther Huck) ---------------------------------------------------------------------- Message: 1 Date: Tue, 5 Feb 2019 10:29:04 +0000 From: Robin O'Leary <ovmsdev(a)caederus.org> To: OVMS Developers <ovmsdev(a)lists.openvehicles.com> Subject: [Ovmsdev] LEAF SOH (was: OvmsDev Digest, Vol 85, Issue 5) Message-ID: <20190205102904.GB19577(a)mail.ro.nu> Content-Type: text/plain; charset=iso-8859-1 On Tue, Feb 05, 2019 at 02:46:40AM +0000, Dean MacGregor wrote: > With the new firmware version the SOH reading doesn't work but it used > to.? That's in both the 'Vehicle Info' and 'metrics list' command. > I have a 2015 Nissan Leaf.? Is this with the car switched off? Can you check with the the car ready to drive? Most other values we display are passively read whenever the can bus is active, but to get more detailed values from the battery (v.b.soh, xnl.v.b.hx, v.b.cac), we need to send an active poll request. We don't want to do this when the car is asleep, since it causes modules to wake up and consume power. We did previously get v.b.soh from a passive message 0x5b3, which is a 7-bit value (0--100%) available whenever the car is awake. The active poll to 0x7bb.6101 gives better resolution (~11 bits). We had a similar situation with the SOC, where I think we have a better solution. We now report both low- and high-resolution values as separate LEAF-specific metrics: the simple percentage in xnl.v.b.soc.instrument and the high-resolution value scaled as a proportion of the "new car" value as xnl.v.b.soc.newcar. By default, the standard metric v.b.soc reports the value from xnl.v.b.soc.instrument; there is a config option if you want it to report xnl.v.b.soc.newcar instead. I think it would be better if we followed the same pattern with SOH. ------------------------------ Message: 2 Date: Tue, 5 Feb 2019 13:16:47 +0000 From: Robin O'Leary <ovmsdev(a)caederus.org> To: OVMS Developers <ovmsdev(a)lists.openvehicles.com> Subject: Re: [Ovmsdev] LEAF SOH Message-ID: <20190205131647.GD19577(a)mail.ro.nu> Content-Type: text/plain; charset=us-ascii On Tue, Feb 05, 2019 at 10:29:04AM +0000, Robin O'Leary wrote: > ... > We did previously get v.b.soh from a passive message 0x5b3, which is a > 7-bit value (0--100%) available whenever the car is awake. The active > poll to 0x7bb.6101 gives better resolution (~11 bits). > > We had a similar situation with the SOC, where I think we have a better > solution. We now report both low- and high-resolution values as separate > LEAF-specific metrics: the simple percentage in xnl.v.b.soc.instrument > and the high-resolution value scaled as a proportion of the "new car" > value as xnl.v.b.soc.newcar. By default, the standard metric v.b.soc > reports the value from xnl.v.b.soc.instrument; there is a config option > if you want it to report xnl.v.b.soc.newcar instead. > > I think it would be better if we followed the same pattern with SOH. This is implemented in: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/200 Report SOH from passive 0x5b3 in private metric "xnl.v.b.soh.instrument". Report SOH from active 0x7bb.6101 in private metric "xnl.v.b.soh.newcar". Standard metric "v.b.soh" copies from "xnl.v.b.soh.instrument" by default, or from "xnl.v.b.soh.newcar" if config option "xnl.soh.newcar" is set to "true". ------------------------------ Message: 3 Date: Tue, 5 Feb 2019 18:06:40 +0100 From: "Guenther Huck" <privat(a)guentherhuck.at> To: "OVMS Developers" <ovmsdev(a)lists.openvehicles.com> Subject: Re: [Ovmsdev] Collecting information on the Fiat 500e Message-ID: <3DF31B4F6313452380B2A0C536D4CC8B@GuentherPCHP> Content-Type: text/plain; charset="utf-8" Hello Mark I have a Fiat 500e and asked if there is anybody who is firm with the CAN Id?s. In the meantime I have some CAN informations for Fiat 500e and can give to you or somebody who is familiar to programm the OVMS for this car. I don?t have enough experiance to programm this. Sorry! What informations to you need to insert this car to your project ? Guenther From: Mark Webb-Johnson Sent: Saturday, June 30, 2018 3:52 PM To: OVMS Developers Subject: Re: [Ovmsdev] Collecting information on the Fiat 500e I?ve had a user in Australia contact me about this recently. It seems there is some activity on Fiat forums, with people discussing this? I am told the factory app is non-renewable after 3 years, and many cars are being exported out of USA. This user is a Fiat and Alfa technician, so has quite some knowledge of the cars. Regards, Mark. On 30 Jun 2018, at 6:21 AM, Jason Perkins <perkins.jason(a)gmail.com> wrote: I had trouble with the Arduinos I'd gotten, they seemed to garble the 2nd CAN whenever the baud rate was set correctly. I only got a single day to play with it before the telematics was cut off on our roomates 2014 :( Another local friend just got a 2015, don't know if his telematics work or not though. -J On Fri, Jun 29, 2018 at 3:36 PM, Guenther Huck <privat(a)guentherhuck.at> wrote: Is here anybody working on Fiat 500e can bus sniffing? (Maybe perkins.jason) I have also some sniffing done and send you file for arduino. This works for SOC. Maybe we can share information? greetings Guenther _______________________________________________ OvmsDev mailing list OvmsDev(a)lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev -- Jason Perkins 313 355 0085 _______________________________________________ OvmsDev mailing list OvmsDev(a)lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev -------------------------------------------------------------------------------- _______________________________________________ OvmsDev mailing list OvmsDev(a)lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev

1 0

Re: [Ovmsdev] OvmsDev Digest, Vol 85, Issue 5
by Dean MacGregor 05 Feb '19

05 Feb '19

With the new firmware version the SOH reading doesn't work but it used to. That's in both the 'Vehicle Info' and 'metrics list' command. I have a 2015 Nissan Leaf. On Mon, Feb 4, 2019 at 5:29 AM, ovmsdev-request(a)lists.openvehicles.com<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 v3.2.001 Over-the-Air firmware update (Mark Webb-Johnson) 2. Re: OVMS v3 v3.2.001 Over-the-Air firmware update (ovms) ---------------------------------------------------------------------- Message: 1 Date: Mon, 4 Feb 2019 18:17:35 +0800 From: Mark Webb-Johnson <mark(a)webb-johnson.net> To: OVMS Developers <ovmsdev(a)lists.openvehicles.com> Subject: Re: [Ovmsdev] OVMS v3 v3.2.001 Over-the-Air firmware update Message-ID: <5EB9E54C-7BBA-4424-8890-17806B2E7D03(a)webb-johnson.net> Content-Type: text/plain; charset="utf-8" Can you give details on what you are compiling custom, and where you are getting the code from? I checked the current driver and there doesn?t seem to be any door lock code. Also checked github pull requests, but nothing related to that. Of it this is your extension, can you email it in? Regards, Mark > On 4 Feb 2019, at 4:39 PM, ovms <ovms(a)topphemmelig.no> wrote: > > Any chance someone can include door lock/unlock for Leaf? Then I don?t have to compile the code every time to get the function, and can use the auto-update function. > I have no idea how to commit anything to git. > > Kind regards, > Stein Arne Sordal > > > > On 2019-02-04 06:11, Mark Webb-Johnson <mark(a)webb-johnson.net> wrote: > I?ve just moved this 3.2.001 to ?main? release level. > > If anybody wants to include something, please commit. Hoping to build 3.2.002 for EAP later this week. > > Regards, Mark. > > On 19 Jan 2019, at 5:00 PM, Mark Webb-Johnson <mark(a)webb-johnson.net> wrote: > > > https://www.openvehicles.com/node/2123 > > Today, we are pleased to release v3.2.0-1 to Early Access Program (EAP) participants. This is the first public v3.2 version, and introduces an entirely new scripting framework based on an embedded javascript engine. Now, custom javascript modules and functions can be written to respond to system events. In addition, a host of other UI changes enhancements have been made. > A summary of the major changes is here: > 2019-01-19 MWJ 3.2.001 OTA release > - v3.2 first public release > - New JavaScript modular framework allowing for dynamic scripting and object model > - New vehicle: Smart ED (adaption by Martin Graml ) > - Mitsubishi i-MiEV re-write for OVMS v3 > - Web UI: text / script editor > - Web UI: user plugin support (pages & hooks) > - Web UI: night mode by URI parameter, e.g. "?/#/dashboard?nm=1" > - Web UI: dashboard accessible w/o login > - Web UI: added config backup & restore tool > - Web UI: file selector added for firmware flashing from SD > - Web UI: text notifications (info/error/alert) displayed as dialogs > - Twizy web UI: drivemode buttons secured & added to dashboard > - Twizy web UI: added file dialog for virtual dyno recording > - Twizy: SEVCON monitoring & recording > New commands: > xrt mon start [] > xrt mon stop > xrt mon reset > New metrics: > xrt.i.* = operational inverter data > xrt.s.* = power & torque by speed (virtual dyno) > - Twizy: experimental powermap calculation including region 3 / breakdown torque > New config: > xrt [motor_trq_breakdown] = 0 Breakdown torque in Nm, e.g. 210.375 > xrt [motor_rpm_rated] = 0 Rated speed in rpm, e.g. 2100 > See docs/Renault-Twizy/Twizy-Powermap-Calculator-Tbrk.ods for details. > - Add inactivity watchdog timers to CAN buses > - NissanLeaf: Fix for 0% SOH on 30KWh models with Nissan BMS update > - Introduction of support for DBC CAN bus configuration files > For full detail on all changes, check the GitHub revision history. > The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. > This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. You can choose the release level by setting 'config ota tag edge|eap|main', as one of: > > > edge: Bleeding edge developer nightly-builds > eap: Early Access Program (full releases, but with little public testing) > main: Publicly tested full releases (the most stable) > > > We expect to release the 3.2.001 firmware to 'main' (all users) after EAP testing (most likely within a week or so). > Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project. > Open Vehicles > _______________________________________________ > OvmsDev mailing list > OvmsDev(a)lists.openvehicles.com > http://lists.openvehicles.com/mailman/listinfo/ovmsdev > _______________________________________________ OvmsDev mailing list OvmsDev(a)lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev > _______________________________________________ > OvmsDev mailing list > OvmsDev(a)lists.openvehicles.com > http://lists.openvehicles.com/mailman/listinfo/ovmsdev

2 2

OVMS v3 v3.2.001 Over-the-Air firmware update
by Mark Webb-Johnson 04 Feb '19

04 Feb '19

https://www.openvehicles.com/node/2123 <https://www.openvehicles.com/node/2123> Today, we are pleased to release v3.2.0-1 to Early Access Program (EAP) participants. This is the first public v3.2 version, and introduces an entirely new scripting framework based on an embedded javascript engine. Now, custom javascript modules and functions can be written to respond to system events. In addition, a host of other UI changes enhancements have been made. A summary of the major changes is here: 2019-01-19 MWJ 3.2.001 OTA release - v3.2 first public release - New JavaScript modular framework allowing for dynamic scripting and object model - New vehicle: Smart ED (adaption by Martin Graml ) - Mitsubishi i-MiEV re-write for OVMS v3 - Web UI: text / script editor - Web UI: user plugin support (pages & hooks) - Web UI: night mode by URI parameter, e.g. "…/#/dashboard?nm=1" - Web UI: dashboard accessible w/o login - Web UI: added config backup & restore tool - Web UI: file selector added for firmware flashing from SD - Web UI: text notifications (info/error/alert) displayed as dialogs - Twizy web UI: drivemode buttons secured & added to dashboard - Twizy web UI: added file dialog for virtual dyno recording - Twizy: SEVCON monitoring & recording New commands: xrt mon start [] xrt mon stop xrt mon reset New metrics: xrt.i.* = operational inverter data xrt.s.* = power & torque by speed (virtual dyno) - Twizy: experimental powermap calculation including region 3 / breakdown torque New config: xrt [motor_trq_breakdown] = 0 Breakdown torque in Nm, e.g. 210.375 xrt [motor_rpm_rated] = 0 Rated speed in rpm, e.g. 2100 See docs/Renault-Twizy/Twizy-Powermap-Calculator-Tbrk.ods for details. - Add inactivity watchdog timers to CAN buses - NissanLeaf: Fix for 0% SOH on 30KWh models with Nissan BMS update - Introduction of support for DBC CAN bus configuration files For full detail on all changes, check the GitHub revision history. The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. You can choose the release level by setting 'config ota tag edge|eap|main', as one of: edge: Bleeding edge developer nightly-builds eap: Early Access Program (full releases, but with little public testing) main: Publicly tested full releases (the most stable) We expect to release the 3.2.001 firmware to 'main' (all users) after EAP testing (most likely within a week or so). Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project. Open Vehicles

3 7

HUD
by Geir Øyvind Vælidalo 02 Feb '19

02 Feb '19

I’m thinking about maybe buying a HUD to connect to OVMS. Do you have any recommendations? Greg, which one do you have? Best regards, Geir

2 5

std::string data corruption (issue #189)
by Michael Balzer 02 Feb '19

02 Feb '19

Everyone please have a look at… https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/189… Please try to reproduce the bug on your modules. I'm open for explanations. I thought this might be some copy-on-write bug with std::string, but the gcc 5.x libstdc++ does no longer use that implementation (wouldn't be C++11 compliant as well). I also tried moving all strings to temporary buffers, but modes 5 & 6 eliminated this explanation as well. My remaining theories: * A task writing out of bounds (but only 0-bytes?) * A hardware issue only affecting some modules A hardware issue only affecting some percentage of ESP32 could explain this as well as the strange heap corruptions that seem to affect some modules especially often. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

2 15

Re: [Ovmsdev] OvmsDev Digest, Vol 83, Issue 5
by Olivier 27 Jan '19

27 Jan '19

Hi Mark, Before the update code is working to but with some error, I will fix my dbc file to add signal for all message. I have two question : 1. do you know how to config the dbc file to "compile" data from 2 Btye not contigu ? Example : ID 00FDF040 8 0x85 0x85 0x81 0x6A 0x7A 0xD9 0x4C 0x2E // ID message contain 5 Cells Voltage Cell 1 : #Byte 0 (0x85) | #LowByte 5 (0x9) => 0x859 => 2137 * 0,0015 = 3,2055Volts Cell 2 : #Byte 1 (0x85) | #HighByte 5 (0xD) => 0x85D Cell 3 : #Byte 2 (0x81) | #LowByte 6 (0xC) => 0x81C Cell 4 : #Byte 3 (0x6A) | #HighByte 7 (0x4) => 0x6A4 Cell 5 : #Byte 4 (0x7A) | #LowByte 8 (0xE) => 0x7AE the last Byte is the ID of BMS Board (0x2?) 2. The next step do after dbc load, How I can use information the value to map or link with Standard metric ? Thank you Olivier Le ven. 7 déc. 2018 à 05:00, <ovmsdev-request(a)lists.openvehicles.com> a écrit : > 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: OvmsDev Digest, Vol 83, Issue 3 (Mark Webb-Johnson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 7 Dec 2018 09:19:41 +0800 > From: Mark Webb-Johnson <mark(a)webb-johnson.net> > To: OVMS Developers <ovmsdev(a)lists.openvehicles.com> > Subject: Re: [Ovmsdev] OvmsDev Digest, Vol 83, Issue 3 > Message-ID: <4F23B219-BDC5-4DA2-BAED-CC8380ABC720(a)webb-johnson.net> > Content-Type: text/plain; charset="utf-8" > > Olivier, > > Glad to see it is working again. I re-worked the dbc parsing code > yesterday to allow sections to be in any order in the DBC (although the > formal specification defines a specific order). That fixed your problem > with loading the DBC? > > I tried your provided Vectrix_VX1.dbc with the day before yesterday?s > 1bce372b20d4a79fb633faa6b96574604d95272f code, and get a segmentation fault > on parsing it. With today?s master head, no problems and the file seems to > load ok. The problem is the line 'BO_ 2164185677 FrontSensorRevision: 8 > FRONTSensor? - a message (BO_) without any signals (SG_). The newer code > doesn?t care, but the older code couldn?t handle it. > > Regarding opendbc, yes I am aware of that. A very good resource. But, most > (if not all) of those DBCs there have illegal structure. I think they are > only used for human (not machine) reference. Things like section terms > mis-spelled, missing semi-colons, values referring to signals or messages > that don?t exist, etc. It is a good resource for testing broken DBC files > ;-) > > Regards, Mark. > > > On 7 Dec 2018, at 4:37 AM, Olivier <ogrums(a)gmail.com> wrote: > > > > Hello Mark, > > > > It's strange, I have re-clone again to be sure about IDF, > > > > $ git describe --tags --dirty > > v3.1-dev-2835-g151269458 > > > > And now both is working, SD read and load dbc > > > > I have add my dbc file, and if you want to test the is this git : > https://github.com/commaai/opendbc <https://github.com/commaai/opendbc> > > > > regards, > > Olivier > > > > Le jeu. 6 d?c. 2018 ? 05:16, <ovmsdev-request(a)lists.openvehicles.com > <mailto:ovmsdev-request@lists.openvehicles.com>> a ?crit : > > Send OvmsDev mailing list submissions to > > ovmsdev(a)lists.openvehicles.com <mailto: > ovmsdev(a)lists.openvehicles.com> > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.openvehicles.com/mailman/listinfo/ovmsdev < > 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 <mailto: > ovmsdev-request(a)lists.openvehicles.com> > > > > You can reach the person managing the list at > > ovmsdev-owner(a)lists.openvehicles.com <mailto: > 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: Issue to store en SD Card after upgrade to idf 3.2-Dev > > (Pull Request 2# from M4GNV5/master) (Mark Webb-Johnson) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Thu, 6 Dec 2018 08:59:57 +0800 > > From: Mark Webb-Johnson <mark(a)webb-johnson.net <mailto: > mark(a)webb-johnson.net>> > > To: OVMS Developers <ovmsdev(a)lists.openvehicles.com <mailto: > ovmsdev(a)lists.openvehicles.com>> > > Subject: Re: [Ovmsdev] Issue to store en SD Card after upgrade to idf > > 3.2-Dev (Pull Request 2# from M4GNV5/master) > > Message-ID: <5B58BB15-BEB4-4B9E-AAFC-E98DFA176748(a)webb-johnson.net > <mailto:5B58BB15-BEB4-4B9E-AAFC-E98DFA176748@webb-johnson.net>> > > Content-Type: text/plain; charset="utf-8" > > > > And related to this, if anyone else has any DBC files, please send them > to me so that I can test them against our DBC support library (to test for > robustness and completeness). > > > > Regards, Mark > > > > > On 6 Dec 2018, at 7:54 AM, Mark Webb-Johnson <mark(a)webb-johnson.net > <mailto:mark@webb-johnson.net>> wrote: > > > > > > Olivier, > > > > > > I think this is two different issues. > > > > > > SD card issue > > > > > > Are there any system-level errors shown in the logs when you try this? > Please try on local console to see what is shown there. > > > > > > Are you powered from USB or vehicle power? > > > > > > Can you show the output of ?config list sdcard? and ?sd status?? > > > > > > DBC load issue > > > > > > Can you send me the Vectrix.dbc file you are using, please. Most > likely something in the structure of this file is causing the crash. It > seems that one of the messages (BO_) cannot be parsed correctly. > > > > > > What version of IDF are you using now? Just master head, right? > > > > > > Regards, Mark. > > > > > >> On 6 Dec 2018, at 4:29 AM, Olivier <ogrums(a)gmail.com <mailto: > ogrums(a)gmail.com> <mailto:ogrums@gmail.com <mailto:ogrums@gmail.com>>> > wrote: > > >> > > >> Hello, > > >> > > >> I have some issue with SD Card on OVMS 3.1 I don't know how to fix > the "bug" > > >> > > >> I can't write or read file on SD Card, but I can make directory : > > >> > > >> OVMS# vfs ls /sd > > >> [DIR] 05-Nov-2018 20:46 logs/ > > >> 13.5k 23-Nov-2018 19:45 Vectrix_bak.dbc > > >> 14.0k 11-Nov-2018 22:04 Vectrix.dbc > > >> 13 01-Jan-1980 00:00 FOO.TXT > > >> 13.5k 23-Nov-2018 19:45 vx1.dbc > > >> > > >> OVMS# vfs mkdir /sd/testdir > > >> VFS directory created > > >> > > >> OVMS# vfs ls /sd > > >> [DIR] 05-Nov-2018 20:46 logs/ > > >> 13.5k 23-Nov-2018 19:45 Vectrix_bak.dbc > > >> 14.0k 11-Nov-2018 22:04 Vectrix.dbc > > >> [DIR] 05-Dec-2018 21:14 testdir/ > > >> 13 01-Jan-1980 00:00 FOO.TXT > > >> 13.5k 23-Nov-2018 19:45 vx1.dbc > > >> > > >> OVMS# config backup /sd/cfg.zip > > >> Creating config backup '/sd/cfg.zip'... > > >> Error: zip failed: No such file or directory > > >> > > >> OVMS# vfs rmdir /sd/testdir > > >> VFS directory removed > > >> > > >> And If I try do load dbc file it's crash > > >> > > >> OVMS# dbc load test /sd/vx1.dbc > > >> > > >> Guru Meditation Error: Core 1 panic'ed (StoreProhibited). Exception > was unhandled. > > >> Core 1 register dump: > > >> PC : 0x40271023 PS : 0x00060730 A0 : 0x800e38f1 A1 > : 0x3ffd4540 > > >> 0x40271023: dbcMessage::SetID(unsigned int) at > ?????/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/dbc/src/dbc.cpp:935 > > >> > > >> A2 : 0x00000000 A3 : 0x80feda4d A4 : 0x3ffe5360 A5 > : 0x3ffe5363 > > >> A6 : 0x00000000 A7 : 0x00000000 A8 : 0x00000020 A9 > : 0x3f4055b0 > > >> A10 : 0x00000001 A11 : 0x3f4061ce A12 : 0x3f81ec50 > A13 : 0x00000000 > > >> A14 : 0x3ffd4524 A15 : 0x00000000 SAR : 0x00000008 > EXCCAUSE: 0x0000001d > > >> EXCVADDR: 0x0000001c LBEG : 0x4009bd69 LEND : 0x4009bd9d > LCOUNT : 0xffffffff > > >> > > >> 0x4009bd69: memcpy at > /home/jeroen/esp8266/esp32/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/machine/xtensa/../../../../.././newlib/libc/machine/xtensa/memcpy.S:291 > > >> 0x4009bd9d: memcpy at > /home/jeroen/esp8266/esp32/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/machine/xtensa/../../../../.././newlib/libc/machine/xtensa/memcpy.S:324 > > >> > > >> Backtrace: 0x40271023:0x3ffd4540 0x400e38ee:0x3ffd4560 > 0x400dfeba:0x3ffd4ea0 0x400dea49:0x3ffd4ee0 0x400dec48:0x3ffd4f80 > 0x400f118a:0x3ffd4fa0 0x400f129b:0x3ffd4fd0 0x400f129b:0x3ffd5000 0x400f12 > > >> d1:0x3ffd5030 0x400ecae8:0x3ffd5050 0x4010601d:0x3ffd5070 > 0x4010608e:0x3ffd50d0 0x400ecb1f:0x3ffd5110 0x40271193:0x3ffd5130 > 0x401010a9:0x3ffd5150 0x400fa5cd:0x3ffd5180 0x400fa7e1:0x3ffd51b0 0x401 > > >> 00f35:0x3ffd51d0 0x40100f44:0x3ffd51f0 0x400f2489:0x3ffd5210 > > >> > > >> 0x40271023: dbcMessage::SetID(unsigned int) at > ?????/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/dbc/src/dbc.cpp:935 > > >> 0x400e38ee: yyparse(void*) at > ?????/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/dbc/src/dbc_parser.y:306 > > >> 0x400dfeba: dbcfile::LoadFile(char const*, __sFILE*) at > ?????/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/dbc/src/dbc.cpp:935 > > >> 0x400dea49: dbc::LoadFile(char const*, char const*) at > ?????/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/dbc/src/dbc_app.cpp:198 > > >> 0x400dec48: dbc_load(int, OvmsWriter*, OvmsCommand*, int, char const* > const*) at > ?????/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/dbc/src/dbc_app.cpp:62 > > >> 0x400f118a: OvmsCommand::Execute(int, OvmsWriter*, int, char const* > const*) at > ?????/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/ovms_command.cpp:73 > > >> 0x400f129b: OvmsCommand::Execute(int, OvmsWriter*, int, char const* > const*) at > ?????/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/ovms_command.cpp:73 > > >> 0x400f129b: OvmsCommand::Execute(int, OvmsWriter*, int, char const* > const*) at > ?????/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/ovms_command.cpp:73 > > >> 0x400f12d1: OvmsCommandApp::Execute(int, OvmsWriter*, int, char > const* const*) at > ?????/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/ovms_command.cpp:73 > > >> > > >> I Have try my SD Card on a PC is working, I have try example code > "sd_card_example_main.c" from SDK "esp-idf\examples\storage\sd_card\main", > It's working to, no crash. > > >> My guest, is the hardware is OK, esp-idf is OK, but they is something > in OVMS main code make this bug. > > >> > > >> I have delete both esp-idf, and OVMS folder and clone again, compiled > again, but it's the same issue. > > >> > > >> Thank you for your help. > > >> Olivier > > >> _______________________________________________ > > >> OvmsDev mailing list > > >> OvmsDev(a)lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> > <mailto:OvmsDev@lists.openvehicles.com <mailto: > OvmsDev(a)lists.openvehicles.com>> > > >> http://lists.openvehicles.com/mailman/listinfo/ovmsdev < > http://lists.openvehicles.com/mailman/listinfo/ovmsdev> > > > > > > _______________________________________________ > > > OvmsDev mailing list > > > OvmsDev(a)lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> > > > http://lists.openvehicles.com/mailman/listinfo/ovmsdev < > http://lists.openvehicles.com/mailman/listinfo/ovmsdev> > > > >

2 3

How to build for HW3.0
by Geir Øyvind Vælidalo 27 Jan '19

27 Jan '19

Hi guys! I just got hold of a Hyundai Kona and I’ll have it for a few days only. I’ve created a vehicle for Kona / e-Niro and I need to use the developer card with the version 3.0 hardware as the 3.1 is used in my Soul. Switching between both HW3.1 and HW3.0 seems cumbersome. Are there any easy ways to switch between them when building? We’ll get out new e-Niro in a few weeks, so it would be nice to build for both hardware versions without to much hassle. Best regards, Geir

3 3