Just a summary of the current metrics (as previously read from can bus) and tyre sets (as manually defined, or previously read and stored using 'tpms read').
Excited as the TPMS board arrived today. Installation went smooth, left SW1 on 2 and moved S1 to other side of "On". Then logged in to OVMS while the car ignition was switched on, and executed some commands (see below) but writing/reading seem to not work. How can I check whether the right sensors are installed on the car? or anything else I can try? --- OVMS# module summary OVMS MODULE SUMMARY Module Version: 3.2.014/ota_1/main (build idf v3.3.2-881-g22d636b Aug 4 2020 16:26:20) Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1 12v: 13.1v SIMCOM Modem Status Network Registration: NotRegistered Provider: Signal: -77 dBm State: PoweredOn Ticker: 15 User Data: 0 HW FIFO overflows: 0 Buffer overflows: 0 State Timeout Goto: PoweringOn (in 15 seconds) Mux Status: down Open Channels: 0 Framing Errors: 0 Last RX frame: 0 sec(s) ago RX frames: 0 TX frames: 0 PPP: Not connected GPS: Not connected Status: disabled Time: disabled Configuration [auto] dbc: no egpio: no ext12v: no init: yes modem: yes obd2ecu: scripting: yes server.v2: yes server.v3: no vehicle.type: TR wifi.mode: apclient wifi.ssid.ap: TSLAOVMS wifi.ssid.client: SOTR [can] [dbc] [egpio] monitor.ports: [http.plugin] PINcrack.auth: Cookie PINcrack.enable: yes PINcrack.label: PIN Crack PINcrack.menu: Tools PINcrack.page: /store/usr/pincrack retools.auth: Cookie retools.enable: yes retools.label: RE Toolkit retools.menu: Tools retools.page: /usr/retools [http.server] [locations] Home: -33.791340,151.126648,50 [log] file.enable: yes file.path: /sd/log level: info [modem] apn: hologram apn.password: apn.user: enable.gps: no enable.gpstime: no enable.net: yes enable.sms: yes pincode: [module] cfgversion: 2020053100 init: done [network] dns: [notify] [obd2ecu] [obd2ecu.map] [ota] http.mru: api.openvehicles.com/firmware/ota/v3.1/main/ovms3.bin server: api.openvehicles.com/firmware/ota [password] module: **redacted** pin: **redacted** server.v2: **redacted** server.v3: **redacted** [power] 12v_shutdown_delay: 30 enabled: yes modemoff_delay: 96 wifioff_delay: 24 [pushover] [sdcard] maxfreq.khz: 20000 [server.v2] server: api.openvehicles.com tls: yes [server.v3] port: server: io.adafruit.com tls: yes topic.prefix: updatetime.connected: updatetime.idle: user: pdanhieux [ssh.info] fingerprint: i8rI16FOYs+bI37EIJYdgewP18N77uEk5gF9KRTipRA [ssh.keys] [ssh.server] key: **redacted** [system.adc] factor12v: 195.7 [tpms] 1: tires: 11111111,22222222,33333333,44444444 [usr] [vehicle] 12v.alert: 12v.ref: id: TSLA771 name: timezone: AEST-10AEDT,M10.1.0,M4.1.0/3 timezone_region: Australia/Sydney units.distance: K [wifi.ap] TSLAOVMS: **redacted** [wifi.ssid] SOTR: **redacted** [xtr] digital.speedo: yes digital.speedo.reps: 3 REPORT ENDS OVMS# tpms status TPMS data is stale. Information shown below is not up to date TPMS status: FL: FR: RL: RR: Tyre Sets: 1: tires: 11111111,22222222,33333333,44444444 OVMS# tpms write Usage: tpms write <set> OVMS# tpms write tires Error: Tyre IDs could not be written to the vehicle (or not implemented) OVMS# tpms status TPMS data is stale. Information shown below is not up to date TPMS status: FL: FR: RL: RR: Tyre Sets: 1: tires: 11111111,22222222,33333333,44444444 OVMS# tpms read Error: TPMS IDs could not be read from the vehicle (or not implemented) OVMS# tpms list Tyre Sets: 1: tires: 11111111,22222222,33333333,44444444 OVMS#
and looking in the debug shell console, I saw this: E (59670) v-teslaroadster: TPMS write (38 bytes) was not formatted as expected I (60120) simcom: State: Enter NetMode state I (60120) gsm-ppp: Initialising... I (62970) gsm-ppp: StatusCallBack: None I (62980) gsm-ppp: status_cb: Connected I (62980) gsm-ppp: our_ipaddr = 10.117.XXX.XXX I (62980) gsm-ppp: his_ipaddr = 10.64.64.64 I (62980) gsm-ppp: netmask = 255.255.255.255 I (62980) gsm-ppp: DNS#0 = 212.9.0.135 I (62980) gsm-ppp: DNS#1 = 212.9.0.136 I (62980) gsm-ppp: our6_ipaddr = :: I (63020) netmanager: Set DNS#1 0.0.0.0 I (63020) netmanager: Set DNS#2 0.0.0.0 I (63020) netmanager: MODEM up (with WIFI client up): staying with WIFI client priority E (76960) v-teslaroadster: TPMS read was 19 bytes (38 expected)
Do you definitely have TPMS installed? Yours is a UK spec car from 2011 and although these have TPMS transmitters in the wheels they (mostly or always) came without the antennae and TPMS is therefore not functional.
That's what I suspect as well. Is there any easy way to check without going under the car and taking the bottom off?
Anybody have a link to the correct TPMS to buy for a 2.5? Mine in the summer tires are dead (confirmed by Discount Tire), and my winter tires never had any. Looking forward to having this feature again.
I just swapped out my summer wheels for my winter wheels today. For the first time in almost 10 years, I was also able to write the "winter" tire TPMS ID numbers to the TPMS module, rather than chasing down someone at my Tesla SC and hoping they would find time, and find the tool, to do this. Thank you again to Mark, Steve and all of the others in this forum who worked on this great project. With OVMS programming being continually updated, I hope I am not out of line to make a suggestion as to what the TPMS command info line returns, if possible. It took me a little while going through this thread to recall (or learn again) that I needed the ignition on to "read" and "write" to the TPMS module. This may be self-evident to those who work on the car every day, but it was not something I kept in my mind. Therefore, if the basic TPMS command usage notation could return (with the suggested addition in red): OVMS# tpms Subcommand required Usage: tpms delete|list|read|set|status|write [Note: Turn ignition on to "read" or "write"] This is just a suggestion if it fits in with future updates and does not involve a lot of work. I know that come March and summer tires, I will likely once again forget that the ignition must be on to read or write, and there may be others out there like me. Having the TPMS command remind on this would be useful. -- John [Edit]: Actually, I misspeak. This is the second time -- last Spring prior to the OVMS TPMS function being completed, Steve lent me his ingenious TMPS sensor writing tool which I used to set my Roadster for the summer wheels.
Glad to hear it is working for you, and a useful capability. It was fun to work on this. Regarding your suggestion, it is not trivial to add that text there - as it is auto-generated from the console command line handler and not something we usually customise. We can, however, check if the car is on/off and if the tpms read/write commands fail then give a better error message if the car is OFF. I've raised the enhancement request here, to make sure it is not lost: TPMS read/write requires vehicle to be ON · Issue #489 · openvehicles/Open-Vehicle-Monitoring-System-3 Regards, Mark.