- OvmsDev - Open Vehicles

IDE setup help
by Jared Greco 03 Sep '23

03 Sep '23

Hi All, I am hoping to start work on adding the VW e-Golf vehicle, but struggling with setup. Currently I am fighting two errors with esp_task_wdt_get_trigger_tasknames() and xt_set_error_handler_callback() not declared in scope. See attached. What I did: -went through dev setup doc (macOS) -pulled master -set up Eclipse IDE to build and flash using this <https://docs.espressif.com/projects/esp-idf/en/v4.3/esp32/get-started-legac…> I get the same errors when running "make flash" from the terminal. Any ideas? Thanks! Jared

2 1

Hologram outage
by Mark Webb-Johnson 30 Aug '23

30 Aug '23

The first major outage of Hologram in the ~7 years we’ve been using them, current status is shown here: https://status.hologram.io/ Update - Our upstream partner has identified the root cause of the regression. One of the provider's network interface was unable to support the amount of traffic being released and was compromised. The solution is currently being assessed, in which they'll migrate the signaling services to a different node that is operating normally and has bandwidth to support the incremental traffic. Latest estimate for full resolution is 0700 to 0800 UTC. This estimate is based on the assumption that the applied solutions work as intended. Aug 29, 2023 - 22:59 UTC The CEO of Hologram has also penned a message to all: I founded Hologram to provide the most reliable cellular connectivity product available, and today we failed to live up to that promise. We've been impacted by a partial outage for over 24 hours, and I've heard deep frustration and anger from many customers about the impact this is having on their business. If you've been affected, I'm genuinely sorry. Here are the facts: The source of the ongoing outage has been traced to a hardware failure in an upstream mobile network operator. We've applied continuous pressure and understand that a fix was implemented earlier this morning. However, given the amount of devices affected, it will take time for your devices to reconnect. You can keep up-to-date on the latest information about the outage on our status page <http://mkto-ab470047.com/n/MTU1LUNCRy03MDIAAAGN4f28lNbpRgDXdNIUELBldxUb-w9Y…>. Our first priority is getting you back online. Immediately afterward, we need to re-earn your trust and confidence that we're taking the necessary steps to ensure this is a "never-again" event. Look for follow-ups in the coming days with details on the root cause and prevention measures. Sincerely, Ben Forgan CEO and Co-Founder hologram.io <http://mkto-ab470047.com/n/MTU1LUNCRy03MDIAAAGN4f28lF5yOsBL1usDBobXkzPvxArJ…> We’ll continue to monitor the status, but not much we can do other than wait for the upstream provider to fix their issues. Regards, Mark.

1 0

openvehicles.com outage
by Mark Webb-Johnson 19 Aug '23

19 Aug '23

There is a scheduled electricity supply 5 year maintenance, affecting openvehicles.com and api.openvehicles.com services, on 2023-08-20 between 00:30 and 09:00 UTC. During this time, OVMS services will be impacted. We will do what we can to minimise the disruption time in this maintenance window. Regards, Mark

1 0

Modem - Last Error: User Interrupt
by Chris van der Meijden 03 Aug '23

03 Aug '23

After I upgraded my modem to a SIM7600 (and replaced my SIM card) I hoped the GSM would be running well again. I'm sorry to say that I still have issues. Every few days GSM will disconnect with "Last Error: User Interrupt". When it disconnects this way it won't connect anymore. Not even when I change location. Only after a "module reset" the connection comes back for another few days. The antenna I use is the internal antenna of the car. I had no issues like this last year. Same antenna then. Am I alone with this behauviour? Any ideas? Thanx Chris cellular status MODEM Status Model: SIM7600 Network Registration: RegisteredHome Provider: congstar Signal: -77 dBm Mode: GSM;Online State: NetLoss Mux: Status up PPP: Not connected Last Error: User Interrupt GPS: Not running module reset cellular status MODEM Status Model: SIM7600 Network Registration: RegisteredHome Provider: congstar Signal: -79 dBm Mode: LTE;Online State: NetMode Mux: Status up PPP: Connected on channel: #2 GPS: Not running

4 7

Current Work in progress - where I'm at for those interested
by Michael Geddes 31 Jul '23

31 Jul '23

Hi all, I'm pushing up my current progress on a reworking of the polling loop. I'm not doing a pull request of this as it absolutely needs to be incorporated in manageable chunks, and I understand that requires time that the devs currently don't have. In broad strokes, this: * Reduces the amount of word done in the Scheduler thread, which under routeros should be kept as lite as possible. This work is done on the (beefed up) Polling thread. * Allows keeping separate OBD state for each polling bus (while maintaining a single thread). * Better compartmentalises the poller operations. * Allows once-off poller actions that don't require blocking the thread. (Which particularly if this is the Scheduler thread - the one that provides the 1s ticks- is not recommended) * Effectively Extends the number of poll 'states' available without changing the base structure. https://github.com/frogonwheels/Open-Vehicle-Monitoring-System-3/tree/polle… I'm still very much interested in feedback and in making this available. In a practical sense, this is what I run on my OVMS and in particular for the OBD2ECU it is working very nicely! //.ichael Geddes

