XDK Cross Domain Development Kit

Hallo zusammen,

ich habe bereits das XDK Portal Beispiel am laufen. Problem hierbei, dass es eben nicht mit einem Enterprise W-Lan Netz funktioniert. Ich weiß es gibt inzwischen das Update für Enterprise sowie ein Beispiel dazu. Das habe ich gemacht und funktioniert auch. Jetzt ist meine Frage wie ich beides zusammenbekomme -> heißt das XDK Portal Beispiel mit Zugang über ein Enterprise W-Lan.

Könnt Ihr mir hierzu etwas Hilfestellung geben? Ich habe es bereits versucht, aber mit meinen geringen Software Kenntnissen wirds da schon schwierig. 

Vielen Dank.

Hallo Timm,

Willkommen in der XDK Community.
Du hast Recht, die Bosch XDK Portal Demo baut lediglich eine WPA Verbindung mit deinem lokalen Hotspot auf. Da diese aber zur eigenen Anpassung ausgelegt ist, müsstest du die gewünschte Funktionalität selbst implementieren.

Um WPA2-Enterprise nutzen zu können, müsstest du den Sourcecode im bxpWifi.c File auf WPA2-Enterprise anpassen. Um das im Detail zu bewerkstelligen, muss du die alte Wifi Implementierung durch die Implementierung der Wi-Fi Enterprise Demo, welche DHCP nutzt, ersetzen.

Bitte beachte, solltest du die einfachen Konfigurationsmöglichkeiten der Bosch XDK Portal Demo durch das File BCDS_bxpConfig.h weiterhin verwenden wollen, musst du auch dort eine zusätzliche Variable für den Usernamen anlegen, welche in deiner WPA-Enterprise Implementierung verwendet wird.

I hoffe, das hilft dir erstmal weiter. Solltest du weitere Fragen haben, zögere nicht ein Ticket zu erstellen.

Mit freundlichen Grüßen,
Franjo

Dear XDK community.

Timm has the purpose that he want's to use the Bosch XDK Portal demo, but he has only access to a local Wi-Fi accesspoint that supports WPA2-Enterprise. He is asking if we could give him som hints about how to extent the XDK Portal demo to use WP2-Enterprise.

I told him, that he has to change the Wi-Fi implementation in bxpWifi.c with the Wi-Fi implementation of the Enterprise Wi-Fi demo, which uses DHCP.

Additionally I told him, if he wants to keep the configuration options via the headerfile BCDS_bxpConfig.h of the Bosch XDK Portal demo, to add a new variable for the Enterprise username to the file BCDS_bxpConfig.h, which should be used in the added WPA-Enterprise implementation too.

Kind regards,
Franjo

Hallo,

hat zufällig jemand einen solchen Code schon erfolgreich umgesetzt? Dann müsste sich nciht jeder der es benötigt damit beschäftigen? ;)

Hallo Danny,

Code Beispiele werden normalerweise von den Usern der XDK community im Reiter Project Exchange mit den anderen Usern geteilt. Sofern dieses spezielle angepasste Beispiel dort nicht vertreten ist, dann ist es leider auch nicht in der XDK Community verfügbar.

Mit freundlichen Grüßen,
Franjo

Hello XDK community,

Danny asked if someone was able to implement the Wi-Fi Enterprise functionality into the Bosch XDK Portal demo. And if that was the case, he asked if the project could be shared, to reduce effort for other people who need the same functionality.

I told him, that usually projects are shared with other users in threads in Project Exchange. If the one he asked for is not there, then it is not available in the XDK community, unfortunately.

Kind regards,
Franjo

Hi,

should this work with the new Workbench 3.0 version too?

I've got the following error message:

fatal error: XdkBoardHandle.h: No such file or directory    WiFiHostPgm.c    /WiFiHostProgramming/source    line 50    C/C++ Problem

Best regards,

Attila

Hello Attila,

the Enterprise Wi-Fi demo had not officially been migrated to 3.0 yet, but will be soon updated and released officially for the latest XDK-Workbench version 3.0.0.

We have prepared a pre-release for you downloadable here, available until it is officially released.

Kind regards,
Franjo

Hi Franjo,

thank you for the new version. I'm facing the following issue (after the invalid program error):

INFO | Booting application...
INFO | XDK DEVICE 1: b
INFO | XDK DEVICE 1:  Jumping to application
INFO | Port 'COM4' has been disconnected
INFO | Connecting to XDK device 'XDK Device 1' in port 'COM4'...
INFO | Connection to port 'COM4' established
INFO | XDK DEVICE 1: Error in led and button initialization

Is this a known problem or something wrong with my computer?

Hello Attila,

thanks for the feedback. Unfortunately, there are still some issues with the code, which still need to be fixed. We will upload another version as soon as possible. Until then, I can only ask for your patience.

Kind regards,
Franjo

Hello Attila,

I am glad to tell you that we fixed all remaining issues in the Wi-Fi Enterprise demo. The new  version is available via the download link in my previous post.

Kind regards,
Franjo

Hi Franjo,

thank you for the information! I've downloaded the new Workbench 3.01 and the new Wi-Fi Enterprise demo. I'm now successfully connected to the enterprise Wi-Fi.

Thank you for your support!

Best regards, Attila

Hello Attila,

I am glad to hear that it works for you now.

Please feel free to ask if you have further questions.

Kind regards,
Franjo

Hello,

I've tried the WiFi and it's connected fine, but after a while (~30min) it disconneting from the network.

Do you have any idea what could be the problem?

Thanks in advane!

Hello Balazs,

