- OvmsDev - Open Vehicles

Issue with PubSub Example Script
by solterra＠kezarnet.com 11 Sep '24

11 Sep '24

I'm currently working on a script that utilizes PubSub, but I'm running into an issue where the background function doesn't seem to display any output in the shell. I'm following the example from the website: |var myTicker = function(msg, data) { print("Event: " + msg + "\n"); }; PubSub.subscribe("ticker.10", myTicker); | For some reason, I can't get the |myTicker| function to output anything when triggered. It seems like the print statements aren't being executed as expected. Has anyone encountered this before, or does anyone have suggestions on what might be causing this issue? Thanks in advance!

2 2

New polling framework example
by solterra＠kezarnet.com 08 Sep '24

08 Sep '24

I'm working on the Toyota eTNGA vehicle integration and had a vehicle module nearly ready to merge last year. Unfortunately, my car broke down, and I've only recently gotten a new one. It seems that the polling framework has changed quite a bit since then. Could someone point me toward a good example of the new framework so I can start converting my module? Thanks in advance for your help!

2 1

Fwd: [Action Advised] Test the new Camera control on your maps before the default changes in version 3.60
by Mark Webb-Johnson 22 Aug '24

22 Aug '24

> Begin forwarded message: > > From: Google Maps Platform <google-maps-platform-noreply(a)google.com> > Subject: [Action Advised] Test the new Camera control on your maps before the default changes in version 3.60 > > > > MY CONSOLE <https://notifications.google.com/g/p/ANiao5qSJr9WisFK9IPEfHHsgx5PPGOu-NheAy…> > Hello Google Maps Customer, > > We are changing the Google Maps JavaScript API controls to reduce the space they occupy on maps by default and to improve the accessibility of panning the map. > > We’re reaching out to you because we have observed one or more of the following criteria: > > Your end-users use the Zoom buttons significantly more than the average. > One or more of your maps explicitly disables the Zoom control. > One or more of your maps have customized controls. > We have provided additional information below to guide you through this change. > > What you need to know > > Map controls <https://notifications.google.com/g/p/ANiao5rIzaVVR5OdKhLWoOCo24HOSzaLPZicfR…> are visual elements that allow user interaction with the map, including zooming the map, enabling Street View, and changing the Map Type. > > Version 3.58 adds a new Camera control <https://notifications.google.com/g/p/ANiao5qsyBbh2CYZUmipt7KzVxkZMVFbyTgECd…> in the Google Maps JavaScript API to make panning the map accessible with a single gesture. This feature will be available in the upcoming week. This new Camera control will feature buttons for panning the map and for zooming the map in and out, effectively being a single control to guide the map’s viewport. > > The upcoming changes are listed in the table below. > > Date Available in Channel Changes Implemented > In the upcoming week In the Beta channel The updated default map controls will replace the Zoom control with the Camera control. > In the upcoming week > > In the weekly channel > > Version 3.58 and version 3.59 will offer the Camera control without changing the default map controls. > > In November 2024 > > In the quarterly channel > > In February 2025 > > In the weekly channel > > Version 3.60 will contain the updated changes to the default map controls. > > In May 2025 > > In the quarterly channel > > What you need to do > > Before the default controls are updated > > Test the new Camera control on your maps before the default changes in version 3.60 reach the weekly channel in February 2025 or the quarterly channel in May 2025. > > To test the Camera control: > > If you use default controls in your map options, specify the Beta channel <https://notifications.google.com/g/p/ANiao5rRp4NzBcGc89tsCfGA6CK4KvYIGOlCyM…> to see how the default controls will change. > If you do not use the default controls, or prefer not to change to the Beta channel in your loader, enable the Camera control, and optionally disable the Zoom control, in google.maps.MapOptions <https://notifications.google.com/g/p/ANiao5qsyBbh2CYZUmipt7KzVxkZMVFbyTgECd…>. > After the default controls are updated > > Consider taking one of the following actions after the default controls are updated to include the Camera control instead of the Zoom control in version 3.60 in February 2025 for the weekly channel and May 2025 for the quarterly channel. > > If your code explicitly enables the Zoom control (zoomControl: true), both the Zoom control and the Camera control will be displayed. Consider choosing one to save on map space. > If your code explicitly disables the Zoom control (zoomControl: false), you may also want to disable the Camera control. > If your code explicitly enables the Zoom control (zoomControl: true) while keeping the default controls disabled (disableDefaultUI: true), only the Zoom control will be displayed. For better accessibility, consider enabling the Camera control instead. > If more time is needed > > If you need more time before adopting the default controls, you can specify version 3.59 <https://notifications.google.com/g/p/ANiao5ow4VNUJk__HI4mblHFJfMeJMaw_Finj4…> which will be available until February 2026. > > We’re here to help > > Refer to our Maps Javascript API documentation <https://notifications.google.com/g/p/ANiao5qsyBbh2CYZUmipt7KzVxkZMVFbyTgECd…> for information about how to edit google.maps.MapOptions to enable cameraControl. > > If you have any other questions or need additional support, please contact us at Google Maps Platform Support <https://notifications.google.com/g/p/ANiao5ppIKsOdKNy6_yUpCslMC8BFehp6yTQoj…>. > > Thanks for choosing Google Maps Platform. > > —The Google Maps Platform Team > DOCUMENTATION <https://notifications.google.com/g/p/ANiao5qsyBbh2CYZUmipt7KzVxkZMVFbyTgECd…> > SUPPORT <https://notifications.google.com/g/p/ANiao5ppIKsOdKNy6_yUpCslMC8BFehp6yTQoj…> > Was this information helpful? > > <https://notifications.google.com/g/p/ANiao5pZILQM1b3p6opNvUizjj_NIBTVPe4986…> <https://notifications.google.com/g/p/ANiao5p5GQ9cVrh3bRYpM3QGAM7prqqmLRoGC8…> <https://notifications.google.com/g/p/ANiao5ptPFc-jvMwzY4w1f3sROWRCXcmZPk4Dv…> > > © 2024 Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043 > > You have received this mandatory service announcement to update you about important changes to Google Maps Platform or your account. > <https://notifications.google.com/g/p/ANiao5qjT5ACsRSu2ISgsgTeXjLg8cVBs1FM5z…> <https://notifications.google.com/g/p/ANiao5oXaQzr8XIKW10CeDuc-8Yo2aD2yigAqc…> <https://notifications.google.com/g/p/ANiao5qz5afhVYmSAZgoBGCTKEJnBWd8qyS58z…>

