[Ovmsdev] Hidden WiFi SSID connection?

Stephen Casner casner at acm.org
Sun Dec 3 08:06:02 HKT 2017


Greg,

The crash was in the "new" operation because you ran out of heap
space.

                                                        -- Steve

On Sat, 2 Dec 2017, Greg D. wrote:

> Hi all,
>
> Is there an easy way to enable the wifi code to connect to an SSID that's known
> (configured) but hidden, without directly telling it to?  i.e., using 'wifi mode
> client' by itself (no SSID specified)?
>
> Some of the places I want to connect to are visible (seen in a scan), but the home
> network is hidden.  If it helps, running a scan within earshot of the home network
> only burps up an error 'wifi: incorrect scan type: 1073583304'.
>
> Greg
>
> p.s.  Possibly related, I have the module in my Roadster, connected to the V2 server
> via WiFi through a SyncUp Drive OBDII dongle that's being driven by the OBD2ECU
> engine.  The SyncUp's WiFi hotspot is visible, and I have a startup script that gets
> everything going, and the OVMS module auto connects through it.  I just tried forcing
> the connection over to the home network (wifi mode client gregnet) and after switching
> networks and reconnecting to the V2 server, crashed and rebooted (whereupon it
> reconnected through the dongle's network).  Any ideas?
>
> OVMS > wifi mode client gregnet
> Starting WIFI as a client to gregnet...
> I (1519905) wifi: ap_loss
> I (1519905) wifi: state: run -> init (0)
> I (1519905) wifi: pm stop, total sleep time: 0/1415162800
>
> I (1519905) wifi: n:1 0, o:1 0, ap:255 255, sta:1 0, prof:1
> I (1519915) ovms-server-v2: Disconnected from OVMS Server V2
> I (1520415) webserver: Stopping Web Server
> I (1520415) telnet: Stopping Telnet Server
> I (1520415) ssh: Stopping SSH Server
> I (1523025) wifi: n:6 0, o:1 0, ap:255 255, sta:6 0, prof:1
> I (1523685) wifi: state: init -> auth (b0)
> I (1523685) wifi: state: auth -> assoc (0)
> I (1523685) wifi: state: assoc -> run (10)
> I (1523715) wifi: connected with gregnet, channel 6
> OVMS > I (1524725) event: ip: 10.30.1.102, mask: 255.255.255.0, gw: 10.30.1.1
> I (1524725) ovms-mdns: Launching MDNS service
> WiFi UP with SSID: gregnet, IP: 10.30.1.102, mask: 255.255.255.0, gw: 10.30.1.1
> I (1524735) webserver: Launching Web Server
> I (1524745) telnet: Launching Telnet Server
> I (1524755) ssh: Launching SSH Server
> I (1529915) ovms-server-v2: Connection is tmc.openvehicles.com:6867
> ROADSTER_834/Gdbkt2017server
> I (1530115) ovms-server-v2: Connected to OVMS Server V2 at tmc.openvehicles.com
> I (1530115) ovms-server-v2: Sending server login: MP-C 0 1zyHGC+OXD1EofY2dlH19v
> sy8L79oHSah2+yDqliMKTA== ROADSTER_834
> I (1530305) ovms-server-v2: Received welcome response MP-S 0 N9H5zlASBHMxtzteFD9WpG
> ZoNMc8491dJNxl/x6XSIxg==
> I (1530305) ovms-server-v2: Got server response: MP-S 0 N9H5zlASBHMxtzteFD9WpG
> ZoNMc8491dJNxl/x6XSIxg==
> I (1530315) ovms-server-v2: Server token is N9H5zlASBHMxtzteFD9WpG and digest is
> ZoNMc8491dJNxl/x6XSIxg==
> I (1530315) ovms-server-v2: Server authentication is successful. Prime the crypto...
> I (1530315) ovms-server-v2: Shared secret key is
> N9H5zlASBHMxtzteFD9WpG1zyHGC+OXD1EofY2dlH19v (44 bytes)
> I (1530315) ovms-server-v2: OVMS V2 login successful, and crypto channel
> establishedbort() was called at PC 0x40121ad6 on core 1
> 0x40121ad6: _Znwj at
> /home/ivan/e/crosstool-NG/.build/src/gcc-5.2.0/libstdc++-v3/libsupc++/new_op.cc:54
>
>
> Backtrace: 0x400886e0:0x3fff8140 0x400887df:0x3fff8160 0x40121ad6:0x3fff8180
> 0x40121ab5:0x3fff81a0 0x40120200:0x3fff81c0 0x400f998e:0x3fff81f0
> 0x400f3d3e:0x3fff8290
> 0x400886e0: invoke_abort at /home/greg/esp/esp-idf/components/esp32/./panic.c:519
>
> 0x400887df: abort at /home/greg/esp/esp-idf/components/esp32/./panic.c:519
>
> 0x40121ad6: _Znwj at
> /home/ivan/e/crosstool-NG/.build/src/gcc-5.2.0/libstdc++-v3/libsupc++/new_op.cc:54
>
> 0x40121ab5: _Znaj at
> /home/ivan/e/crosstool-NG/.build/src/gcc-5.2.0/libstdc++-v3/libsupc++/new_opv.cc:32
>
> 0x40120200: _ZN10OvmsBuffer10PollSocketEil at/home/greg/greg/ovms/Open-Vehicle-Monitoring-System-3-master/Open-Vehicle-Monitoring-
> System-3/vehicle/OVMS.V3/main/./ovms_buffer.cpp:145
>
> 0x400f998e: _ZN12OvmsServerV210ServerTaskEv at/home/greg/greg/ovms/Open-Vehicle-Monitoring-System-3-master/Open-Vehicle-Monitoring-
> System-3/vehicle/OVMS.V3/components/ovms_server_v2/src/ovms_server_v2.cpp:247
>
> 0x400f3d3e: _ZL15OvmsServer_taskPv at/home/greg/greg/ovms/Open-Vehicle-Monitoring-System-3-master/Open-Vehicle-Monitoring-
> System-3/vehicle/OVMS.V3/components/ovms_server/./ovms_server.cpp:55
>
>
> Rebooting...


More information about the OvmsDev mailing list