We use cookies and similar technologies (also from third parties) to collect your device and browser information for a better understanding on how you use our online offerings. This enables us to optimize and personalize your experience with Infineon and to provide you with additional services and information based on your individual profile. Details are available in our privacy policy.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Home
- Software
- WICED™ Studio
- WICED Studio Wi-Fi Combo
- Re: connection problem
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Anonymous
Not applicable
Nov 07, 2013
12:07 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi,I am testing two modules containing Broadcom from company Inventek Systems, the ISM4319 and the ISM43362 module.When connecting to a test access point, Eminent EM4553, the ISM4319 can connect easily but I cant get the ISM43362 to be connected as well.I made some capture files using WireShark in monitor mode and also attached the settings of the access point. One remark, when changing the security to open, so no secured network, then the ISM43362 will connect as well. I would be nice to get some feedback on this, to know why the ISM43362 will not connect (even after 20 times retry). Thanks!best regards, Mels.
Solved! Go to Solution.
Labels
- Labels:
-
SPI
- Tags:
- access
- attached
- broadcom
- capture
- changing
- company
- connect
- connected
- connecting
- connection
- easily
- em4553
- eminent
- feedback
- files
- inventek
- ism4319
- ism43362
- made
- mels
- mode
- module
- modules
- monitor
- network
- nice
- open
- point
- problem
- remark
- retry
- secured
- security
- settings
- systems
- test
- testing
- times
- wireshark
1 Solution
Anonymous
Not applicable
Nov 18, 2013
12:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Issue is solved by setting connection time to 7 sec. Now all modules are able to join!
The timeout for joining (C0 command) has been changed from 3000ms to 7000ms for routers that need more time to join.
2 Replies
Level 3
DiBa_1995216
Level 3
Nov 12, 2013
08:57 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
The timeout for joining (C0 command) has been changed from 3000ms to 7000ms for routers that need more time to join.
Anonymous
Not applicable
Nov 18, 2013
12:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Issue is solved by setting connection time to 7 sec. Now all modules are able to join!
The timeout for joining (C0 command) has been changed from 3000ms to 7000ms for routers that need more time to join.
Top labels
-
8-bit-16-bit-and-32-bit-proprietary
1 -
ADC
19 -
AWS
82 -
Cloud
62 -
Community Information
4 -
DCT
97 -
Debug
179 -
Ethernet
19 -
FM4_MCU
1 -
GPIO
51 -
Help
1 -
I2CI2S
39 -
Interrupts
38 -
Legacy Microcontrollers
3 -
Linux
39 -
MAC OSX
35 -
Manufacturing and Test
72 -
Memory
110 -
Other Legacy MCU
1 -
Other Technologies General
5 -
Over The Air Updates (OTA)
151 -
PCBLayout
33 -
PSoC 6 MCU
1 -
PSoC general
5 -
RegulatoryCertification
51 -
RTOS
1 -
SDK 2.4.1
183 -
SDK 3.x
808 -
Security
127 -
softAP
142 -
SPI
662 -
TCPIP
243 -
UART
107 -
Web Services
110 -
Wi-Fi Direct
196 -
WICED Studio
527 -
WICED Studio Wi-Fi Combo
171 -
Wifi+Bluetooth
608 -
Windows
99 -
Wireless MCU
246
- « Previous
- Next »