a disconnection from your local Enterprise Wi-Fi hotspot can have multiple causes. Your hotspot could have been temporarily overburdened and the XDK would be forced to disconnect from it.
But that is only one possible scenario, and unfortunately, the Enterprise Wi-Fi demo does not integrate a routine to check if the connection is still active or a reconnect has to be done. As such, if the XDK loses the connection, it won't connect again to your local Enterprise hotspot.

To solve that, you could implement an additional timer task, that regularly checks if the XDK is connected to the Enterprise Wi-Fi hotspot and reconnects if necessary. The reconnect code would look as follows:

 if(CONNECTED_AND_IPV4_ACQUIRED != WlanConnect_GetCurrentNwStatus()){
        WlanConnect(connectSSID, connectPassPhrase, NULL);
        }

Alternatively, you can do this check every time you want to transmit something via the Wi-Fi connection.

Please note that you would have to make the variables, which contain the SSID and the passphrase, global.

Please let me know if that was helpful and do not hesitate to ask if you have further questions.

Kind regards,
Franjo

Hi Franjo,

we've checked the WiFi controller's log and found some interesting entry:

*Dot1x_NW_MsgTask_0: Sep 20 22:32:56.287: #DOT1X-3-ABORT_AUTH: 1x_bauth_sm.c:449  Authentication Aborted for client 98:84:e3:4d:27:10

*dot1xMsgTask: Sep 21 06:43:21.258: #DOT1X-3-WPA_SEND_STATE_ERR: 1x_kxsm.c:1405 Unable to send EAPOL-key msg  - invalid WPA state (0) - client 98:84:e3:4d:27:10

These messages appear continuously in the log. Is it failure on the XDK-site?

The XDK disconnection time is still about 30 minutes.

- Attila -

Hello Attila,

could you go more into detail about the log? Are these messages appearing ever since you implemented the reconnection code, which I porsted previously? What exactly do you mean by "appear continuously", when you refer to the message's appearancy? Additionally, I would like to know more about your local Enterprise Wi-Fi to reproduce the issue. What device are you using, can you present me a snapshot of your configurations?

Kind regards,
Franjo

Hi Franjo,

I'll try to collect more information, at least detailed log entries. Parallel I'll test this issue with the original demo application. Maybe I made something wrong during the wiring of the two code (EnterpriseWifi + SendDataOverUDP)...

- Attila -

Same issue with the original (unmodified) EnterpriseWifi application. After ~30 mins the device didn't respond to ping.

The comtroller's type is Cisco WLC 5505 (Unfortunately I can't provide the WLAN-Controller's config.)

Sep 28 09:54:23 10.11.16.124 *Dot1x_NW_MsgTask_0: Sep 28 07:54:23.031: #DOT1X-3-ABORT_AUTH: 1x_bauth_sm.c:449  Authentication Aborted for client 98:84:e3:4d:27:10

Sep 28 09:56:21 10.11.16.124  *Dot1x_NW_MsgTask_0: Sep 28 07:56:21.045: #DOT1X-3-ABORT_AUTH: 1x_bauth_sm.c:449  Authentication Aborted for client 98:84:e3:4d:27:10

The XDK started at Sep 28 ~09:24 and after 30 mins was not reachable. In this case we saw just this two entries.

Hello Attila,

Thank you for providing the information about your Enterprise Wi-Fi. But you didn't answer my question since I asked you if this behavior is appearing after you inserted the recommended reconnect routine.

Regarding your test case, you told me that you combined the Enterprise Wi-Fi demo application with the sendDataOverUdp example. Afterwards, I assume you pinged the XDK with a script to check if it is still connected to the Enterprise Wi-Fi hotspot? Additionally, you said you observed the same behavior when you used the unaltered Enterprise Wi-Fi demo. Is that correct?

Does this imply that both projects had integrated the reconnect routine I posted before?

In general, Wi-Fi connections are not as stable as wired connections. The XDK is especially affected by this, and the Wi-Fi chip does not automatically attempt to reconnect. This is why I always recommend to add a reconnect routine to any code that uses Wi-Fi for long periods of time.

Kind regards,
Franjo

 Hello Franjo,

sorry, I forgot to answer this question. We've tried the suggested solution (reconnect routine) but the result was the same. No package transfer after 30 mins.

I added the following part to SendDataOverUdp.c --> static void wifiUdpSend(void * param1, uint32_t port):

// chek Wi-Fi status and reconnect if neccessary
    if(CONNECTED_AND_IPV4_ACQUIRED != WlanConnect_GetCurrentNwStatus())
    {
        printf("Wi-Fi Reconnecting...\r\n");
        WlanConnect(connectSSID, connectPassPhrase, NULL);
    }

Yes, I pinged the XDK device from command line using "ping -t [IPADDRESS]". I used the original Enterprise Wi-Fi demo without the reconnection routine and it was also disconnected after 30 mins.

We're trying to stream sensor data (2 package / sec) using WiFi (establishing LAN endpoints in the production is not so easy sometimes) and for that we need stable connection. In the current phase we try to find out which communication interface (WiFi / LAN / Bluetooth) would be better for us.

I'll test this with WPA personal and with separated wireless network (not with the enterprise network).

Thank you for help! I'll let you know if I found something interesting.

Best regards, Attila

Hello Attila,

I am glad to help. Thank you for answering the question.

I will analyze this issue in more detail. To do it, I will try to reproduce your environment as far as possible, to receive the same behavior. Could you tell how many hotspots are working on the same channel than your current enterprise hotspot? It other words, is there a possibility that the WiFi channel is overburden? And does the disconnect occur after exactly ~30 minutes, or is that just a rough estimate?

Regarding your application, you used the Enterprise Wi-Fi demo in combination with the SendDataOverUdpExample to send environmental sensor data via UDP. Is that correct?

Kind regards,
Franjo