<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="">Oh, and also important to bring out some expansion via sockets on side of case. In particular for digital I/O.<div class=""><br class=""></div><div class="">Regards, Mark.</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 2 Feb 2016, at 5:21 PM, Mark Webb-Johnson <<a href="mailto:mark@webb-johnson.net" class="">mark@webb-johnson.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=windows-1252" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><meta http-equiv="Content-Type" content="text/html charset=windows-1252" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">My preference for connectors is those 0.1” SIP/DIP ones. They are extremely vibration resistant, breadboard compatible, stackable, etc.<div class=""><br class=""></div><div class=""></div></div><span id="cid:1BD9BE58-4EEE-409C-9A52-FA8E3998BDC6"><PastedGraphic-3.tiff></span><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><meta http-equiv="Content-Type" content="text/html charset=windows-1252" class=""><div class=""></div></div><span id="cid:2FEFF291-3674-47C3-9EB5-859D27799739"><PastedGraphic-2.tiff></span><meta http-equiv="Content-Type" content="text/html charset=windows-1252" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""></div><div class=""><br class=""></div><div class="">When layed out properly, they also allow you to stack expansion over existing board components, without sacrificing much space.<br class=""><div class=""><br class=""></div><div class="">For bringing out lots of pins, not so good. But for enough for one or two expansion slots they work well.</div><div class=""><br class=""></div><div class="">Regards, Mark.</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 2 Feb 2016, at 4:59 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 text="#000000" bgcolor="#FFFFFF" class="">
<br class="">
<div class="moz-cite-prefix">On 02/02/2016 08:49 AM, Mark
Webb-Johnson wrote:<br class="">
</div>
<blockquote cite="mid:B410D199-7E13-4F4F-8F98-CDCD0947751B@webb-johnson.net" type="cite" class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
Julien,
<div class=""><br class="">
</div>
<div class="">It seems that our thinking is similar.</div>
<div class=""><br class="">
</div>
<div class="">I view OVMS as the CAN processor - perhaps a
bridge/gateway - and telematics module. User Interface, Car PC,
etc, systems are best handled externally by something that
starts up and shuts down with the ignition switch and can suck
as much power as your home PC. OVMS has to keep running, in as
low power mode as possible, as telematics are required even when
the car is off.</div>
</blockquote>
Exactly, my whole point, plus, that part, externalized, with a
standardized way of communicating with the OVMS (uart/bt +
ethernet/wifi+mqtt,<a class="moz-txt-link-freetext" href="http://api/">http://api</a>) will give a full freedom of
implementation of the Heavyweight part. BTW: one of the extension
boards could be a power-control board with power state signaling,
MOSFETs, and a watchdog for that part<br class="">
<blockquote cite="mid:B410D199-7E13-4F4F-8F98-CDCD0947751B@webb-johnson.net" type="cite" class="">
<div class=""><br class="">
</div>
<div class="">Regarding ESP32, that is top of our shortlisted
devices for wifi/bluetooth. But, it depends on release schedule.
We want OVMS v3 to be FCC and CE certified, and that means we
must use FCC+CE certified modules for the comms parts.</div>
</blockquote>
I don't know if their distribution of 200 beta boards was a cap
limit, but maybe shooting a mail to <a class="moz-txt-link-abbreviated" href="mailto:beta@espressif.com">beta@espressif.com</a> might be
worth it, asking them for approximate timelines with it, no ?<br class="">
<blockquote cite="mid:B410D199-7E13-4F4F-8F98-CDCD0947751B@webb-johnson.net" type="cite" class="">
<div class=""><br class="">
</div>
<div class="">The overall goal is for OVMS v3 to be the
microprocessor, power, CAN, USB, ethernet, wifi, and bluetooth,
as a base module. Then, everything else (including cellular) are
optional plugin modules. We could make wifi+bluetooth optional,
but I suspect that they will not add dramatically to the
cost/complexity to include as standard. This has got to go in an
automotive environment, so plugin modules will most likely go on
some sturdy headers on the board.</div>
</blockquote>
BT/BLE I believe is a minimum to have: It will allow people to have
a locally connected Android App (without pumping data over a slow,
optionnal and maybe misconfigured GSM stack) and without any hassle
at that, latency can be sub 0.5s which is bareable for live
metrics... plus, not all phones implement USB OTG correctly... and
it's cablefree, which non-DIYers might appreciate.<br class="">
<br class="">
Form factor wise, my edge connector idea might not be that great,
we'd end up with a lonnnngg serie of boards, maybe stackable as an
arduino shield ? connectors are cheap, easier for the DIYer, no need
to design long pathways that get in the way for signals from border
to border...<br class="">
<br class="">
<blockquote cite="mid:B410D199-7E13-4F4F-8F98-CDCD0947751B@webb-johnson.net" type="cite" class="">
<div class=""><br class="">
</div>
<div class="">Regards, Mark.</div>
<div class=""><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On 2 Feb 2016, at 3:34 PM, Julien Banchet <<a moz-do-not-send="true" href="mailto:jaxx@jaxx.org" class=""></a><a class="moz-txt-link-abbreviated" href="mailto:jaxx@jaxx.org">jaxx@jaxx.org</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">Hi,<br class="">
<br class="">
</div>
I love the OpenCV part, though I'll
have to find a way to retofit
powersteering and brake actuators in
a Twizy, that said, it all shoots
way beyond the scope of OVMS (even a
v4/v5) imho... but, but, but... an
OVMS module shall be the bridge and
the low-level comms offloader for an
optionnal "Hyper Smart OpenCV
Dashboard Music Streaming thingy"
that a sister project can take over
:-) (my opinion again)<br class="">
<br class="">
</div>
So yeah, It needs to be beefy, and the
ESP32 seems to be a nice candidate and
embeds by itself a nice load of
functions (Wifi and BLE!)<br class="">
<a moz-do-not-send="true" href="http://www.pighixxx.com/test/2015/12/esp32-processor-pinout/" class="">http://www.pighixxx.com/test/2015/12/esp32-processor-pinout/</a><br class="">
<br class="">
</div>
It has no CAN, but it has SPI (can't
tell how many on this pinout) and plenty
of HS GPIOs for native or soft UARTs.
Having 2 CANbuses shouldn't be an issue
(I'll let those who fathomed that more
than me tell me wrong otherwise)<br class="">
<br class="">
</div>
I don't believe everyone needs a 2/3/4G
stack, not counting that those radios end
up being the big bucks of the BOM.<br class="">
<br class="">
</div>
Instead, would it be possible to envision a
naked board with an extension bus and i2c,
interrupts, multiplexed (or not) enable and
power lanes? (an edge fitted socket for
example, each extension board presents
another socket)<br class="">
<br class="">
</div>
The motivation for this particular request is:<br class="">
</div>
<div class="">- It lowers the base cost, with
knowledge it can be enhanced, and still
carries Wifi+BTBLE for local connectivity with
an ESP32<br class="">
</div>
- I doubt my Twizy will ever be stolen to be
brought out of LoRa range, and those networks
are being deployed quickly, no need for power
hungry GSM stacks (that empty my Twizys' 12V
battery in 3 days, driving me nuts by the way)<br class="">
</div>
- I might want a home brewed I2C GPIO extender on
it, a socket makes it easy to make (or a stepper
motor drivers to pilot a paintball gun turret
fitted on the roof and shoot *ssholes)<br class="">
</div>
- The hypothetical day I upgrade to a Tesla 3, I can
add that 5G Module that wasn't out yet ;-)<br class="">
<br class="">
</div>
Just thoughts,<br class="">
<br class="">
</div>
JaXX<br class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class=""><br class="">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Mon, Feb 1, 2016 at 8:30 PM,
Michael Eymann <span dir="ltr" class=""><<a moz-do-not-send="true" href="mailto:Michael.Eymann@networkz.de" target="_blank" class=""></a><a class="moz-txt-link-abbreviated" href="mailto:Michael.Eymann@networkz.de">Michael.Eymann@networkz.de</a>></span>
wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word" class="">All,
<div class=""><br class="">
</div>
<div class="">what about opening our garden,
providing a public park which could be used for
several features beside the scope of this group?</div>
<div class=""><br class="">
</div>
<div class="">3G/4G Wlan Bluetooth GPS whatever
could be added / replaced easily….</div>
<div class=""><br class="">
</div>
<div class="">what i mean is vocabulary like:</div>
<div class="">- raspberry pi</div>
<div class="">- CarPI (CarPC)</div>
<div class="">- OBD - smartphone speedometer
gadgets (sure really useless - but the
mainstream love it)</div>
<div class="">- Harry´s laptimer support (<a moz-do-not-send="true" href="http://www.gps-laptimer.de/" target="_blank" class=""></a><a class="moz-txt-link-freetext" href="http://www.gps-laptimer.de/">http://www.gps-laptimer.de</a>)
// video: <a moz-do-not-send="true" href="https://www.youtube.com/watch?v=fTCNhmsFZBE" target="_blank" class="">Harry's LapTimer
GPS/OBD II Video Overlay - Nordschleife with
911 GTS</a> <a moz-do-not-send="true" href="https://www.youtube.com/watch?v=fTCNhmsFZBE" target="_blank" class="">https://www.youtube.com/watch?v=fTCNhmsFZBE</a></div>
<div class="">- Wlan.. repeater - hotspot… (my
favorit)</div>
<div class=""><span style="white-space:pre-wrap" class=""> </span></div>
<div class="">this could also enable add on
development….</div>
<div class="">- spotify </div>
<div class="">- surround view parking (raspian
& openCV?) // AVM: <a moz-do-not-send="true" href="https://www.youtube.com/watch?v=1Q9iVoSvjGk" target="_blank" class="">AVM (Around View Monitoring /monitor
) 4CH camera become 360 degree Parking
Guidance System</a> <a moz-do-not-send="true" href="https://www.youtube.com/watch?v=1Q9iVoSvjGk" target="_blank" class="">https://www.youtube.com/watch?v=1Q9iVoSvjGk</a></div>
<div class="">- KITT Watch - car call?</div>
<div class="">- replace Infotainment systems</div>
<div class="">- SmartAutomation like OpenHab
integration (They call it „Binding“ - Tesla
Model S Binding is already integrated - did they
overtake us? ;-) <a moz-do-not-send="true" href="http://www.openhab.org/" target="_blank" class="">http://www.openhab.org</a></div>
<div class=""><span style="white-space:pre-wrap" class=""> </span></div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">views?</div>
<span class="HOEnZb"><font class="" color="#888888">
<div class=""><br class="">
</div>
<div class="">Michael</div>
<div class=""><br class="">
</div>
</font></span>
<div class=""><br class="">
<div class="">
<div class="">
<div class="h5">
<div class="">Am 01.02.2016 um 18:51
schrieb Dominik Westner <<a moz-do-not-send="true" href="mailto:ovms@nikwest.de" target="_blank" class=""></a><a class="moz-txt-link-abbreviated" href="mailto:ovms@nikwest.de">ovms@nikwest.de</a>>:</div>
<br class="">
</div>
</div>
<div class="">
<div class="">
<div class="h5">
<div style="word-wrap:break-word" class="">Generally I think 3G doesn’t
make a lot of sense. A new platform
should be 4G capable. As far as I know
2G is more likely to stay longer than
3G.
<div class="">I know already some
areas in Germany and Austria where
you can find 4G and maybe 2G, but no
3G.</div>
<div class=""><br class="">
<div class="">For example
seeedstudio retargeted their
Rephone 3G module to 4G after some
investigations about the future of
3G.<br class="">
<div class="">(<a moz-do-not-send="true" href="https://www.kickstarter.com/projects/seeed/rephone-kit-worlds-first-open-source-and-modular-p/posts/1468366" target="_blank" class=""></a><a class="moz-txt-link-freetext" href="https://www.kickstarter.com/projects/seeed/rephone-kit-worlds-first-open-source-and-modular-p/posts/1468366">https://www.kickstarter.com/projects/seeed/rephone-kit-worlds-first-open-source-and-modular-p/posts/1468366</a>)</div>
<div class=""><br class="">
</div>
<div class="">Just my 2 cents</div>
<div class=""><br class="">
</div>
<div class="">Dominik</div>
<div class=""><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On 01 Feb
2016, at 18:30, Arthur
Hebert <<a moz-do-not-send="true" href="mailto:ahebert@gmail.com" target="_blank" class=""></a><a class="moz-txt-link-abbreviated" href="mailto:ahebert@gmail.com">ahebert@gmail.com</a>>
wrote:</div>
<br class="">
<div class="">
<div dir="ltr" class="">The
Particle Electron has
recently caught my
attention: <a moz-do-not-send="true" href="https://www.particle.io/cellular" target="_blank" class=""></a><a class="moz-txt-link-freetext" href="https://www.particle.io/cellular">https://www.particle.io/cellular</a>.
Actual performance and
usability are unknown,
since the first units
don't ship until later
this month, but it has
some attractive
features:
<div class="">
<ul class="">
<li class="">low-cost
M2M-oriented
international
SMS/data plans
($3/mo. for 20k
messages)</li>
<li class="">STM32F205
MCU with <b class="">1MB
flash</b>, 128k
RAM and <b class="">2 CAN
buses</b></li>
<li class="">free
development IDE: <a moz-do-not-send="true" href="https://www.particle.io/dev" target="_blank" class=""></a><a class="moz-txt-link-freetext" href="https://www.particle.io/dev">https://www.particle.io/dev</a></li>
<li class="">also a
free web-based dev
environment at <a moz-do-not-send="true" href="https://build.particle.io/" target="_blank" class=""></a><a class="moz-txt-link-freetext" href="https://build.particle.io/">https://build.particle.io</a>
(I assume/hope
this will support
the Electron
cellular board
when it comes out)</li>
</ul>
<div class="">I know
it doesn't come
close to meeting the
RAM requirements,
but the cellular
plan is a pretty big
draw IMO. Perhaps
worth using this
module in
conjunction with
another board with a
better MCU?</div>
</div>
<div class=""><br class="">
</div>
<div class="">-Arthur</div>
</div>
<div class="gmail_extra"><br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</div>
</div>
</div>
<span class="">_______________________________________________<br class="">
OvmsDev mailing list<br class="">
<a moz-do-not-send="true" href="mailto:OvmsDev@lists.teslaclub.hk" target="_blank" class="">OvmsDev@lists.teslaclub.hk</a><br class="">
<a moz-do-not-send="true" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" target="_blank" class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br class="">
</span></div>
</div>
<br class="">
</div>
</div>
<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 moz-do-not-send="true" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" rel="noreferrer" target="_blank" class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br class="">
<br class="">
</blockquote>
</div>
<br class="">
</div>
_______________________________________________<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=""><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br class=""></div></blockquote></div><br class=""></div></div></div></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>