1 0

New module for BYD Atto 3
by Alan Harper 31 Jul '23

31 Jul '23

Hi All, Just sharing that I’m currently working on a vehicle module for the BYD Atto 3. Have basics like SOC, moment in time battery current usage, odometer and speed, but still testing out that I have captured the states correctly when charging with an EVSE and haven’t yet tested at all with DC fast charging. Any particular modules I should be using as a guide for the best way of developing a module?

2 1

Strange issues with Car GPS accuracy.
by Michael Geddes 14 Jul '23

14 Jul '23

Hi all, I'm having a bunch of weird things going on which seem correlated to having the OVMS running. I'm not convinced of causation yet. My car's Nav system is drifting out majorly (like by >100m) and then seems to stay out. This causes major distractions as the nav system keeps giving me warnings about going down one-way roads and it makes the navigation 'interesting' to use. I also noticed that Android Auto location was frozen in one place, so I assumed this was coming from the car - or meant to be anyway. I reduced the polling rate (new work I'm doing) slightly and this freezing no longer happens. (To 3 speed queries per second). But the drifting out on the Navigation still happens... but then not on AA!? Very very weird. If I unplug the OVMS from the OBD port (as I'm driving) it seems to (but not immediately - after a minute or so) correct itself. It's hard to confirm this is directly resulting .. but it seems to be? I turned off my ECU2OBD which should mean that it is resorting to 1 per second POLL with a low throttle value. I'll run with some logs to make sure this is what is happening.. but it still seems that this hasn't stopped this issue from happening. I've tried turning the GSM power off. No result. Another note: I seem to have stopped getting anything near regular updates from the OVMS GPS. Every now and again it gets a successful change come through. Still working on diagnosing that.. maybe it's related? Any thoughts / help would be useful. //.ichael

4 9

Re: [Ovmsdev] simcom 7600 board not responding
by Derek Caudwell 05 Jul '23

05 Jul '23

I had set the driver to SIM7600 with the config set modem driver to speed up connecting. It could be handy to set this from the cellular config page.

1 0

Netmanager priority issue solved
by Michael Balzer 05 Jul '23

05 Jul '23

TL;DR: you need to pull my latest esp-idf changes. I've finally found & solved the strange priority changes for our netmanager task (i.e. being raised suddenly from origin 5 to 18/22): the bug was in the esp-idf posix threads mutex implementation. I had suspected the mutex priority inheritance for a while, so added a way to retrieve the internal mutex hold count for our task list. Using this I noticed the hold count would always & only raise by 2 whenever any kind of mongoose connection was closed. That lead me to checking the thread concurrency protection for mongoose mbufs, because every mongoose connection has two mbufs associated (rx & tx), each having a posix mutex. The bug was: posix mutexes were deleted after locking (taking) them. FreeRTOS mutexes must not be deleted while being taken, that breaks the priority inheritance (more precisely the disinheritance), with the visible effect being the mutex hold count not returning to zero. As a side effect, this may also solve the strange event task starvations (hope so…). I was investigating this as I suspected some busy loop in the netmanager context. With the netman running at prio 22, that would effectively block almost all other processing including the timer service. I've found & fixed one potential busy loop trigger in the netman that would have been caused by the netman task still running while all interfaces had been lost -- not sure if that could happen, but it would explain the effects. So please watch your crash debug info & report if the issue still turns up. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

5 19

Re: [Ovmsdev] simcom 7600 board not responding
by Derek Caudwell 05 Jul '23

05 Jul '23

Thanks Mark, I am on the "edge" firmware and have the verbose logging already enabled. The tx is being logged ok but no rx back. Another anomaly is it will sometimes go from PoweringOn to PoweredOn with no apparent response to the AT command being sent, then times out back to PoweringOn. So there may be a hardware failure, voltage level shifter perhaps? I will try putting an oscilloscope on both ends of transmission next. In testing I simply modified the simcom 7600 driver code to override the default modem driver so as not to effect the 5360 pulse logic. The spec sheet also mentioned it takes the UART around 11s to respond after power up. Using the spec sheet timing with a delay after turning on appears very reliable on mine in powering up and down the module. Whereas the 2s and 6s pulse turned it on and the 4s pulse turned it off going by the led status.

2 1