1 0

Fwd: [Reminder] Update to latest renderer for the Maps SDK for Android
by Mark Webb-Johnson 22 Aug '24

22 Aug '24

> Begin forwarded message: > > From: Google Maps Platform <google-maps-platform-noreply(a)google.com> > Subject: [Reminder] Update to latest renderer for the Maps SDK for Android > > > > MY CONSOLE <https://notifications.google.com/g/p/ANiao5pYODAVleAYP31YM3qFAqF69deQGAMdNz…> > You may have projects using the legacy renderer that will be decommissioned by March 3, 2025. Apps built with the Maps SDK for Android have been automatically updated to the latest renderer as of June 2024. > Hello Google Maps Platform Customer, > > This is a follow up to the announcements sent in 2021 and 2022 regarding the new renderer for Maps SDK for Android. To provide an improved user experience and app performance, apps built with the Maps SDK for Android have been automatically updated to the latest renderer <https://notifications.google.com/g/p/ANiao5rHUSQmtxQPuR_Hi4TKlXg4tDqZbIsAS4…> as of June 2024. The legacy renderer is scheduled for decommissioning on March 3, 2025. > > What you need to know > > The new renderer was introduced in Maps SDK for Android version 18.0 in an opt-in manner. It is offered as a default starting on version 18.2, with an option to specify the Legacy renderer (Renderer.LEGACY) <https://notifications.google.com/g/p/ANiao5p_sMP-kXkk44kzDTYbQeeigaHx4l8GtY…>. > > Your app may be currently using the legacy renderer in two situations. > > Situation 1. If you use Maps SDK for Android version < 18, or 18.0-18.1 without opting in the new renderer: > We temporarily excluded your apps from the automatic migration because of issues occurring with the new renderer. > Situation 2. If you specify the legacy renderer (on version 18.0 or later): > Your application will continue receiving the legacy renderer until March 2025. Starting in March 2025, you will get the new renderer even if you specify the Legacy renderer. > During the migration period, Google will continue to provide support and fixes to major bugs and outages on the legacy renderer. New features and improvements are only offered on the new renderer. > > The new renderer is currently only available on Android phones. If your app is used on Wear OS or Android Go, the new renderer will be available in Google Play Services at a later time. Please follow the progress on this rollout by starring this issue tracker entry <https://notifications.google.com/g/p/ANiao5qoosfyI3uURXoB160BIBfnMmT3Wjh7DJ…>. > > What you need to do > > No action is recommended if your app already uses Maps SDK for Android v18.2.0 and does not specify a renderer during the initialization process. > > Updating to the latest renderer in the Maps SDK for Android may introduce a slight change to the performance and behavior of the maps in your app. Google does not expect this to cause any operational issues. > > We recommend that developers of mission-critical apps test their application with the new renderer ahead of the automatic update (happening in March 2025), in order to limit risks of potential issues. You can do this by updating the dependencies <https://notifications.google.com/g/p/ANiao5qBoAN36GRHwRebxaRYycpHnxbwxIDE3v…> for your app to the Maps SDK for Android version 18.2.0 or later, without specifying the Legacy renderer (Renderer.LEGACY) <https://notifications.google.com/g/p/ANiao5p_sMP-kXkk44kzDTYbQeeigaHx4l8GtY…>. > > See release notes <https://notifications.google.com/g/p/ANiao5ot7WEas73zIY1L9eGZf9xL-qF7EfBO1U…> for differences between older versions and version 18.2.0. > > We have determined that your projects listed below are using the Legacy renderer on Maps SDK for Android in the past 30 days: > > Project name (project number) Apps using the Legacy renderer on Maps SDK for Android > Open Vehicles (497749188588) <https://notifications.google.com/g/p/ANiao5q77GmjPv3wKlyvYh3WBn5EtLz_YqHp-s…> com.openvehicles.OVMS <> > Open Vehicles (497749188588) <https://notifications.google.com/g/p/ANiao5q77GmjPv3wKlyvYh3WBn5EtLz_YqHp-s…> com.openvehicles.ovms <> > Note: only the top 20 apps that sent the most traffic are listed for each project. > > [CONTACT SUPPORT <https://notifications.google.com/g/p/ANiao5oktol_g2I-H-e_ymHCwCXr9PsKxEjVm_…>] > > Thanks for choosing Google Maps Platform, > > The Google Maps Platform Team > SUPPORT <https://notifications.google.com/g/p/ANiao5oktol_g2I-H-e_ymHCwCXr9PsKxEjVm_…> > Was this information helpful? > > <https://notifications.google.com/g/p/ANiao5q4hF1gbk49JoN7NcZddRt64UPwdZUFqA…> <https://notifications.google.com/g/p/ANiao5r_p5BpareCayaikeW1scnCe4imPnpLwo…> <https://notifications.google.com/g/p/ANiao5pWq7mafh2Vp1omNXh0stCalRpa9e_16L…> > > © 2024 Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043 > > You have received this mandatory service announcement to update you about important changes to Google Maps Platform or your account. > <https://notifications.google.com/g/p/ANiao5pPAlGanFkLl3DRh7VEcQxyUHzXACAev_…> <https://notifications.google.com/g/p/ANiao5qDKwxx975-vy0xNbWg8GPyuM2-qb1wO2…> <https://notifications.google.com/g/p/ANiao5oq0Xc_rFn3MLZW5pP3vkR7TuI_aDZ198…>

