Hi All, I like where OVMS project is going and would like to help if I can. Where I can possibly add value is make things easy for people to use (eg documentation, etc) experienced on UI/UX design, etc. as an ex developer, good at testing and finding problems. Some initial thoughts on activities are to make it easier for non technical people to use OVMS, help doc author pull out user only specific content to a user manual and make it non-technical (renaming current user manual to developers manual) to help people see roadmap, provide a mechanism to see who wants what and who is working on it. to allow developers and users to display problems with their vehicle only, add Labels to the github issues list or group by project (I am not an expert on GITHUB so please be patient) update GITHUB readmes to better direct people that find GITHUB first. Please let me know if anyone is dealing with any of these areas add and/or vote for what things you think I can help with by putting a comment next to the activity above. Regards, Robert Sharpe Electric Vehicle Consultant 07711 252971 Your Plugged-in Partner Evergreen Consulting is the trading name of Sharpe Consultants Ltd
Robert, thanks for joining and offering help on the documentation & support side. Before beginning to work on improvements please first make sure you're up to date on existing features, documents and issues. These are the channels to know: * this mailing list: http://lists.openvehicles.com/pipermail/ovmsdev/ * the github issues/todo list: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues (+ iOS & Android app repositories) o + https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master... o + https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master... * the git log: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commits/mas... o + https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/master... * the openvehicles.com site: o Forum: https://www.openvehicles.com/forum o Support area: https://www.openvehicles.com/support/openvehicles * the user guide: https://docs.google.com/document/d/16JrXR7rybp-18DrEoeh1rg6GqQT_jVBvhaXh2oEW... * the developer guide: https://docs.google.com/document/d/1q5M9Lb5jzQhJzPMnkMKwy4Es5YK12ACQejX_NWEi... Noone I know of is currently focused on documentation / public presentation, and we can use some help there. The repository readme certainly could have an update, it's still the v1 readme. There is no "formal" roadmap, as there is noone keeping books of ideas and todos. We're also rather building a city than a road. Some beginner tutorial would be nice. That should come from real beginner questions & issues using the current version -- note most issues in the support area were related to earlier versions. It seems the current version is already quite easy to use, first questions tend to become more specific now. Regards, Michael Am 03.08.2018 um 10:01 schrieb Robert Sharpe (Electric Vehicle Consultant):
Hi All,
I like where OVMS project is going and would like to help if I can.
Where I can possibly add value is
* make things easy for people to use (eg documentation, etc) * experienced on UI/UX design, etc. * as an ex developer, good at testing and finding problems.
Some initial thoughts on activities are
* to make it easier for non technical people to use OVMS, help doc author pull out user only specific content to a user manual and make it non-technical (renaming current user manual to developers manual) * to help people see roadmap, provide a mechanism to see who wants what and who is working on it. * to allow developers and users to display problems with their vehicle only, add Labels to the github issues list or group by project (I am not an expert on GITHUB so please be patient) * update GITHUB readmes to better direct people that find GITHUB first.
Please
* let me know if anyone is dealing with any of these areas * add and/or vote for what things you think I can help with by putting a comment next to the activity above.
Regards, Robert Sharpe Electric Vehicle Consultant 07711 252971
<http://www.linkedin.com/in/arsharpe> <http://www.twitter.com/EgcTechnical> <https://www.facebook.com/EvergreenConsultingLtd> <http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html> <http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
<http://www.evergreen-consulting.co.uk/?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
/Your Plugged-in Partner/
Evergreen Consulting is the trading name of Sharpe Consultants Ltd
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Robert, Thanks for the offer to help out. Perhaps you can look at it from the user’s point of view, and try to improve our documentation and approach for that? Regards, Mark.
On 3 Aug 2018, at 4:01 PM, Robert Sharpe (Electric Vehicle Consultant) <robert.sharpe@evergreen-consulting.co.uk> wrote:
Hi All,
I like where OVMS project is going and would like to help if I can.
Where I can possibly add value is make things easy for people to use (eg documentation, etc) experienced on UI/UX design, etc. as an ex developer, good at testing and finding problems. Some initial thoughts on activities are to make it easier for non technical people to use OVMS, help doc author pull out user only specific content to a user manual and make it non-technical (renaming current user manual to developers manual) to help people see roadmap, provide a mechanism to see who wants what and who is working on it. to allow developers and users to display problems with their vehicle only, add Labels to the github issues list or group by project (I am not an expert on GITHUB so please be patient) update GITHUB readmes to better direct people that find GITHUB first. Please let me know if anyone is dealing with any of these areas add and/or vote for what things you think I can help with by putting a comment next to the activity above. Regards, Robert Sharpe Electric Vehicle Consultant 07711 252971
<1.gif> <http://www.linkedin.com/in/arsharpe> <2.gif> <http://www.twitter.com/EgcTechnical> <3.gif> <https://www.facebook.com/EvergreenConsultingLtd> <4.gif> <http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html> <5.gif> <http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email> <6.png> <http://www.evergreen-consulting.co.uk/?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email> Your Plugged-in Partner
Evergreen Consulting is the trading name of Sharpe Consultants Ltd
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Hi Mark, Yep - will do. Here is an update on current progress. The User Manual has been modified as follows some typos have been corrected immediately quite a view Google doc "Suggestions" have been added so that need reviewing Simplified terminology/layout to make easier to read/use Identified potential TODOs as comments (which will be pulled out later to a roadmap) Added vehicle commands section Created standard vehicle specific template Do you want to review changes before they are made public? If so can you accept or comment on my changes. If not let me know There are a number of questions added as comments that I cant answer. Next step is put a list of tasks together. Hope this helps. Rob --- On Tue, 07 Aug 2018 03:30:33 +0100 Mark Webb-Johnson <mark@webb-johnson.net> wrote ---- Robert, Thanks for the offer to help out. Perhaps you can look at it from the user’s point of view, and try to improve our documentation and approach for that? Regards, Mark. On 3 Aug 2018, at 4:01 PM, Robert Sharpe (Electric Vehicle Consultant) <robert.sharpe@evergreen-consulting.co.uk> wrote: Hi All, I like where OVMS project is going and would like to help if I can. Where I can possibly add value is make things easy for people to use (eg documentation, etc) experienced on UI/UX design, etc. as an ex developer, good at testing and finding problems. Some initial thoughts on activities are to make it easier for non technical people to use OVMS, help doc author pull out user only specific content to a user manual and make it non-technical (renaming current user manual to developers manual) to help people see roadmap, provide a mechanism to see who wants what and who is working on it. to allow developers and users to display problems with their vehicle only, add Labels to the github issues list or group by project (I am not an expert on GITHUB so please be patient) update GITHUB readmes to better direct people that find GITHUB first. Please let me know if anyone is dealing with any of these areas add and/or vote for what things you think I can help with by putting a comment next to the activity above. Regards, Robert Sharpe Electric Vehicle Consultant 07711 252971 <1.gif> <2.gif> <3.gif> <4.gif> <5.gif> <6.png> Your Plugged-in Partner Evergreen Consulting is the trading name of Sharpe Consultants Ltd _______________________________________________ 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
Robert, I've answered some of your questions, others need specific responses from the developer in charge. Most of your changes are OK, I think you can directly change the document when you're sure about a topic. I've changed the command descriptions according to your suggestion. I'm not so sure about using "Access point name" instead of "SSID", I think SSID is perfectly OK. Regards, Michael Am 07.08.2018 um 10:27 schrieb Robert Sharpe (Electric Vehicle Consultant):
Hi Mark,
Yep - will do.
Here is an update on current progress. The User Manual has been modified as follows
* some typos have been corrected immediately * quite a view Google doc "Suggestions" have been added so that need reviewing o Simplified terminology/layout to make easier to read/use o Identified potential TODOs as comments (which will be pulled out later to a roadmap) o Added vehicle commands section o Created standard vehicle specific template
*Do you want to review changes before they are made public?*
* If so can you accept or comment on my changes. * If not let me know
*There are a number of questions added as comments that I cant answer.*
Next step is put a list of tasks together.
Hope this helps.
Rob
--- On Tue, 07 Aug 2018 03:30:33 +0100 *Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>>* wrote ----
Robert,
Thanks for the offer to help out.
Perhaps you can look at it from the user’s point of view, and try to improve our documentation and approach for that?
Regards, Mark.
On 3 Aug 2018, at 4:01 PM, Robert Sharpe (Electric Vehicle Consultant) <robert.sharpe@evergreen-consulting.co.uk <mailto:robert.sharpe@evergreen-consulting.co.uk>> wrote:
Hi All,
I like where OVMS project is going and would like to help if I can.
Where I can possibly add value is
* make things easy for people to use (eg documentation, etc) * experienced on UI/UX design, etc. * as an ex developer, good at testing and finding problems.
Some initial thoughts on activities are
* to make it easier for non technical people to use OVMS, help doc author pull out user only specific content to a user manual and make it non-technical (renaming current user manual to developers manual) * to help people see roadmap, provide a mechanism to see who wants what and who is working on it. * to allow developers and users to display problems with their vehicle only, add Labels to the github issues list or group by project (I am not an expert on GITHUB so please be patient) * update GITHUB readmes to better direct people that find GITHUB first.
Please
* let me know if anyone is dealing with any of these areas * add and/or vote for what things you think I can help with by putting a comment next to the activity above.
Regards, Robert Sharpe Electric Vehicle Consultant 07711 252971
<1.gif> <http://www.linkedin.com/in/arsharpe> <2.gif> <http://www.twitter.com/EgcTechnical> <3.gif> <https://www.facebook.com/EvergreenConsultingLtd> <4.gif> <http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html> <5.gif> <http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
<6.png> <http://www.evergreen-consulting.co.uk/?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
/Your Plugged-in Partner/
Evergreen Consulting is the trading name of Sharpe Consultants Ltd
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto: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
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Hi, Mark has asked me to improve documentation from the user's point of view and I am stuck on some Leaf and ACC points that I am hoping people can help with. 1) Leaf questions 1.1) Does the TCU still need to be disconnected for Gen 2 cars to enable remote access? 1.2) Has anyone used or tested charge start/stop on a Nissan Leaf? Someone made a comment about needing to use the CAN Write feature of v3 to start-stop charging and cant find reference. 2) ACC features 2.1) Is the following documentation relevant to current version OVMS ACC Configuration (Tesla Motors Club, Oct 2017) - is this valid for non-Tesla cars? v2.5.5 firmware (2013) - is this still valid? 2.2) Where is the source code for ACC? I cant find "CHARGEBY" in any github repos. 2.3) Can someone send the help output for ACC Thanks, Rob _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev Robert, Thanks for the offer to help out. Perhaps you can look at it from the user’s point of view, and try to improve our documentation and approach for that? Regards, Mark. On 3 Aug 2018, at 4:01 PM, Robert Sharpe (Electric Vehicle Consultant) <robert.sharpe@evergreen-consulting.co.uk> wrote: Hi All, I like where OVMS project is going and would like to help if I can. Where I can possibly add value is make things easy for people to use (eg documentation, etc) experienced on UI/UX design, etc. as an ex developer, good at testing and finding problems. Some initial thoughts on activities are to make it easier for non technical people to use OVMS, help doc author pull out user only specific content to a user manual and make it non-technical (renaming current user manual to developers manual) to help people see roadmap, provide a mechanism to see who wants what and who is working on it. to allow developers and users to display problems with their vehicle only, add Labels to the github issues list or group by project (I am not an expert on GITHUB so please be patient) update GITHUB readmes to better direct people that find GITHUB first. Please let me know if anyone is dealing with any of these areas add and/or vote for what things you think I can help with by putting a comment next to the activity above. Regards, Robert Sharpe Electric Vehicle Consultant 07711 252971 <1.gif> <2.gif> <3.gif> <4.gif> <5.gif> <6.png> Your Plugged-in Partner Evergreen Consulting is the trading name of Sharpe Consultants Ltd _______________________________________________ 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
Hi Rob On 3/01/19 5:14 AM, Robert Sharpe (Electric Vehicle Consultant) wrote:
Mark has asked me to improve documentation from the user's point of view and I am stuck on some Leaf and ACC points that I am hoping people can help with.
1) Leaf questions 1.1) Does the TCU still need to be disconnected for Gen 2 cars to enable remote access?
Yes. After the OVMS wakes the car up, the TCU puts the car back to sleep if it is connected. As far as I know this is true for all models 2011-2017. In 2016 & 2017 model year cars with a TCU, the hands-free bluetooth microphone is routed through the TCU, so you can't unplug the TCU without breaking bluetooth hands free calling. I haven't explored a workaround beyond staring at the wiring diagram. I have read that if you try longer and harder you can win the fight with the TCU but I haven't tried this.
1.2) Has anyone used or tested charge start/stop on a Nissan Leaf? Someone made a comment about needing to use the CAN Write feature of v3 to start-stop charging and cant find reference.
There is no CAN write configuration in the v3, CAN write is always enabled and hence you don't need to enable it.
Hi, Tom - thanks for clarification of Leaf operation Has anyone got any thoughts on ACC feature documentation? 2) ACC features 2.1) Is the following documentation relevant to current version OVMS ACC Configuration (Tesla Motors Club, Oct 2017) - is this valid for non-Tesla cars? v2.5.5 firmware (2013) - is this still valid? 2.2) Where is the source code for ACC? I cant find "CHARGEBY" references in github. 2.3) Can someone help with ACC help text? Thanks, Rob --- On Thu, 03 Jan 2019 09:28:51 +0000 Tom Parker <tom@carrott.org> wrote ---- Hi Rob On 3/01/19 5:14 AM, Robert Sharpe (Electric Vehicle Consultant) wrote: Mark has asked me to improve documentation from the user's point of view and I am stuck on some Leaf and ACC points that I am hoping people can help with. 1) Leaf questions 1.1) Does the TCU still need to be disconnected for Gen 2 cars to enable remote access? Yes. After the OVMS wakes the car up, the TCU puts the car back to sleep if it is connected. As far as I know this is true for all models 2011-2017. In 2016 & 2017 model year cars with a TCU, the hands-free bluetooth microphone is routed through the TCU, so you can't unplug the TCU without breaking bluetooth hands free calling. I haven't explored a workaround beyond staring at the wiring diagram. I have read that if you try longer and harder you can win the fight with the TCU but I haven't tried this. 1.2) Has anyone used or tested charge start/stop on a Nissan Leaf? Someone made a comment about needing to use the CAN Write feature of v3 to start-stop charging and cant find reference. There is no CAN write configuration in the v3, CAN write is always enabled and hence you don't need to enable it. --- On Wed, 02 Jan 2019 16:14:34 +0000 Robert Sharpe (Electric Vehicle Consultant) <robert.sharpe@evergreen-consulting.co.uk> wrote ---- Hi, Mark has asked me to improve documentation from the user's point of view and I am stuck on some Leaf and ACC points that I am hoping people can help with. 1) Leaf questions 1.1) Does the TCU still need to be disconnected for Gen 2 cars to enable remote access? 1.2) Has anyone used or tested charge start/stop on a Nissan Leaf? Someone made a comment about needing to use the CAN Write feature of v3 to start-stop charging and cant find reference. 2) ACC features 2.1) Is the following documentation relevant to current version OVMS ACC Configuration (Tesla Motors Club, Oct 2017) - is this valid for non-Tesla cars? v2.5.5 firmware (2013) - is this still valid? 2.2) Where is the source code for ACC? I cant find "CHARGEBY" in any github repos. 2.3) Can someone send the help output for ACC Thanks, Rob
On Thu, 3 Jan 2019, Robert Sharpe (Electric Vehicle Consultant) wrote:
Has anyone got any thoughts on ACC feature documentation?
The ACC feature does not exist (yet) in OVMSv3. Mark has said that it should be possible to write scripts to perform the same functions, so I started out to do that and discovered that there are some required pieces still missing.
2) ACC features 2.1) Is the following documentation relevant to current version OVMS ACC Configuration (Tesla Motors Club, Oct 2017) - is this valid for non-Tesla cars?
I don't know. I didn't have OVMSv2 and so never used ACC.
v2.5.5 firmware (2013) - is this still valid?
That version number was for OVMSv2. OVMSv3 has completely different firmware and a new version sequence.
2.2) Where is the source code for ACC? I cant find "CHARGEBY" references in github.
Does not exist.
2.3) Can someone help with ACC help text?
Waiting for a couple of things Mark said he was working on. -- Steve
Hi, Re: Documentation usability review. I cant find any documentation on the scripting that was mentioned in either the user or development manual or the github. Can anyone point me to more information on this feature. Rob --- On Thu, 03 Jan 2019 17:39:31 +0000 Stephen Casner <mailto:casner@acm.org> wrote ---- On Thu, 3 Jan 2019, Robert Sharpe (Electric Vehicle Consultant) wrote:
Has anyone got any thoughts on ACC feature documentation?
The ACC feature does not exist (yet) in OVMSv3. Mark has said that it should be possible to write scripts to perform the same functions, so I started out to do that and discovered that there are some required pieces still missing.
2) ACC features
2.1) Is the following documentation relevant to current version
OVMS ACC Configuration (Tesla Motors Club, Oct 2017) - is this valid
for non-Tesla cars?
I don't know. I didn't have OVMSv2 and so never used ACC.
v2.5.5 firmware (2013) - is this still valid?
That version number was for OVMSv2. OVMSv3 has completely different firmware and a new version sequence.
2.2) Where is the source code for ACC?
I cant find "CHARGEBY" references in github.
Does not exist.
2.3) Can someone help with ACC help text?
Waiting for a couple of things Mark said he was working on. -- Steve_______________________________________________ OvmsDev mailing list mailto:OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Rob, The archive of this email list is the only documentation I know about. -- Steve On Sun, 6 Jan 2019, Robert Sharpe (Electric Vehicle Consultant) wrote:
Hi,
Re: Documentation usability review.
I cant find any documentation on the scripting that was mentioned in either the user or development manual or the github. Can anyone point me to more information on this feature.
Rob
--- On Thu, 03 Jan 2019 17:39:31 +0000 Stephen Casner <mailto:casner@acm.org> wrote ----
On Thu, 3 Jan 2019, Robert Sharpe (Electric Vehicle Consultant) wrote:
Has anyone got any thoughts on ACC feature documentation?
The ACC feature does not exist (yet) in OVMSv3. Mark has said that it
should be possible to write scripts to perform the same functions, so
I started out to do that and discovered that there are some required
pieces still missing.
2) ACC features
2.1) Is the following documentation relevant to current version
OVMS ACC Configuration (Tesla Motors Club, Oct 2017) - is this valid
for non-Tesla cars?
I don't know. I didn't have OVMSv2 and so never used ACC.
v2.5.5 firmware (2013) - is this still valid?
That version number was for OVMSv2. OVMSv3 has completely different
firmware and a new version sequence.
2.2) Where is the source code for ACC?
I cant find "CHARGEBY" references in github.
Does not exist.
2.3) Can someone help with ACC help text?
Waiting for a couple of things Mark said he was working on.
-- Steve_______________________________________________
OvmsDev mailing list
mailto:OvmsDev@lists.openvehicles.com
Thanks, unfortunately it looks like the http://lists.openvehicles.com/pipermail/ovmsdev/ doesn't seem to be any search facility so it is not going to be feasible to go through all the email manually. So it looks like I will have to wait until someone can point me to the appropriate email. Rob --- On Sun, 06 Jan 2019 17:09:02 +0000 Stephen Casner <mailto:casner@acm.org> wrote ---- Rob, The archive of this email list is the only documentation I know about. -- Steve On Sun, 6 Jan 2019, Robert Sharpe (Electric Vehicle Consultant) wrote:
Hi,
Re: Documentation usability review.
I cant find any documentation on the scripting that was mentioned in either the user or development manual or the github. Can anyone point me to more information on this feature.
Rob
--- On Thu, 03 Jan 2019 17:39:31 +0000 Stephen Casner <mailto:mailto:casner@acm.org> wrote ----
On Thu, 3 Jan 2019, Robert Sharpe (Electric Vehicle Consultant) wrote:
Has anyone got any thoughts on ACC feature documentation?
The ACC feature does not exist (yet) in OVMSv3. Mark has said that it
should be possible to write scripts to perform the same functions, so
I started out to do that and discovered that there are some required
pieces still missing.
2) ACC features
2.1) Is the following documentation relevant to current version
OVMS ACC Configuration (Tesla Motors Club, Oct 2017) - is this valid
for non-Tesla cars?
I don't know. I didn't have OVMSv2 and so never used ACC.
v2.5.5 firmware (2013) - is this still valid?
That version number was for OVMSv2. OVMSv3 has completely different
firmware and a new version sequence.
2.2) Where is the source code for ACC?
I cant find "CHARGEBY" references in github.
Does not exist.
2.3) Can someone help with ACC help text?
Waiting for a couple of things Mark said he was working on.
-- Steve_______________________________________________
OvmsDev mailing list
mailto:mailto:OvmsDev@lists.openvehicles.com
On Sun, 6 Jan 2019, Robert Sharpe (Electric Vehicle Consultant) wrote:
Thanks, unfortunately it looks like the http://lists.openvehicles.com/pipermail/ovmsdev/ doesn't seem to be any search facility so it is not going to be feasible to go through all the email manually.
Try going to google.com and entering this: site:lists.openvehicles.com script -- Steve
Hi Steve, Thanks. Unfortunately, it hasn't been indexed since Mar 2018 and I don't have access to the webmasters console. Could the domain owner please reindex the archives since Mar 2018 with Google? Rob --- On Sun, 06 Jan 2019 18:28:32 +0000 Stephen Casner <mailto:casner@acm.org> wrote ---- On Sun, 6 Jan 2019, Robert Sharpe (Electric Vehicle Consultant) wrote:
Thanks, unfortunately it looks like the
http://lists.openvehicles.com/pipermail/ovmsdev/ doesn't seem to be
any search facility so it is not going to be feasible to go through
all the email manually.
Try going to google.com and entering this: site:lists.openvehicles.com script -- Steve _______________________________________________ OvmsDev mailing list mailto:OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Hi Mark/All, Sometime ago I did lots of obvious updates of the User Manual to help readability, etc as a first stab. Now doing a second stab, there is one thing that has come to light and that is the definition of a user. In order to check the documentation I need to know what the user is capable of off. I appreciate that the definition of user has probably changed over the development of the project and the product has matured enough that it can be operated by non-technical users opening up its usefulness. Assuming that what were the original users would how fall into the category of Developers, does the following draft specification accurately reflect the minimum capabilities of a current/future User? User Definition a general household DIY capable person. can mount and plug things into the vehicle cant create connectors/leads modify the OVMS hardware don't know about internal or technical terms, such as Nissan Leaf GIDs, WiFi SSID, etc User Expectations the unit fully supports the listed features under all reasonable conditions reliable in operation error messages are non-technical and help the user solve the problem should be plug-n-play where possible, eg automatically detects vehicle type and year automatically detects battery capacity, etc Please let me know if this is accurate or what changes/clarifications need to be made. Rob --- On Tue, 07 Aug 2018 03:30:33 +0100 Mark Webb-Johnson <mark@webb-johnson.net> wrote ---- Robert, Thanks for the offer to help out. Perhaps you can look at it from the user’s point of view, and try to improve our documentation and approach for that? Regards, Mark. On 3 Aug 2018, at 4:01 PM, Robert Sharpe (Electric Vehicle Consultant) <robert.sharpe@evergreen-consulting.co.uk> wrote: Hi All, I like where OVMS project is going and would like to help if I can. Where I can possibly add value is make things easy for people to use (eg documentation, etc) experienced on UI/UX design, etc. as an ex developer, good at testing and finding problems. Some initial thoughts on activities are to make it easier for non technical people to use OVMS, help doc author pull out user only specific content to a user manual and make it non-technical (renaming current user manual to developers manual) to help people see roadmap, provide a mechanism to see who wants what and who is working on it. to allow developers and users to display problems with their vehicle only, add Labels to the github issues list or group by project (I am not an expert on GITHUB so please be patient) update GITHUB readmes to better direct people that find GITHUB first. Please let me know if anyone is dealing with any of these areas add and/or vote for what things you think I can help with by putting a comment next to the activity above. Regards, Robert Sharpe Electric Vehicle Consultant 07711 252971 <1.gif> <2.gif> <3.gif> <4.gif> <5.gif> <6.png> Your Plugged-in Partner Evergreen Consulting is the trading name of Sharpe Consultants Ltd _______________________________________________ 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
Rob, maybe I'm too pessimistic (realistic?), but if you're targeting users within that category, your spec lacks "doesn't like reading manuals or searching the web for answers" and "likes watching short videos", so working on the manual with these users in mind is futile. My last App support: the App told the user it can't connect to the server, he should verify the server address and vehicle ID. I sent him the data he should use. He insisted in having entered exactly that. After four or five mails I finally got him to send me this "screenshot": Many current users (even v2 users) I have supported fit into that category, none of them would (could) read anything longer than a few sentences. The manual introduction section is already too much for them, they normally just jump into using the system and they normally fail at things like entering a server name or password correctly. Of course we should generally try to further simplify the UIs, e.g. provide a select option for the standard servers and an account registration API. But the manual IMO is meant for the capable / advanced user trying to get specific jobs done with the system. For the "low end" user target, a single (!) page "first setup" sheet is needed, and a series of 3 minute feature introduction videos on Youtube. Regards, Michael Am 03.01.19 um 16:05 schrieb Robert Sharpe (Electric Vehicle Consultant):
Hi Mark/All,
Sometime ago I did lots of obvious updates of the User Manual to help readability, etc as a first stab.
Now doing a second stab, there is one thing that has come to light and that is the definition of a user.
In order to check the documentation I need to know what the user is capable of off. I appreciate that the definition of user has probably changed over the development of the project and the product has matured enough that it can be operated by non-technical users opening up its usefulness.
Assuming that what were the original users would how fall into the category of Developers, does the following draft specification accurately reflect the minimum capabilities of a current/future User?
User Definition
* a general household DIY capable person. * can mount and plug things into the vehicle * cant o create connectors/leads o modify the OVMS hardware o don't know about internal or technical terms, such as Nissan Leaf GIDs, WiFi SSID, etc
User Expectations
* the unit fully supports the listed features under all reasonable conditions * reliable in operation * error messages are non-technical and help the user solve the problem * should be plug-n-play where possible, eg o automatically detects vehicle type and year o automatically detects battery capacity, etc
Please let me know if this is accurate or what changes/clarifications need to be made.
Rob
--- On Tue, 07 Aug 2018 03:30:33 +0100 *Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>>* wrote ----
Robert,
Thanks for the offer to help out.
Perhaps you can look at it from the user’s point of view, and try to improve our documentation and approach for that?
Regards, Mark.
On 3 Aug 2018, at 4:01 PM, Robert Sharpe (Electric Vehicle Consultant) <robert.sharpe@evergreen-consulting.co.uk <mailto:robert.sharpe@evergreen-consulting.co.uk>> wrote:
Hi All,
I like where OVMS project is going and would like to help if I can.
Where I can possibly add value is
* make things easy for people to use (eg documentation, etc) * experienced on UI/UX design, etc. * as an ex developer, good at testing and finding problems.
Some initial thoughts on activities are
* to make it easier for non technical people to use OVMS, help doc author pull out user only specific content to a user manual and make it non-technical (renaming current user manual to developers manual) * to help people see roadmap, provide a mechanism to see who wants what and who is working on it. * to allow developers and users to display problems with their vehicle only, add Labels to the github issues list or group by project (I am not an expert on GITHUB so please be patient) * update GITHUB readmes to better direct people that find GITHUB first.
Please
* let me know if anyone is dealing with any of these areas * add and/or vote for what things you think I can help with by putting a comment next to the activity above.
Regards, Robert Sharpe Electric Vehicle Consultant 07711 252971
<1.gif> <http://www.linkedin.com/in/arsharpe> <2.gif> <http://www.twitter.com/EgcTechnical> <3.gif> <https://www.facebook.com/EvergreenConsultingLtd> <4.gif> <http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html> <5.gif> <http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
<6.png> <http://www.evergreen-consulting.co.uk/?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
/Your Plugged-in Partner/
Evergreen Consulting is the trading name of Sharpe Consultants Ltd
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto: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
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Hi Michael, Thanks for your excellent points. In terms of suggested actions does the following accurately summarise your thoughts (with redline changes) summary? User Definition a general household DIY capable person. can mount and plug things into the vehicle will only read a single quick install sheet a list of text commands maybe 3 min youTube videos cant create connectors/leads modify the OVMS hardware don't know about internal or technical terms, such as Nissan Leaf GIDs, WiFi SSID, etc User Expectations the unit fully supports the listed features under all reasonable conditions reliable in operation error messages are non-technical and help the user solve the problem should be plug-n-play where possible, eg automatically detects vehicle type and year automatically detects battery capacity, etc Rename User Manual to "Advanced User Manual" Advanced User Definition can create connectors/leads modify the OVMS hardware (eg add wake-up hardware) modifying car at module level (eg remove TCU on Leaf) knows internal or technical terms, such as Nissan Leaf GIDs, WiFi SSID, etc Advanced User Expectations to easily access detailed reasons why a feature doesn't work and possible workarounds Rob --- On Fri, 04 Jan 2019 14:13:43 +0000 Michael Balzer <mailto:dexter@expeedo.de> wrote ---- Rob, maybe I'm too pessimistic (realistic?), but if you're targeting users within that category, your spec lacks "doesn't like reading manuals or searching the web for answers" and "likes watching short videos", so working on the manual with these users in mind is futile. My last App support: the App told the user it can't connect to the server, he should verify the server address and vehicle ID. I sent him the data he should use. He insisted in having entered exactly that. After four or five mails I finally got him to send me this "screenshot": Many current users (even v2 users) I have supported fit into that category, none of them would (could) read anything longer than a few sentences. The manual introduction section is already too much for them, they normally just jump into using the system and they normally fail at things like entering a server name or password correctly. Of course we should generally try to further simplify the UIs, e.g. provide a select option for the standard servers and an account registration API. But the manual IMO is meant for the capable / advanced user trying to get specific jobs done with the system. For the "low end" user target, a single (!) page "first setup" sheet is needed, and a series of 3 minute feature introduction videos on Youtube. Regards, Michael Am 03.01.19 um 16:05 schrieb Robert Sharpe (Electric Vehicle Consultant): -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list mailto:OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev Hi Mark/All, Sometime ago I did lots of obvious updates of the User Manual to help readability, etc as a first stab. Now doing a second stab, there is one thing that has come to light and that is the definition of a user. In order to check the documentation I need to know what the user is capable of off. I appreciate that the definition of user has probably changed over the development of the project and the product has matured enough that it can be operated by non-technical users opening up its usefulness. Assuming that what were the original users would how fall into the category of Developers, does the following draft specification accurately reflect the minimum capabilities of a current/future User? User Definition a general household DIY capable person. can mount and plug things into the vehicle cant create connectors/leads modify the OVMS hardware don't know about internal or technical terms, such as Nissan Leaf GIDs, WiFi SSID, etc User Expectations the unit fully supports the listed features under all reasonable conditions reliable in operation error messages are non-technical and help the user solve the problem should be plug-n-play where possible, eg automatically detects vehicle type and year automatically detects battery capacity, etc Please let me know if this is accurate or what changes/clarifications need to be made. Rob --- On Tue, 07 Aug 2018 03:30:33 +0100 Mark Webb-Johnson <mailto:mark@webb-johnson.net> wrote ---- Robert, Thanks for the offer to help out. Perhaps you can look at it from the user’s point of view, and try to improve our documentation and approach for that? Regards, Mark. On 3 Aug 2018, at 4:01 PM, Robert Sharpe (Electric Vehicle Consultant) <mailto:robert.sharpe@evergreen-consulting.co.uk> wrote: Hi All, I like where OVMS project is going and would like to help if I can. Where I can possibly add value is make things easy for people to use (eg documentation, etc) experienced on UI/UX design, etc. as an ex developer, good at testing and finding problems. Some initial thoughts on activities are to make it easier for non technical people to use OVMS, help doc author pull out user only specific content to a user manual and make it non-technical (renaming current user manual to developers manual) to help people see roadmap, provide a mechanism to see who wants what and who is working on it. to allow developers and users to display problems with their vehicle only, add Labels to the github issues list or group by project (I am not an expert on GITHUB so please be patient) update GITHUB readmes to better direct people that find GITHUB first. Please let me know if anyone is dealing with any of these areas add and/or vote for what things you think I can help with by putting a comment next to the activity above. Regards, Robert Sharpe Electric Vehicle Consultant 07711 252971 http://www.linkedin.com/in/arsharpe http://www.twitter.com/EgcTechnical https://www.facebook.com/EvergreenConsultingLtd http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campa... http://www.evergreen-consulting.co.uk/?utm_campaign=General&utm_source=Email... Your Plugged-in Partner Evergreen Consulting is the trading name of Sharpe Consultants Ltd _______________________________________________ OvmsDev mailing list mailto:OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list mailto:OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list mailto:OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
I think the advanced user definition maybe too restrictive. Our current user base is perhaps best described as: A science-based hobbyist (electronics, computers, etc) Able to work with computers and electronics Understands the core underlying technology A not-so-capable user can still use our system, but requires someone with the above capabilities to help setup and provide local support. Regards, Mark.
On 5 Jan 2019, at 2:05 AM, Robert Sharpe (Electric Vehicle Consultant) <robert.sharpe@evergreen-consulting.co.uk> wrote:
Hi Michael,
Thanks for your excellent points.
In terms of suggested actions does the following accurately summarise your thoughts (with redline changes) summary?
User Definition a general household DIY capable person. can mount and plug things into the vehicle will only read a single quick install sheet a list of text commands maybe 3 min youTube videos cant create connectors/leads modify the OVMS hardware don't know about internal or technical terms, such as Nissan Leaf GIDs, WiFi SSID, etc User Expectations the unit fully supports the listed features under all reasonable conditions reliable in operation error messages are non-technical and help the user solve the problem should be plug-n-play where possible, eg automatically detects vehicle type and year automatically detects battery capacity, etc Rename User Manual to "Advanced User Manual"
Advanced User Definition can create connectors/leads modify the OVMS hardware (eg add wake-up hardware) modifying car at module level (eg remove TCU on Leaf) knows internal or technical terms, such as Nissan Leaf GIDs, WiFi SSID, etc Advanced User Expectations to easily access detailed reasons why a feature doesn't work and possible workarounds
Rob
--- On Fri, 04 Jan 2019 14:13:43 +0000 Michael Balzer <dexter@expeedo.de <mailto:dexter@expeedo.de>> wrote ----
Rob,
maybe I'm too pessimistic (realistic?), but if you're targeting users within that category, your spec lacks "doesn't like reading manuals or searching the web for answers" and "likes watching short videos", so working on the manual with these users in mind is futile.
My last App support: the App told the user it can't connect to the server, he should verify the server address and vehicle ID. I sent him the data he should use. He insisted in having entered exactly that. After four or five mails I finally got him to send me this "screenshot":
<1.jpg>
Many current users (even v2 users) I have supported fit into that category, none of them would (could) read anything longer than a few sentences. The manual introduction section is already too much for them, they normally just jump into using the system and they normally fail at things like entering a server name or password correctly.
Of course we should generally try to further simplify the UIs, e.g. provide a select option for the standard servers and an account registration API.
But the manual IMO is meant for the capable / advanced user trying to get specific jobs done with the system.
For the "low end" user target, a single (!) page "first setup" sheet is needed, and a series of 3 minute feature introduction videos on Youtube.
Regards, Michael
Am 03.01.19 um 16:05 schrieb Robert Sharpe (Electric Vehicle Consultant):
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev> Hi Mark/All,
Sometime ago I did lots of obvious updates of the User Manual to help readability, etc as a first stab.
Now doing a second stab, there is one thing that has come to light and that is the definition of a user.
In order to check the documentation I need to know what the user is capable of off. I appreciate that the definition of user has probably changed over the development of the project and the product has matured enough that it can be operated by non-technical users opening up its usefulness.
Assuming that what were the original users would how fall into the category of Developers, does the following draft specification accurately reflect the minimum capabilities of a current/future User?
User Definition a general household DIY capable person. can mount and plug things into the vehicle cant create connectors/leads modify the OVMS hardware don't know about internal or technical terms, such as Nissan Leaf GIDs, WiFi SSID, etc User Expectations the unit fully supports the listed features under all reasonable conditions reliable in operation error messages are non-technical and help the user solve the problem should be plug-n-play where possible, eg automatically detects vehicle type and year automatically detects battery capacity, etc Please let me know if this is accurate or what changes/clarifications need to be made.
Rob
--- On Tue, 07 Aug 2018 03:30:33 +0100 Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>> wrote ----
Robert,
Thanks for the offer to help out.
Perhaps you can look at it from the user’s point of view, and try to improve our documentation and approach for that?
Regards, Mark.
On 3 Aug 2018, at 4:01 PM, Robert Sharpe (Electric Vehicle Consultant) <robert.sharpe@evergreen-consulting.co.uk <mailto:robert.sharpe@evergreen-consulting.co.uk>> wrote:
Hi All,
I like where OVMS project is going and would like to help if I can.
Where I can possibly add value is make things easy for people to use (eg documentation, etc) experienced on UI/UX design, etc. as an ex developer, good at testing and finding problems. Some initial thoughts on activities are to make it easier for non technical people to use OVMS, help doc author pull out user only specific content to a user manual and make it non-technical (renaming current user manual to developers manual) to help people see roadmap, provide a mechanism to see who wants what and who is working on it. to allow developers and users to display problems with their vehicle only, add Labels to the github issues list or group by project (I am not an expert on GITHUB so please be patient) update GITHUB readmes to better direct people that find GITHUB first. Please let me know if anyone is dealing with any of these areas add and/or vote for what things you think I can help with by putting a comment next to the activity above. Regards, Robert Sharpe Electric Vehicle Consultant 07711 252971
<1.gif> <http://www.linkedin.com/in/arsharpe> <2.gif> <http://www.twitter.com/EgcTechnical> <3.gif> <https://www.facebook.com/EvergreenConsultingLtd> <4.gif> <http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html> <5.gif> <http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email> <6.png> <http://www.evergreen-consulting.co.uk/?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email> Your Plugged-in Partner
Evergreen Consulting is the trading name of Sharpe Consultants Ltd
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
I agree 100% with Michael here. Far too much time is spent hand-holding very inexperienced users, and it is incredibly frustrating. About half of the people who ask me for help turn out to have a simple typo in the username / password. Half the remaining have a more complicated typo. Perhaps when the v3 product has matured some, we can look at how to look after more novice users, but for the moment I think we should keep the material targeted to experienced users. I.T. literate. Regards, Mark.
On 4 Jan 2019, at 10:13 PM, Michael Balzer <dexter@expeedo.de> wrote:
Rob,
maybe I'm too pessimistic (realistic?), but if you're targeting users within that category, your spec lacks "doesn't like reading manuals or searching the web for answers" and "likes watching short videos", so working on the manual with these users in mind is futile.
My last App support: the App told the user it can't connect to the server, he should verify the server address and vehicle ID. I sent him the data he should use. He insisted in having entered exactly that. After four or five mails I finally got him to send me this "screenshot":
<glkolgejahicndjc.jpeg>
Many current users (even v2 users) I have supported fit into that category, none of them would (could) read anything longer than a few sentences. The manual introduction section is already too much for them, they normally just jump into using the system and they normally fail at things like entering a server name or password correctly.
Of course we should generally try to further simplify the UIs, e.g. provide a select option for the standard servers and an account registration API.
But the manual IMO is meant for the capable / advanced user trying to get specific jobs done with the system.
For the "low end" user target, a single (!) page "first setup" sheet is needed, and a series of 3 minute feature introduction videos on Youtube.
Regards, Michael
Am 03.01.19 um 16:05 schrieb Robert Sharpe (Electric Vehicle Consultant):
Hi Mark/All,
Sometime ago I did lots of obvious updates of the User Manual to help readability, etc as a first stab.
Now doing a second stab, there is one thing that has come to light and that is the definition of a user.
In order to check the documentation I need to know what the user is capable of off. I appreciate that the definition of user has probably changed over the development of the project and the product has matured enough that it can be operated by non-technical users opening up its usefulness.
Assuming that what were the original users would how fall into the category of Developers, does the following draft specification accurately reflect the minimum capabilities of a current/future User?
User Definition a general household DIY capable person. can mount and plug things into the vehicle cant create connectors/leads modify the OVMS hardware don't know about internal or technical terms, such as Nissan Leaf GIDs, WiFi SSID, etc User Expectations the unit fully supports the listed features under all reasonable conditions reliable in operation error messages are non-technical and help the user solve the problem should be plug-n-play where possible, eg automatically detects vehicle type and year automatically detects battery capacity, etc Please let me know if this is accurate or what changes/clarifications need to be made.
Rob
--- On Tue, 07 Aug 2018 03:30:33 +0100 Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>> wrote ----
Robert,
Thanks for the offer to help out.
Perhaps you can look at it from the user’s point of view, and try to improve our documentation and approach for that?
Regards, Mark.
On 3 Aug 2018, at 4:01 PM, Robert Sharpe (Electric Vehicle Consultant) <robert.sharpe@evergreen-consulting.co.uk <mailto:robert.sharpe@evergreen-consulting.co.uk>> wrote:
Hi All,
I like where OVMS project is going and would like to help if I can.
Where I can possibly add value is make things easy for people to use (eg documentation, etc) experienced on UI/UX design, etc. as an ex developer, good at testing and finding problems. Some initial thoughts on activities are to make it easier for non technical people to use OVMS, help doc author pull out user only specific content to a user manual and make it non-technical (renaming current user manual to developers manual) to help people see roadmap, provide a mechanism to see who wants what and who is working on it. to allow developers and users to display problems with their vehicle only, add Labels to the github issues list or group by project (I am not an expert on GITHUB so please be patient) update GITHUB readmes to better direct people that find GITHUB first. Please let me know if anyone is dealing with any of these areas add and/or vote for what things you think I can help with by putting a comment next to the activity above. Regards, Robert Sharpe Electric Vehicle Consultant 07711 252971
<1.gif> <http://www.linkedin.com/in/arsharpe> <2.gif> <http://www.twitter.com/EgcTechnical> <3.gif> <https://www.facebook.com/EvergreenConsultingLtd> <4.gif> <http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html> <5.gif> <http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email> <6.png> <http://www.evergreen-consulting.co.uk/?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email> Your Plugged-in Partner
Evergreen Consulting is the trading name of Sharpe Consultants Ltd
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
participants (5)
-
Mark Webb-Johnson -
Michael Balzer -
Robert Sharpe (Electric Vehicle Consultant) -
Stephen Casner -
Tom Parker