<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Low power is one of our primary goals.<div class=""><br class=""></div><div class="">The idea is that each module will be individually capable of being powered up/down or sleep/awake. In addition, we’ll use a proper switching power supply (the current ones literally burn 13V down to 5V and 3.3V). Finally, the framework will support the central processor being put to sleep.</div><div class=""><br class=""></div><div class="">This is one of the reasons I am still interested in the hybrid Arduino/Linux design. I like the idea of a low power supervisor being able to sleep/awake a higher power processor.</div><div class=""><br class=""></div><div class="">Regards, Mark.</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 26 Aug, 2015, at 4:21 pm, Julien (JaXX) Banchet <<a href="mailto:jaxx@jaxx.org" class="">jaxx@jaxx.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
I agree,<br class="">
<br class="">
The unit has to be simple (actually i would have seen something
modular, with optionnal means of comms, but it would be a pain on
the SW side I suppose)<br class="">
Even a simple console port could do... or ethernet (being a network
guy, not liking wifi latency) and an MQTT stack :-)<br class="">
<br class="">
[ question: will each means of communication be disable-able ? the
Twizy has a cr*ppy service battery, the actual v2 eats it up in less
than a week in the best case, killing the car literally if you're
away from a plug, there is nearly no need for a continuosly powered
GSM/GPS when the car isn't moving, or barely a status update on a
regular basis or on events ]<br class="">
<br class="">
JaXX./.<br class="">
<br class="">
<div class="moz-cite-prefix">Le 26/08/2015 09:58, Mark Webb-Johnson
a écrit :<br class="">
</div>
<blockquote cite="mid:249763F2-129E-4F70-B842-AD8E7F6F93C8@webb-johnson.net" type="cite" class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
Display is interesting, and something a few have asked about.
<div class=""><br class="">
</div>
<div class="">My suggestion was to keep this off the basic unit,
as it is just too expensive and means the unit must be mounted
in a visible position. It dramatically changes the housing
design, and is hard to please everyone with one design. I would
rather provide:</div>
<div class=""><br class="">
</div>
<div class="">
<ul class="MailOutline">
<li class="">A standard port that can be used to drive an
external display</li>
<li class="">A standard protocol that can be used for external
displays either via that port or via bluetooth/wifi/cellular
comms link</li>
</ul>
</div>
<div class=""><br class="">
</div>
<div class="">That would mean a display could be run on an
iPhone/Android device via bluetooth/wifi.</div>
<div class=""><br class="">
</div>
<div class="">It would also mean that a dumb display couldn’t be
used, which would drive up cost for those that wanted a display,
but would give us the flexibility to add one for those that want
it. It would also keep all the display code out of the core
project and into a separate project.</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark.</div>
<div class=""><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On 26 Aug, 2015, at 3:48 pm, Julien (JaXX)
Banchet <<a moz-do-not-send="true" href="mailto:jaxx@jaxx.org" class="">jaxx@jaxx.org</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">Hi,<br class="">
<br class="">
I have little personnal time but I'd still be highly
interested in putting what I have on testing out a beta
v3... I'm slowly working on a cluster replacement for the
Twizy and having a board to preprocess comms to the CANbus
(or moving what I'm doing to the "heavyweight" part of a
Udoo Neo-like board) would be a great relief.<br class="">
<br class="">
Yes, I intend to make those LCD-dashboard-savvy Mercedes
and Jaguar drivers jealous :-)<br class="">
<br class="">
So if there are any available slots for a test board or
better/safer, an early version of a production board (to
give priority to the devs, i'm in no hurry), count me in.<br class="">
<br class="">
Best,<br class="">
<br class="">
Julien JaXX Banchet<br class="">
<br class="">
Le 26/08/2015 09:37, Mark Webb-Johnson a écrit :<br class="">
<blockquote type="cite" class="">Development boards are a
tricky thing. Our suppliers hate making too many of
them.<br class="">
<br class="">
What I’ve told them this time is to firstly make a
couple of test boards that we can use to validate all
major functionality (can we program, can we reach all
the auxiliary chips, do the lights flash, etc). Once we
have that, then come up with a development board based
on the test board design (without box, and more pinouts
available) and make 10 of them hand-soldered. We’ll send
those out to the guys developing vehicle modules to help
with their porting processes.<br class="">
<br class="">
Based on the feedback of the development boards, we can
then re-layout the production board to optimise for the
chosen case, and make the first production run (probably
100 to 200 units, machine soldered).<br class="">
<br class="">
Regards, Mark.<br class="">
<br class="">
<blockquote type="cite" class="">On 25 Aug, 2015, at
4:04 pm, Michael Balzer <<a moz-do-not-send="true" href="mailto:dexter@expeedo.de" class="">dexter@expeedo.de</a>>
wrote:<br class="">
<br class="">
Great news, thanks!<br class="">
<br class="">
Please put me on the list for two of the V3
development boards.<br class="">
<br class="">
I've forwarded your info to the Twizy forum. There are
some active beta testers, I asked to send orders for
the V3 development board to me or you.<br class="">
<br class="">
I said pricing will probably be max 200 €.<br class="">
<br class="">
Regards,<br class="">
Michael<br class="">
<br class="">
<br class="">
Am 25.08.2015 um 07:41 schrieb Mark Webb-Johnson:<br class="">
<blockquote type="cite" class="">Plans change.<br class="">
<br class="">
For some inexplicable reason (Michael? #twizycon?),
we had a jump in order for the v2 modules. August is
not even yet over, and they are going too quickly
now. We are down to about 40 (of which I need to
retain at least 10 for RMA/repair purposes).<br class="">
<br class="">
The Arduino+Linux hybrid sample boards look to be
delayed another month, and MBED OS was due in August
2015 but has yet to make an appearance.<br class="">
<br class="">
I checked, and the supplier has just a few hundred
SIM908 modules left.<br class="">
<br class="">
Accordingly, I just put in an order for
definitely-the-last-batch of 100x v2 modules. With
four more months to go in the year, I’ll take the
risk.<br class="">
<br class="">
Hopefully we can start work on v3 next month, once
we see the Arduino+Linux hybrid vs MBED OS options
solidify. I suspect MBED OS won’t be finalised until
2016Q1 anyway. The guys I am working with in China
suggest to first produce a small batch of
development boards (not in a case, but functionally
complete) so that we can start development work, and
then work on packaging the board into a small
footprint with case, certification, etc. I suspect
that this could be a six month project to get a
final v3 based packaged product, so those 140
remaining v2 modules should hopefully give us some
breathing room.<br class="">
<br class="">
I am excited about bluetooth and wifi options.
Pricing for these has plummeted, and available
options grown dramatically. I am hopeful that we can
get a small board with cellular + gps + wifi +
bluetooth radios, for a reasonable cost. Add on a
bunch of flash (1GB+), SD-card, RAM (at least 128KB,
maybe more), at least 2 CAN ports, and we’ll have a
pretty amazing vehicle hacking and telemetry
platform.<br class="">
<br class="">
Regards, Mark<br class="">
<br class="">
<blockquote type="cite" class="">On 11 Aug, 2015, at
10:17 am, Mark Webb-Johnson <<a moz-do-not-send="true" href="mailto:mark@webb-johnson.net" class=""></a><a class="moz-txt-link-abbreviated" href="mailto:mark@webb-johnson.net">mark@webb-johnson.net</a>>
wrote:<br class="">
<br class="">
<br class="">
At the current rate, the batch we have of OVMS v2
modules will run out sometime in the next two
months.<br class="">
<br class="">
Given the imminent shutdown of AT&T’s 2G
network in USA, global re-allocation of 2G
frequency bands, and the difficulties we are
having obtaining the discontinued SIM908, it is
decision time.<br class="">
<br class="">
Option #1: Re-order a large batch now, enough to
last us into the new year, but with the risk that
I’ll be personally stuck with them.<br class="">
Option #2: Just let the v2 modules run out, and
move on with the plans for v3.<br class="">
<br class="">
Development on v2 is stagnating. Partly because
the platform already does what we need it to do,
and partly because we’re hitting the limits (no
external connectivity other than GPRS, single CAN
bus, no storage, limited RAM, flash, etc).<br class="">
<br class="">
The v3 plans have been on hold for some time,
pending MBED OS release (first beta due this
month) and the imminent release of hybrid
processors such as that used in the UDOO Neo (due
in September). We know what we want, but it is
just too hard to pick a long-term platform when
everything is on the cusp of changing.<br class="">
<br class="">
I really want a v3 module. Something with lots of
RAM and Flash, wifi, bluetooth and cellular
connectivity, multiple CAN bus support, and a rich
development platform. Something we can all use as
a platform for reverse engineering as well as
end-user connectivity. I’ll do everything I can to
make this a reality. Just not today. Too much is
changing and we need to wait for things to
stabilise.<br class="">
<br class="">
So, my gut feeling is to choose option #2. 2G GPRS
is slowing dying, and building more on that
platform just seems to be the wrong decision. This
may leave us with several months of no platform
stock, but I would rather people waited than spend
$100 on something that is going to be
obsolete/outdated. Kind of like buying an iPhone
in August ;-) I don’t want to be stuck with the
stock, and I don’t want people to buy a v2, only
to have v3 come out a week later.<br class="">
<br class="">
Even if we started now, which we can’t, an
optimistic schedule for the first end-user v3
units would be early 2016.<br class="">
<br class="">
So, tough decisions, but I really think option #2
is best. Bottom line is if you need v2 modules,
order them now.<br class="">
<br class="">
If you are likely to need a large quantity for any
upcoming projects, let me know. The SIM908 modules
will be unavailable within the next month or so,
and changing to another module is a PITA I don’t
want to deal with (especially given the tight RAM
and FLASH we have now).<br class="">
<br class="">
Regards, Mark.<br class="">
<br class="">
</blockquote>
_______________________________________________<br class="">
OvmsDev mailing list<br class="">
<a moz-do-not-send="true" href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br class="">
</blockquote>
<br class="">
-- <br class="">
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal<br class="">
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
OvmsDev mailing list<br class="">
<a moz-do-not-send="true" href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br class="">
</blockquote>
_______________________________________________<br class="">
OvmsDev mailing list<br class="">
<a moz-do-not-send="true" href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br class="">
</blockquote>
<br class="">
_______________________________________________<br class="">
OvmsDev mailing list<br class="">
<a moz-do-not-send="true" href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre wrap="" class="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br class="">
</div>
_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br class=""></div></blockquote></div><br class=""></div></body></html>