Hi all, I have managed to install 2 V.3 boxes on two Think City A306 and the basic functionality works great - I am able to see the SOC, position, battery temperature. I will be measuring power consumption and look at logging and adding more parameters in near future. I had a few wows that came from me not reading documentation and one that I could not find in the documentation. The undocumented one was that I was able to set password to "test" - it was just for testing on the bench, and I was no longer able to find the access point... when I connected via usb cable and terminal I could see that the process for the AC was complaining that the module password was too short and aborted startup. I haven't tested this in the latest update, but wanted to put it out there in case any of you run in to it. Nikolay On Thursday, July 12, 2018, 11:40:49 AM GMT+2, Mark Webb-Johnson <mark@webb-johnson.net> wrote: Just seems wasteful to have a dozen metrics for this. Expensive in ram, bandwidth, and mqtt. Every vehicle module would have to set the unused ones to ‘no’ (due to the way mqtt retained topics work). If we add a new capability, all the vehicle modules would have to be changed to set it to ’no'. Your suggestion is cleaner, but more expensive. Regards, Mark.
On 12 Jul 2018, at 5:34 PM, Robin O'Leary <ovmsdev@caederus.org> wrote:
On Thu, Jul 12, 2018 at 08:56:25AM +0800, Mark Webb-Johnson wrote:
I think the capabilities are useful, but need to be done in a better, more future-proof, way. Relying on protocol v2 commands is limited. ... My suggestion is:
Create a standard metric ‘v.capabilities’. Have the vehicle modules set that metric with their capabilities, as a comma-separated list of the commands supported:
Mapping things to strings seems rather roundabout. Would it not be better to have individual boolean capabilities?
v.capability.chargemode = yes/no ... v.capability.climate = yes/no _______________________________________________ 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
Nikolay, how did you set the password to "test"? Via the web UI? If so, on which page? You may set any (wrong) configuration by the "config set" command, that does not do any sanity checks. But the web interface should catch and prevent that mistake. Regards, Michael Am 12.07.2018 um 13:52 schrieb Nikolay Shishkov:
Hi all,
I have managed to install 2 V.3 boxes on two Think City A306 and the basic functionality works great - I am able to see the SOC, position, battery temperature. I will be measuring power consumption and look at logging and adding more parameters in near future.
I had a few wows that came from me not reading documentation and one that I could not find in the documentation. The undocumented one was that I was able to set password to "test" - it was just for testing on the bench, and I was no longer able to find the access point... when I connected via usb cable and terminal I could see that the process for the AC was complaining that the module password was too short and aborted startup. I haven't tested this in the latest update, but wanted to put it out there in case any of you run in to it.
Nikolay
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Thanks Michael, I think I set it via the web interface, but that was on a very early version - my boxes were stuck in customs for 2 months.But now, when you ask this - I may have done it via the config set... I can try replicating it again when I get my new boxes or unmount one of the existing ones. Regards,Nikolay On Thursday, July 12, 2018, 2:38:42 PM GMT+2, Michael Balzer <dexter@expeedo.de> wrote: Nikolay, how did you set the password to "test"? Via the web UI? If so, on which page? You may set any (wrong) configuration by the "config set" command, that does not do any sanity checks. But the web interface should catch and prevent that mistake. Regards, Michael Am 12.07.2018 um 13:52 schrieb Nikolay Shishkov: Hi all, I have managed to install 2 V.3 boxes on two Think City A306 and the basic functionality works great - I am able to see the SOC, position, battery temperature. I will be measuring power consumption and look at logging and adding more parameters in near future. I had a few wows that came from me not reading documentation and one that I could not find in the documentation. The undocumented one was that I was able to set password to "test" - it was just for testing on the bench, and I was no longer able to find the access point... when I connected via usb cable and terminal I could see that the process for the AC was complaining that the module password was too short and aborted startup. I haven't tested this in the latest update, but wanted to put it out there in case any of you run in to it. Nikolay -- 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 (2)
-
Michael Balzer -
Nikolay Shishkov