1 0

Cellular usage, as it applies to OVMS
by Mark Webb-Johnson 16 Aug '24

16 Aug '24

I saw this the other day, and thought it applied perfectly to what we experience. We weren’t even pushing the limits of 2G. Mark

2 2

Warning in Duktape
by Michael Geddes 09 Aug '24

09 Aug '24

There's an unused variable 'dcc' warning in the below code. It seems that the 'Perform the callback' is not being 'performed! Is this deliberate? //.ichael void DukOvmsCommandRegisterRun(int verbosity, OvmsWriter* writer, OvmsCommand* cmd, int argc, const char* const* argv) { ESP_LOGD(TAG, "DukOvmsCommandRegisterRun(%s)",cmd->GetName()); auto it = MyDuktape.m_cmdmap.find(cmd); if (it == MyDuktape.m_cmdmap.end()) { ESP_LOGE(TAG, "Command '%s' cannot be found in registry",cmd->GetName ()); return; } else { DuktapeConsoleCommand* dcc = it->second; // Perform the callback } }

3 6

SDCard speed / max speed
by Michael Geddes 30 Jul '24

30 Jul '24

I was looking at adding the maximum host speed as well as the sdcard speed to the SD Card information. My question is whether the 'max speed' is apples-for-apples comparable with the card frequency or whether they are not quite the same thing? //. if (verbosity > COMMAND_RESULT_MINIMAL) { writer->printf("\nCard type: %s\n", (card->ocr & SD_OCR_SDHC_CAP)?"SDHC/SDXC":"SDSC"); - writer->printf("Max speed: %d kHz\n", card->csd.tr_speed/1000); + int maxspeed = card->csd.tr_speed/1000; + writer->printf("Max speed: %d kHz\n", maxspeed); + int maxfreq = MyPeripherals->m_sdcard->m_host.max_freq_khz; + if (maxspeed > maxfreq) + writer->printf("Max host speed: %d kHz\n", maxfreq); writer->printf("Capacity: %llu MB\n", ((uint64_t) card->csd.capacity) * card->csd.sector_size / (1024 * 1024)); writer->printf("CSD: ver=%d, sector_size=%d, capacity=%d read_bl_len=%d\n", card->csd.csd_ver,

