Do you get a calculated amp-hour capacity (CAC) value on the Model S? Tom -----Original Message----- From: OvmsDev <ovmsdev-bounces@lists.openvehicles.com> on behalf of Mark Webb-Johnson <mark@webb-johnson.net> Reply-To: OVMS Developers <ovmsdev@lists.openvehicles.com> Date: Tuesday, April 10, 2018 at 1:30 AM To: Stephen & Karen Casner <casner@acm.org> Cc: OVMS Developers <ovmsdev@lists.openvehicles.com> Subject: Re: [Ovmsdev] ssh: secure mode prompt not set #31 Thanks, Steve. I will try it in a few minutes. P.S. I’m about to drive home in my Model S, with the vehicle module actually running for the first time. I’ve got speed, soc, and park/drive support working on Tesla Model S (probably) so will finally have something to see on the web dashboard. Regards, Mark. > On 10 Apr 2018, at 2:41 PM, Stephen Casner <casner@acm.org> wrote: > > Mark, > > What this really means is that my previous implementation of the > secure mode prompt was in the wrong place. I've fixed it, isolating > the setting of the prompt into OvmsShell. This removes the > SetPrompt() API from OvmsWriter, which is good, at the cost of making > SetSecure() virtual. > > -- Steve > > On Tue, 10 Apr 2018, Mark Webb-Johnson wrote: > >> >> Steve, >> >> Can you have a look at this one: >> >> https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/31 <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/31> >> >> When connecting to the box via ssh, using a trusted ssh.keys mechanism, it seems that the session is correctly put into secure mode (enable). But, the prompt is OVMS> (should be OVMS#). The full set of enable commands is shown, so pretty sure the session is in enable mode. >> >> I think the issue is purely the prompt being incorrect. >> >> I think (hope) it should be simple. >> >> Thanks, Mark. _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev