April 2019 - OvmsDev - Open Vehicles

Fwd: [ovms:2137] Limit speed and path
by Mark Webb-Johnson 18 Apr '19

18 Apr '19

@michael, or other twizy experts, can you help to answer the following support ticket? Thanks, Mark. > bricoauto has updated the ticket 'Limit speed and path': > https://www.openvehicles.com/node/2137#comment-5685 > State: active > Priority: normal > > You can visit the following URL to update this ticket: > https://www.openvehicles.com/node/2137#comment-form > > Update text: > ------------------------------ > > Dear Friend, excuse the delay. > I attached error image, and the firmware data. > The ovms is v 3.1. The vehicle is a Renault Twizy 80. > I have 3 same from different years, one from 2012, another from 2015 and > another from 2016. > In the 3 it happens the same, I can not change the limit of speed and the > limit of the route. > When I try, I activate the Can script in command # 15 with the number 1, then > I put the key in turn 2 activated and from the mobile APP I try to change the > speed or the path, and the message is that of the attached image. > We are an active tourism company, and we make excursions with these > vehicles, and we are interested in limiting the speed and the route. > Thank you and I hope your answer.

1 0

DA26 breakout
by Mark Webb-Johnson 08 Apr '19

08 Apr '19

If you have work to do on this DA26 expansion ports, this is pretty cool and well built: https://www.aliexpress.com/item/26-Pin-D-SUB-DB26-3-Rows-Serial-Parallel-Po… <https://www.aliexpress.com/item/26-Pin-D-SUB-DB26-3-Rows-Serial-Parallel-Po…>

2 3

Android App v3.12.2 in Play Store
by Michael Balzer 07 Apr '19

07 Apr '19

Whoa. Our first public App update since …drumroll… June 2014 :) I didn't get any bug reports for my 3.12.2 beta release, so I just finished some last details and uploaded it. May take some hours to appear in the Play Store. As change history has grown a bit beyond the allowed 500 chars for the release info, I've added a history page to the Wiki: https://github.com/openvehicles/Open-Vehicle-Android/wiki/History I'm afraid it's just the condensed gitlog though. I hope users won't get confused, sure could need some refinement. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

10 47

Kia e-Niro
by Geir Øyvind Vælidalo 07 Apr '19

07 Apr '19

Hi guys, I’ve sent a pull request with the support for the new Kia e-Niro. It is mostly on the same level of functionality as for the Kia Soul, with the exception of the estimated range! Everything needs to be polled in this car, so it has been quite time-consuming to find all the other data. I’ve found a ton of fun commands to control everything from the lights to the power seats, but the range is nowhere to be found :-( I’ll try to update the user guide and the list of supported metrics as soon as I can. BTW, as I have had the «pleasure» of going through the setup process a few times the last couple of months, I must say the process has become really slick! Well done! Best regards, Geir

2 1

Tesla Model S & X
by Mark Webb-Johnson 07 Apr '19

07 Apr '19

After months of stagnation, I am finally making some progress on Tesla Model S and X support. As a start, tonight’s edge update decodes the elusive estimated and ideal ranges. These cars are incredibly complex. Dozens of modules, 4 active CAN buses, an Ethernet network, two displays, and one of the busiest CAN buses I’ve ever seen. The CAN messages themselves are often packed tightly on bit (not byte) boundaries, so real hard to find the individual information items. The architecture itself is quite neat. There is a freertos based CAN gateway at the back of the Centre Information Display (CID). That takes all the CAN buses and gateways them to a single Ethernet connection joining the infotainment and other control systems. If the CID wants to transmit on the CAN bus (for example, to lock/unlock the doors), it sends a command to the gateway that converts it to a CAN bus message. Incoming CAN bus messaged get converted to UDP broadcasts. There is a great diagnostics tool built into the CID, but it is locked down by strong encryption. Rather than tear down my wife’s car, I think this is a better solution: It came from a scrapped, insurance written-off, Model S. I’ve also got this, but not much use for what I am doing at the moment. It didn’t take long to break into the diagnostics displays: And that is my first new message decode - the display SOC%, as well as rated and estimated ranges plus Wh/mile consumption. There is a huge amount of information there. Like the Tesla Roadster 1050 displays, on steroids... Hundreds of messages, all coming off the Ethernet. At the moment, the car is not connected, so I am just looking at messages from the MCU and Gateway themselves. But even that is close to 80 messages. I can see the values transmitted, and bus they are transmitted on, but no idea of CAN ID#, data length, or encoding. So, it is painstaking going through them one by one. The MCU messages themselves are a summary of car status, and look pretty good. Because they are isolated on the bench, it is relatively easy to work with them as a starting subset, and I am concentrating on the ones useful to OVMS (battery status, charge status, etc). It seems we have full charge status available, including supercharging, and the reason for charge termination. Once I’ve got the MCU messages decoded, it will be time for: $ nc mycar.local 3000 | nc bench.local 3000 to send all the data from the car to the bench and see what is displayed. I can then mess with the messages (fuzzing) to try to identify IDs and then data. The result of this work should be full OVMS support, and three DBC files describing the data. It would be much easier to have OVMS directly connected to the Ethernet, but Tesla will probably at some time lock that down, and it is so troublesome to take the dash apart to man-in-the-middle that. Regards, Mark.

2 1

Fasttech stock status
by Michael Balzer 01 Apr '19

01 Apr '19

Mark, any idea when the modules will be in stock again? Until a few days ago it was just the EU kit, so users could assemble the base module + modem, but now the base module is also sold out. Thanks, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

3 4