2 1

Ovms Poller and Leaf, where are we at?
by Michael Geddes 28 Jul '24

28 Jul '24

I really want to make sure that we get this Leaf issue sorted out. Has there been any progress? Did my latest changes sort the issue out? //.ichael

1 0

Uart errors accessing SD Card
by Michael Geddes 22 Jul '24

22 Jul '24

Since forever I've been getting uart errors (4) - which seems to be an ERROR *E (56071827) uart_events: uart event type: 4* It seems it gets easily overwhelmed. For example while doing (From the web i/f) 'vfs ls /sd' is fine (there are only 15 entries there) .. the command: *vfs ls /sd/log* causes a whole bunch of the above uart errors (l50 or so) interrupted by the output of the command results (50 or so files). I'm not sure whether it lists all of them.. but probably? I was implementing file completion in 'vfs' command.. and it works except for when trying to complete in that directory. I suspect that it's overwhelming the limited spaces in the complete buffer.. but also the messages queue is getting swamped by all the uart_event errors. Thoughts? //.ichael

3 4

Google requiring API level 14+ for play apps
by Mark Webb-Johnson 17 Jul '24

17 Jul '24

Issue details Summary Status You won't be able to release app updates (45 days away) Date sent Jul 4, 2024 Deadline Aug 31, 2024 Violation App must target Android 14 (API level 34) or higher Details To provide users with a safe and secure experience, Google Play requires all apps to meet target API level requirements. From Aug 31, 2024, if your target API level is not within 1 year of the latest Android release, you won't be able to update your app. How to fix Your highest non-compliant target API level is Android 13 (API level 33). To ensure that you can continue to make updates to your app you must: Update your app to target Android 14 (API level 34) or higher. Publish a new version of your app to production. Before you do this, you can test your app using internal, closed, or open testing. Once you've done this, we'll send you an Inbox message to confirm that your app update was successful, and that your app is no longer affected. For more information: Learn more about the requirements <https://support.google.com/googleplay/android-developer/answer/11926878> Learn how to update your app <https://support.google.com/googleplay/android-developer/answer/9859350> Learn what changes you may need to make in your app <https://developer.android.com/google/play/requirements/target-sdk> Read the policy announcement <https://support.google.com/googleplay/android-developer/answer/13411745>

1 0