<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Julien,<br>
<br>
welcome :)<br>
<br>
<br>
<div class="moz-cite-prefix">Am 22.09.2014 um 16:55 schrieb Julien
NOZAIS:<br>
</div>
<blockquote
cite="mid:751077C3D22CF442998DE241147349338E2C29@trip.uni.lux"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
<div style="direction: ltr;font-family: Tahoma;color:
#000000;font-size: 10pt;"><font face="Arial"><b>MSG commands</b><br>
<br>
My current situation is that I have upgraded my OVMS module to
2.6.5 firmware with the .hex file provided on GitHub. I have
also successfully connected to the module via SMS commands and
Android App. Most of the basic commands that I tried worked.<br>
<br>
I say 'most', because I have set the #15 'write' bit to '1'
and cleared the #14 bit as well. However, I don't seem to be
able to send CFG commands via SMS (such as CFG SPEED
<speed> for example) in the way that the twizy manual
describes it. All I get are push notifications forwarding my
SMS to the app. Is there something I'm missing? :(<br>
</font></div>
</blockquote>
<br>
Yes. That's having read the last page of the manual and/or having
browsed through this list's archive... ;)<br>
<br>
The Github hex files are missing the SEVCON functions. You need to
download the latest hex release from the german forum or compile
yourself.<br>
<br>
To compile yourself you need to define these (and only these)
compiler flags:<br>
<br>
OVMS_CAR_NONE<br>
OVMS_CAR_RENAULTTWIZY<br>
OVMS_HW_V2<br>
OVMS_DIAGMODULE<br>
OVMS_INTERNALGPS<br>
OVMS_TWIZY_BATTMON<br>
OVMS_TWIZY_CFG<br>
<br>
...and you need to manually exclude source files "acc.c",
"logging.c" and all other "vehicle*.c" from the build, because
otherwise...<br>
<br>
<blockquote
cite="mid:751077C3D22CF442998DE241147349338E2C29@trip.uni.lux"
type="cite">
<div style="direction: ltr;font-family: Tahoma;color:
#000000;font-size: 10pt;"><font face="Arial">
<br>
<font color="808080" size="2">> Error - section
'.romdata_net_msg.o' can not fit the section. Section
'.romdata_net_msg.o' length=0x000000a8</font><br>
</font><br>
</div>
</blockquote>
... this will happen ;)<br>
<br>
Just use the context menu "properties" on the files to exclude them.<br>
<br>
<br>
<blockquote
cite="mid:751077C3D22CF442998DE241147349338E2C29@trip.uni.lux"
type="cite">
<div style="direction: ltr;font-family: Tahoma;color:
#000000;font-size: 10pt;"><font face="Arial">
<br>
<b>DIAG communication</b><br>
<br>
Probably noob error: I tried connecting through the DIAG port
with minicom. I set minicom to 9600 Bds / 8N1, as specified in
the developers documentation, but had no success. I think that
I'm closed since since I received data, but it was just
gibberish encoding errors. Since these errors are often caused
by a wrong baud setting, I tried different baud values without
success. I hope somebody can point out something that I could
have missed. I have read the manual, but, well... you never
know.<br>
</font></div>
</blockquote>
<br>
Be sure to also disable any flow control. Depending on your serial
adapter, another parameter init and/or hardware reconnect may be
necessary. Also make sure your serial device is writable by your
login, to be sure launch minicom as root.<br>
<br>
<br>
<blockquote
cite="mid:751077C3D22CF442998DE241147349338E2C29@trip.uni.lux"
type="cite">
<div style="direction: ltr;font-family: Tahoma;color:
#000000;font-size: 10pt;"><font face="Arial">
<br>
I look forward to reading from you !<br>
</font></div>
</blockquote>
<br>
I look forward to reading about your project :)<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
</pre>
</body>
</html>