Hi guys, I would like to have ChaDeMo and CSS added to car_chargemode, and maybe Type 1 and Type 2 too. Then we can display those names in the apps and maybe even add images for those charge plugs. I would propose this: 0x00 - Standard 0x01 - Storage 0x02 - ??? 0x03 - Range 0x04 - Performance 0x05 - ChaDeMo 0x06 - CSS 0x07 - J1772 Type 1 0x08 - Mennekes Type 2 What to you guys think? Would it be problematic for the server and/or apps if suddenly the Kia Souls stated sending chargemode 0x05? Best regards, Geir
The chargemode currently encodes software charging profiles, based on what the Roadster offers. It's similar to what the early Leafs offered, charging to full or charge to 80%, but more complex setting both a charging limit and target battery temperature ranges. What you are proposing adding is to encode the charging connection type, which is a different kind of thing, orthogonal to the car's chosen charging profile. A Roadster can charge in any of the four profiles from either a Level 1 connection (120V, 12A to 16A) or Level 2 (208V to 240V at up to 70A), for example Standard mode on Level 1 or Range mode on Level 2. So, you can't encode both a charging profile and a connection type with a single number. A Leaf is similar in how those two interact. To me, the interesting thing is more the charge rate (V/A or kW) more than which connector my car uses. I don't need OVMS to tell me how I plugged in, but I do care about knowing how fast it's charging. Tom On 12/8/15, 10:19 AM, "Geir Øyvind Vælidalo" <ovmsdev-bounces@lists.teslaclub.hk on behalf of geir@validalo.net> wrote:
Hi guys,
I would like to have ChaDeMo and CSS added to car_chargemode, and maybe Type 1 and Type 2 too. Then we can display those names in the apps and maybe even add images for those charge plugs. I would propose this: 0x00 - Standard 0x01 - Storage 0x02 - ??? 0x03 - Range 0x04 - Performance 0x05 - ChaDeMo 0x06 - CSS 0x07 - J1772 Type 1 0x08 - Mennekes Type 2
What to you guys think? Would it be problematic for the server and/or apps if suddenly the Kia Souls stated sending chargemode 0x05?
Best regards, Geir
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Charge type would become important if you were automatically sending charge session data back (anonymously) to the OCM database… ᐧ [image: --] Nikki Gordon-Bloomfield [image: https://]about.me/aminorjourney <https://about.me/aminorjourney?promo=email_sig> On Tue, Dec 8, 2015 at 10:46 AM, Tom Saxton <tom@idleloop.com> wrote:
The chargemode currently encodes software charging profiles, based on what the Roadster offers. It's similar to what the early Leafs offered, charging to full or charge to 80%, but more complex setting both a charging limit and target battery temperature ranges.
What you are proposing adding is to encode the charging connection type, which is a different kind of thing, orthogonal to the car's chosen charging profile.
A Roadster can charge in any of the four profiles from either a Level 1 connection (120V, 12A to 16A) or Level 2 (208V to 240V at up to 70A), for example Standard mode on Level 1 or Range mode on Level 2. So, you can't encode both a charging profile and a connection type with a single number. A Leaf is similar in how those two interact.
To me, the interesting thing is more the charge rate (V/A or kW) more than which connector my car uses. I don't need OVMS to tell me how I plugged in, but I do care about knowing how fast it's charging.
Tom
On 12/8/15, 10:19 AM, "Geir Øyvind Vælidalo" < ovmsdev-bounces@lists.teslaclub.hk on behalf of geir@validalo.net> wrote:
Hi guys,
I would like to have ChaDeMo and CSS added to car_chargemode, and maybe Type 1 and Type 2 too. Then we can display those names in the apps and maybe even add images for those charge plugs. I would propose this: 0x00 - Standard 0x01 - Storage 0x02 - ??? 0x03 - Range 0x04 - Performance 0x05 - ChaDeMo 0x06 - CSS 0x07 - J1772 Type 1 0x08 - Mennekes Type 2
What to you guys think? Would it be problematic for the server and/or apps if suddenly the Kia Souls stated sending chargemode 0x05?
Best regards, Geir
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
I like the idea of having charge type for logging purposes. I agree it shouldn't be combined with the Roadster charging types. Can just create a new "field" called connector type? On 12/8/2015 2:07 PM, Nikki Gordon-Bloomfield wrote:
Charge type would become important if you were automatically sending charge session data back (anonymously) to the OCM database… ᐧ
--
Nikki Gordon-Bloomfield https://about.me/aminorjourney
<https://about.me/aminorjourney?promo=email_sig>
On Tue, Dec 8, 2015 at 10:46 AM, Tom Saxton <tom@idleloop.com <mailto:tom@idleloop.com>> wrote:
The chargemode currently encodes software charging profiles, based on what the Roadster offers. It's similar to what the early Leafs offered, charging to full or charge to 80%, but more complex setting both a charging limit and target battery temperature ranges.
What you are proposing adding is to encode the charging connection type, which is a different kind of thing, orthogonal to the car's chosen charging profile.
A Roadster can charge in any of the four profiles from either a Level 1 connection (120V, 12A to 16A) or Level 2 (208V to 240V at up to 70A), for example Standard mode on Level 1 or Range mode on Level 2. So, you can't encode both a charging profile and a connection type with a single number. A Leaf is similar in how those two interact.
To me, the interesting thing is more the charge rate (V/A or kW) more than which connector my car uses. I don't need OVMS to tell me how I plugged in, but I do care about knowing how fast it's charging.
Tom
On 12/8/15, 10:19 AM, "Geir Øyvind Vælidalo" <ovmsdev-bounces@lists.teslaclub.hk <mailto:ovmsdev-bounces@lists.teslaclub.hk> on behalf of geir@validalo.net <mailto:geir@validalo.net>> wrote:
>Hi guys, > >I would like to have ChaDeMo and CSS added to car_chargemode, and maybe Type 1 and Type 2 too. Then we can display those names in the apps and maybe even add images for those charge plugs. >I would propose this: >0x00 - Standard >0x01 - Storage >0x02 - ??? >0x03 - Range >0x04 - Performance >0x05 - ChaDeMo >0x06 - CSS >0x07 - J1772 Type 1 >0x08 - Mennekes Type 2 > >What to you guys think? Would it be problematic for the server and/or apps if suddenly the Kia Souls stated sending chargemode 0x05? > >Best regards, >Geir > >_______________________________________________ >OvmsDev mailing list >OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> >http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Yep, please steer clear of the car_chargermode variable. That is really badly named and is more an operation mode (like Eco/Normal on a Prius, for example). I think it is named as it is because the source on the roadster is the charger message. I suggest: unsigned char car_chargeplug; and setup an enumeration as desired. Create it in ovms.{h,c} and then add it on the end of the ’S’ message. If someone wants to commit that and send in a pull request, I’ll accept (and update the protocol guide myself). Regards, Mark.
On 9 Dec 2015, at 3:10 AM, Robert Cotran <robert@cotran.ca> wrote:
I like the idea of having charge type for logging purposes.
I agree it shouldn't be combined with the Roadster charging types.
Can just create a new "field" called connector type?
On 12/8/2015 2:07 PM, Nikki Gordon-Bloomfield wrote:
Charge type would become important if you were automatically sending charge session data back (anonymously) to the OCM database… ᐧ
Nikki Gordon-Bloomfield about.me/aminorjourney <https://about.me/aminorjourney?promo=email_sig>
On Tue, Dec 8, 2015 at 10:46 AM, Tom Saxton <tom@idleloop.com <mailto:tom@idleloop.com>> wrote: The chargemode currently encodes software charging profiles, based on what the Roadster offers. It's similar to what the early Leafs offered, charging to full or charge to 80%, but more complex setting both a charging limit and target battery temperature ranges.
What you are proposing adding is to encode the charging connection type, which is a different kind of thing, orthogonal to the car's chosen charging profile.
A Roadster can charge in any of the four profiles from either a Level 1 connection (120V, 12A to 16A) or Level 2 (208V to 240V at up to 70A), for example Standard mode on Level 1 or Range mode on Level 2. So, you can't encode both a charging profile and a connection type with a single number. A Leaf is similar in how those two interact.
To me, the interesting thing is more the charge rate (V/A or kW) more than which connector my car uses. I don't need OVMS to tell me how I plugged in, but I do care about knowing how fast it's charging.
Tom
On 12/8/15, 10:19 AM, "Geir Øyvind Vælidalo" < <mailto:ovmsdev-bounces@lists.teslaclub.hk>ovmsdev-bounces@lists.teslaclub.hk <mailto:ovmsdev-bounces@lists.teslaclub.hk> on behalf of geir@validalo.net <mailto:geir@validalo.net>> wrote:
Hi guys,
I would like to have ChaDeMo and CSS added to car_chargemode, and maybe Type 1 and Type 2 too. Then we can display those names in the apps and maybe even add images for those charge plugs. I would propose this: 0x00 - Standard 0x01 - Storage 0x02 - ??? 0x03 - Range 0x04 - Performance 0x05 - ChaDeMo 0x06 - CSS 0x07 - J1772 Type 1 0x08 - Mennekes Type 2
What to you guys think? Would it be problematic for the server and/or apps if suddenly the Kia Souls stated sending chargemode 0x05?
Best regards, Geir
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Robert, maybe this is something you could do? As your first task in OVMS? :-) Regards, Geir Sendt fra min iPhone
Den 9. des. 2015 kl. 07.50 skrev Mark Webb-Johnson <mark@webb-johnson.net>:
Yep, please steer clear of the car_chargermode variable. That is really badly named and is more an operation mode (like Eco/Normal on a Prius, for example). I think it is named as it is because the source on the roadster is the charger message.
I suggest:
unsigned char car_chargeplug;
and setup an enumeration as desired. Create it in ovms.{h,c} and then add it on the end of the ’S’ message.
If someone wants to commit that and send in a pull request, I’ll accept (and update the protocol guide myself).
Regards, Mark.
On 9 Dec 2015, at 3:10 AM, Robert Cotran <robert@cotran.ca> wrote:
I like the idea of having charge type for logging purposes.
I agree it shouldn't be combined with the Roadster charging types.
Can just create a new "field" called connector type?
On 12/8/2015 2:07 PM, Nikki Gordon-Bloomfield wrote: Charge type would become important if you were automatically sending charge session data back (anonymously) to the OCM database… ᐧ
Nikki Gordon-Bloomfield about.me/aminorjourney
On Tue, Dec 8, 2015 at 10:46 AM, Tom Saxton <tom@idleloop.com> wrote: The chargemode currently encodes software charging profiles, based on what the Roadster offers. It's similar to what the early Leafs offered, charging to full or charge to 80%, but more complex setting both a charging limit and target battery temperature ranges.
What you are proposing adding is to encode the charging connection type, which is a different kind of thing, orthogonal to the car's chosen charging profile.
A Roadster can charge in any of the four profiles from either a Level 1 connection (120V, 12A to 16A) or Level 2 (208V to 240V at up to 70A), for example Standard mode on Level 1 or Range mode on Level 2. So, you can't encode both a charging profile and a connection type with a single number. A Leaf is similar in how those two interact.
To me, the interesting thing is more the charge rate (V/A or kW) more than which connector my car uses. I don't need OVMS to tell me how I plugged in, but I do care about knowing how fast it's charging.
Tom
On 12/8/15, 10:19 AM, "Geir Øyvind Vælidalo" <ovmsdev-bounces@lists.teslaclub.hk on behalf of geir@validalo.net> wrote:
Hi guys,
I would like to have ChaDeMo and CSS added to car_chargemode, and maybe Type 1 and Type 2 too. Then we can display those names in the apps and maybe even add images for those charge plugs. I would propose this: 0x00 - Standard 0x01 - Storage 0x02 - ??? 0x03 - Range 0x04 - Performance 0x05 - ChaDeMo 0x06 - CSS 0x07 - J1772 Type 1 0x08 - Mennekes Type 2
What to you guys think? Would it be problematic for the server and/or apps if suddenly the Kia Souls stated sending chargemode 0x05?
Best regards, Geir
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Or car_chargetype Mark
On 9 Dec 2015, at 4:44 PM, Geir Øyvind Vælidalo <geir@validalo.net> wrote:
Robert, maybe this is something you could do? As your first task in OVMS? :-)
Regards, Geir
Sendt fra min iPhone
Den 9. des. 2015 kl. 07.50 skrev Mark Webb-Johnson <mark@webb-johnson.net>:
Yep, please steer clear of the car_chargermode variable. That is really badly named and is more an operation mode (like Eco/Normal on a Prius, for example). I think it is named as it is because the source on the roadster is the charger message.
I suggest:
unsigned char car_chargeplug;
and setup an enumeration as desired. Create it in ovms.{h,c} and then add it on the end of the ’S’ message.
If someone wants to commit that and send in a pull request, I’ll accept (and update the protocol guide myself).
Regards, Mark.
On 9 Dec 2015, at 3:10 AM, Robert Cotran <robert@cotran.ca> wrote:
I like the idea of having charge type for logging purposes.
I agree it shouldn't be combined with the Roadster charging types.
Can just create a new "field" called connector type?
On 12/8/2015 2:07 PM, Nikki Gordon-Bloomfield wrote: Charge type would become important if you were automatically sending charge session data back (anonymously) to the OCM database… ᐧ
Nikki Gordon-Bloomfield about.me/aminorjourney
On Tue, Dec 8, 2015 at 10:46 AM, Tom Saxton <tom@idleloop.com> wrote: The chargemode currently encodes software charging profiles, based on what the Roadster offers. It's similar to what the early Leafs offered, charging to full or charge to 80%, but more complex setting both a charging limit and target battery temperature ranges.
What you are proposing adding is to encode the charging connection type, which is a different kind of thing, orthogonal to the car's chosen charging profile.
A Roadster can charge in any of the four profiles from either a Level 1 connection (120V, 12A to 16A) or Level 2 (208V to 240V at up to 70A), for example Standard mode on Level 1 or Range mode on Level 2. So, you can't encode both a charging profile and a connection type with a single number. A Leaf is similar in how those two interact.
To me, the interesting thing is more the charge rate (V/A or kW) more than which connector my car uses. I don't need OVMS to tell me how I plugged in, but I do care about knowing how fast it's charging.
Tom
On 12/8/15, 10:19 AM, "Geir Øyvind Vælidalo" <ovmsdev-bounces@lists.teslaclub.hk on behalf of geir@validalo.net> wrote:
Hi guys,
I would like to have ChaDeMo and CSS added to car_chargemode, and maybe Type 1 and Type 2 too. Then we can display those names in the apps and maybe even add images for those charge plugs. I would propose this: 0x00 - Standard 0x01 - Storage 0x02 - ??? 0x03 - Range 0x04 - Performance 0x05 - ChaDeMo 0x06 - CSS 0x07 - J1772 Type 1 0x08 - Mennekes Type 2
What to you guys think? Would it be problematic for the server and/or apps if suddenly the Kia Souls stated sending chargemode 0x05?
Best regards, Geir
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Une petite chose a tu retrouvé le lien du Pickit 2 que tu utilisais ? car celui pro sur le site de microchip… soit le Pickit V2.53 ou bien meme le V2.61 ne fonctionne pas possible de programer…. sur le V2.53 je n’ai pas le PIC dans la liste des devices id….. sur le V2.61 j’ai bien le PIC18F2685 mais la programmation ne fonctionne pas…… je ne comprend pas…… j’ai essayé le PIC 3 et lui me dit qui faut une alimentation supplémentaire… j’ai donc fourni du 12V depuis la prise ODB mais idem…… une idée?
Le 9 déc. 2015 à 10:37, Mark Webb-Johnson <mark@webb-johnson.net> a écrit :
Or
car_chargetype
Mark
On 9 Dec 2015, at 4:44 PM, Geir Øyvind Vælidalo <geir@validalo.net <mailto:geir@validalo.net>> wrote:
Robert, maybe this is something you could do? As your first task in OVMS? :-)
Regards, Geir
Sendt fra min iPhone
Den 9. des. 2015 kl. 07.50 skrev Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>>:
Yep, please steer clear of the car_chargermode variable. That is really badly named and is more an operation mode (like Eco/Normal on a Prius, for example). I think it is named as it is because the source on the roadster is the charger message.
I suggest:
unsigned char car_chargeplug;
and setup an enumeration as desired. Create it in ovms.{h,c} and then add it on the end of the ’S’ message.
If someone wants to commit that and send in a pull request, I’ll accept (and update the protocol guide myself).
Regards, Mark.
On 9 Dec 2015, at 3:10 AM, Robert Cotran <robert@cotran.ca <mailto:robert@cotran.ca>> wrote:
I like the idea of having charge type for logging purposes.
I agree it shouldn't be combined with the Roadster charging types.
Can just create a new "field" called connector type?
On 12/8/2015 2:07 PM, Nikki Gordon-Bloomfield wrote:
Charge type would become important if you were automatically sending charge session data back (anonymously) to the OCM database… ᐧ
Nikki Gordon-Bloomfield about.me/aminorjourney <https://about.me/aminorjourney?promo=email_sig>
On Tue, Dec 8, 2015 at 10:46 AM, Tom Saxton <tom@idleloop.com <mailto:tom@idleloop.com>> wrote: The chargemode currently encodes software charging profiles, based on what the Roadster offers. It's similar to what the early Leafs offered, charging to full or charge to 80%, but more complex setting both a charging limit and target battery temperature ranges.
What you are proposing adding is to encode the charging connection type, which is a different kind of thing, orthogonal to the car's chosen charging profile.
A Roadster can charge in any of the four profiles from either a Level 1 connection (120V, 12A to 16A) or Level 2 (208V to 240V at up to 70A), for example Standard mode on Level 1 or Range mode on Level 2. So, you can't encode both a charging profile and a connection type with a single number. A Leaf is similar in how those two interact.
To me, the interesting thing is more the charge rate (V/A or kW) more than which connector my car uses. I don't need OVMS to tell me how I plugged in, but I do care about knowing how fast it's charging.
Tom
On 12/8/15, 10:19 AM, "Geir Øyvind Vælidalo" < <mailto:ovmsdev-bounces@lists.teslaclub.hk>ovmsdev-bounces@lists.teslaclub.hk <mailto:ovmsdev-bounces@lists.teslaclub.hk> on behalf of geir@validalo.net <mailto:geir@validalo.net>> wrote:
Hi guys,
I would like to have ChaDeMo and CSS added to car_chargemode, and maybe Type 1 and Type 2 too. Then we can display those names in the apps and maybe even add images for those charge plugs. I would propose this: 0x00 - Standard 0x01 - Storage 0x02 - ??? 0x03 - Range 0x04 - Performance 0x05 - ChaDeMo 0x06 - CSS 0x07 - J1772 Type 1 0x08 - Mennekes Type 2
What to you guys think? Would it be problematic for the server and/or apps if suddenly the Kia Souls stated sending chargemode 0x05?
Best regards, Geir
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
OvmsDev mailing list OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Ah… Ok, I see that I misunderstood the charge mode a bit :-) Sounds to me Introducing a new variable is probably the best way to go then. The Kia Soul support 80% and 100%, but we don’t have any way of starting or stopping the charging from OVMS, yet. Regards, Geir
Geir, the server is very agnostic about the content data, should be no problem. car_chargemode is in fact up to now a Tesla Roadster specific thing, that's still interpreted by the framework. On the roadster, this does not reflect the plug type, but the charging program selected by the user. While that's a good idea, most other cars don't offer this option (yet). I think only the Leaf offers two charge modes (80% / 100%). Modes could be implemented in the OVMS though, if the OVMS can control the charge (read: terminate when the desired SOC has been reached). So introducing plug types as charge modes is a semantic mockup. A possible solution is to define a bit mask for a charge mode part (i.e. lower three bits) and another mask for the plug type. Or we can introduce a new virtual car variable "car_chargeplugtype" for this. Openchargemap.org currently lists 35 known plug types (+ 0 = unknown), see http://api.openchargemap.io/v2/referencedata/ for their IDs. So using 5 bits of car_chargemode will not yield enough place, IMO you should introduce a new framework variable. You can simply add that new variable to the MSG protocol "S" (status) message, just add it at the end to make it compatible. The server will just store it, clients (Apps) will automatically receive it but need to be extended to interpret & display it. Regards, Michael Am 08.12.2015 um 19:19 schrieb Geir Øyvind Vælidalo:
Hi guys,
I would like to have ChaDeMo and CSS added to car_chargemode, and maybe Type 1 and Type 2 too. Then we can display those names in the apps and maybe even add images for those charge plugs. I would propose this: 0x00 - Standard 0x01 - Storage 0x02 - ??? 0x03 - Range 0x04 - Performance 0x05 - ChaDeMo 0x06 - CSS 0x07 - J1772 Type 1 0x08 - Mennekes Type 2
What to you guys think? Would it be problematic for the server and/or apps if suddenly the Kia Souls stated sending chargemode 0x05?
Best regards, Geir
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 8335735 * Handy 0176 / 206 989 26
participants (7)
-
Geir Øyvind Vælidalo -
Gregory PETIT -
Mark Webb-Johnson -
Michael Balzer -
Nikki Gordon-Bloomfield -
Robert Cotran -
Tom Saxton