Am 22.12.22 um 22:31 schrieb Solterra:

Do people really donate vehicles?

I was hoping you'd help us get that tradition started ;-)

I'm in line to get one next week. I'm interested in contributing and wondering if there are others working on the same vehicle (or the bZ4X).

None that I know of yet, but sometimes people introduce themselves to this list with an already completed adaptation.

If you're going to do the initial decoding work for the car, here are some intitial links:

• https://www.openvehicles.com/developers
• https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/255#...

A good starting point for the vehicle module is cloning one of the more simple and more recent modules like that for the Hyundai Ioniq vFL.

Regards, Michael

Nice to meet you.

On 2022-12-22 16:24, Michael Balzer wrote:

...

Am 22.12.22 um 14:40 schrieb Solterra:

...

Any interest in adding support for Subaru Solterra?

Are you offering to donate a vehicle to a developer? If so, I'm sure some developer can be found to help you on this.

Or are you a developer planning to buy one and implement the support? If so, we'll help you getting started.

Regards, Michael

-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

Hey Solterra, I couldn't say definitively but imho there are various options depending on HOW different.

1. They are exactly the same - or differences can be distinguished from responses: Register the name with both in it. Done. (This has happened with some older Kia + Hyundai even)
2. They are mostly the same. You could probably keep the one directory but have 2 wrapper classes constructing the base class with a parameter and register both in the factory Init. (Not sure if there are examples - ask the other Michael if this is ok).
3. They have a lot of commonality. You can inherit off a base class - or inherit one vehicle impl off the other... But put them in separate directories. (This happens for Ioniq 5 and a bunch of other Kia + Hyundai cars).

//.ichael Geddes

On Sat, 27 May 2023 at 21:19, Solterra <solterra@kezarnet.com> wrote:

Hello again,

I've finished my initial vehicle investigation and am not ready to add support to OVMS.

When creating the vehicle stub, is there guidance for situations like on this vehicle? There are two makes and models that are essentially the same. Can I create a common 'components/vehicle_toyota_bz4x' and point two vehicle selections to it somewhere else?

Thank you

---

OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev

It's Toyota's e-TNGA platform. I know the CAN network is the same for Toyota bZ4X and Subaru Solterra, but I'm not sure about the bZ3 (China) and Lexus RZ... One complicating factor is there are two battery configurations for the bZ4X, one of which is shared with the Solterra.

Probably a detail for down the road a bit. For now, I've just created a bZ4X vehicle module and am tinkering under that.

On 2023-05-28 21:45, Mark Webb-Johnson wrote:

Solterra,

Michael's advice is good.

If it is just two names for essentially the same vehicle, I think you can refer to vehicle_voltampera (which implemented the Chevy Volt and Open Ampera vehicle support). These were essentially the same vehicle platform, but with minor bodywork differences and labelling.

If the two vehicles share the same platform (such as BMS, battery, etc) but are otherwise very different, then I suggest you implement a vehicle_<platform> for that platform, and derive two classes from that in the same /src/ directory (one for each vehicle type). That will allow you to put all common support code in the base platform, but have each vehicle type customisable (and individually selectable).

Looking at images of the cars, it seems they are closest to the Volt Ampera situation. Perhaps BZSS?

Regards, Mark.

On 28 May 2023, at 8:23 AM, Michael Geddes <frog@bunyip.wheelycreek.net> wrote:

Hey Solterra, I couldn't say definitively but imho there are various options depending on HOW different.

1. They are exactly the same - or differences can be distinguished from responses: Register the name with both in it. Done. (This has happened with some older Kia + Hyundai even)
2. They are mostly the same. You could probably keep the one directory but have 2 wrapper classes constructing the base class with a parameter and register both in the factory Init. (Not sure if there are examples - ask the other Michael if this is ok).
3. They have a lot of commonality. You can inherit off a base class - or inherit one vehicle impl off the other... But put them in separate directories. (This happens for Ioniq 5 and a bunch of other Kia + Hyundai cars).

//.ichael Geddes

On Sat, 27 May 2023 at 21:19, Solterra <solterra@kezarnet.com> wrote:

Hello again,

I've finished my initial vehicle investigation and am not ready to add support to OVMS.

When creating the vehicle stub, is there guidance for situations like on this vehicle? There are two makes and models that are essentially the same. Can I create a common 'components/vehicle_toyota_bz4x' and point two vehicle selections to it somewhere else?

Thank you

---

OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev

---

OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev

OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev

I've decided on a structure, so I'll outline it here.

My major problem is that I don't know how different the vehicles are (I just have the Subaru...). So, I created a Toyota e-TNGA class where most of the functionality lives. I then created a wrapper for the Subaru (and will do the same for bZ4X). The same code likely works for Lexus RZ450e as well.

I guess when I (or someone else) finds a difference, at least there's a home for the code.

Thanks for your advice.

On 2023-05-29 20:21, Michael Geddes wrote:

Just FYI on the Ioniq5 I was able to see using the 'valid bits' which of the battery voltages were valid, therefore hopefully what the overall battery capacity is. I have not got feedback on any different battery configs yet... You can have a look at what I've done there anyway.

Sounds good anyway.

Michael

On Tue, 30 May 2023, 3:29 am Solterra, <solterra@kezarnet.com> wrote:

It's Toyota's e-TNGA platform. I know the CAN network is the same for Toyota bZ4X and Subaru Solterra, but I'm not sure about the bZ3 (China) and Lexus RZ... One complicating factor is there are two battery configurations for the bZ4X, one of which is shared with the Solterra.

Probably a detail for down the road a bit. For now, I've just created a bZ4X vehicle module and am tinkering under that.

On 2023-05-28 21:45, Mark Webb-Johnson wrote:

Solterra,

Michael's advice is good.

If it is just two names for essentially the same vehicle, I think you can refer to vehicle_voltampera (which implemented the Chevy Volt and Open Ampera vehicle support). These were essentially the same vehicle platform, but with minor bodywork differences and labelling.

If the two vehicles share the same platform (such as BMS, battery, etc) but are otherwise very different, then I suggest you implement a vehicle_<platform> for that platform, and derive two classes from that in the same /src/ directory (one for each vehicle type). That will allow you to put all common support code in the base platform, but have each vehicle type customisable (and individually selectable).

Looking at images of the cars, it seems they are closest to the Volt Ampera situation. Perhaps BZSS?

Regards, Mark.

On 28 May 2023, at 8:23 AM, Michael Geddes <frog@bunyip.wheelycreek.net> wrote:

Hey Solterra, I couldn't say definitively but imho there are various options depending on HOW different.

1. They are exactly the same - or differences can be distinguished from responses: Register the name with both in it. Done. (This has happened with some older Kia + Hyundai even)
2. They are mostly the same. You could probably keep the one directory but have 2 wrapper classes constructing the base class with a parameter and register both in the factory Init. (Not sure if there are examples - ask the other Michael if this is ok).
3. They have a lot of commonality. You can inherit off a base class - or inherit one vehicle impl off the other... But put them in separate directories. (This happens for Ioniq 5 and a bunch of other Kia + Hyundai cars).

//.ichael Geddes

On Sat, 27 May 2023 at 21:19, Solterra <solterra@kezarnet.com> wrote:

Hello again,

I've finished my initial vehicle investigation and am not ready to add support to OVMS.

When creating the vehicle stub, is there guidance for situations like on this vehicle? There are two makes and models that are essentially the same. Can I create a common 'components/vehicle_toyota_bz4x' and point two vehicle selections to it somewhere else?

Thank you

---

OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev

---

OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev

OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev

OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev

OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev