[Ovmsdev] wifi not coming all the way up?

[Julien “JaXX” Banchet]

Tried the v3 alone on the bus (leaving module RT, will try ‘none' later on Marks suggestion)

Plugged, waited a minute, then put the contact.
It didn’t go very well, I hopefully didn’t burst into flames neither :)

https://photos.app.goo.gl/rlkUmowR28AAp8Nf2

JB./.



On 19 Mar 2018 at 14:22 +0100, Michael Balzer <dexter at expeedo.de>, wrote:
> The RT module sets the Twizy CAN speed, no need to configure that.
>
> I'm pretty sure it's been caused by the v2 hooked to the bus parallel to the v3. Maybe that can work if you only allow one of them to write to the bus.
>
> Btw, Arduino CAN shields often need some jumper for termination.
>
> Regards,
> Michael
>
>
> Am 19.03.2018 um 14:01 schrieb Julien “JaXX” Banchet:
> > Oh!? A wrong CAN speed ? Haven’t though of that.
> >
> > I have RT set, but I do’t know how to look up the speed which is set (besides the defaulted CONFIG_CAN_SPEED_100KBPS=y in sdkconfig, though I suppose the module sets the right speed, right ?)
> >
> > JB./.
> >
> > On 19 Mar 2018 at 13:39 +0100, Mark Webb-Johnson <mark at webb-johnson.net>, wrote:
> > > Do you have a vehicle module defined, with a can bus active?
> > >
> > > I had a similar thing when I was set to 1Mbps (it should have been 500Kbps).
> > >
> > > Regards, Mark.
> > >
> > > > On 19 Mar 2018, at 7:46 PM, Julien “JaXX” Banchet <jaxx at jaxx.org> wrote:
> > > >
> > > > It went christmas animation nuts as soon as I plugged it on the bus (already contact ON+GO), and went away the second I unplugged it.
> > > >
> > > > I admit having left the v2 (which still carries all my profiles, and in case I needed to limit power+recup on the way as it’s been snowing again)
> > > >
> > > > My bet is that there where too many CAN terminations on the bus and the dashboard cluster couldn’t see it’s friends, I’ll give it a shot without v2 on my way back home.
> > > > (Which leads me to believe the termination resistor on my Arduino OBD shields aren’t connected)
> > > >
> > > > JB./.
> > > >
> > > > On 19 Mar 2018 at 12:43 +0100, Michael Balzer <dexter at expeedo.de>, wrote:
> > > > > Uh oh… CAN bus contact failure? I haven't had any issues like that…
> > > > >
> > > > > Am 19.03.2018 um 11:09 schrieb Julien “JaXX” Banchet:
> > > > > > That didn’t happen :-)
> > > > > > https://twitter.com/happyjaxx/status/975675071451844608
> > > > > >
> > > > > > On 19 Mar 2018 at 10:07 +0100, Julien “JaXX” Banchet <jaxx at jaxx.org>, wrote:
> > > > > > >
> > > > > > > Gonna put it in the car (despite the passive GPS issue)
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > OvmsDev mailing list
> > > > > > OvmsDev at lists.teslaclub.hk
> > > > > > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> > > > >
> > > > >
> > > > > --
> > > > > Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
> > > > > Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
> > > > > _______________________________________________
> > > > > OvmsDev mailing list
> > > > > OvmsDev at lists.teslaclub.hk
> > > > > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> > > > _______________________________________________
> > > > OvmsDev mailing list
> > > > OvmsDev at lists.teslaclub.hk
> > > > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> > >
> > > _______________________________________________
> > > OvmsDev mailing list
> > > OvmsDev at lists.teslaclub.hk
> > > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> >
> >
> > _______________________________________________
> > OvmsDev mailing list
> > OvmsDev at lists.teslaclub.hk
> > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>
>
> --
> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180319/60403d6e/attachment.htm>