C ALYPSO REFERENCE MANUAL AMB5201 / 261001102500 X V ERSION 1.
Revision history Manual version FW version HW version 1.0 1.0.0 2.0 Notes • Initial release of the manual Date January 2019 • Added chapter Reference design • Added chapter Information for Ex protection February 2019 1.1 1.0.0 2.0 1.2 1.0.0 2.0 • Added known issues in chapter Firmware history March 2019 1.3 1.0.0 2.0 • Added FCC compliance April 2019 Calypso reference manual version 1.2 www.we-online.
Abbreviations Abbreviation Name Description NWP Network processor unit 802.11 network processor unit AP Access point WLAN (IEEE 802.11) infrastructure node offering stations to connect to DC Duty cycle Transmission time in relation of one hour. 1% means, channel is occupied for 36 seconds per hour. FSE Field Sales Engineer Support and sales contact person responsible for limited sales area 0xhh [HEX] Hexadecimal All numbers beginning with 0x are stated as hexadecimal numbers.
Abbreviation Name Description WLAN Wireless Local Area Network P2P Peer to Peer MAC Medium access control IEEE Institute of Electrical and Electronics Engineers IP Internet Protocol Network layer protocol TCP Transmission Control Protocol Transport layer protocol UDP Use Datagram Protocol Transport layer protocol SSL Secure Sockets Layer Transport layer protocol TLS Transport Layer Security Transport layer protocol HTTP(s) Hypertext transfer protocol (secure) Application layer pr
Contents 1. Introduction 1.1. Operational description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2. Block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3. Ordering information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9 10 10 2. Electrical specifications 2.1. Recommended operating conditions 2.2. Absolute maximum ratings . . . . . . 2.3. Power consumption . . . . . . . . . . 2.3.1. Static . . . . . . . . . . . . . 2.4.
7. The command interface 7.1. Command types . . . . . . 7.2. AT command characteristics 7.2.1. Request . . . . . . 7.2.2. Confirmations . . . 7.2.3. Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 32 32 32 33 33 8. AT commands 8.1. Device commands . . . . . . . . . 8.1.
9. Provisioning 9.1. Start the provisioning mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2. Enter the credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 77 77 10. Typical application use cases 10.1. UDP communication . . . . . . . . . . . . . . . . . . . 10.1.1. Prerequisites . . . . . . . . . . . . . . . . . . 10.1.2. UDP socket communication . . . . . . . . . . 10.2. TCP communication . . . . . . . . . . . . . . . . . . . 10.3. Secure socket communication . . .
15.3.4. Antennas provided by Würth Elektronik eiSos . . . . . . . . . . . 15.3.4.1. 2600130011 - Helike - 169 MHz dipole antenna . . . . . . . . 15.3.4.2. 2600130041 - Herse - 434 MHz dipole antenna . . . . . . . . 15.3.4.3. 2600130081 - Hyperion-I - 868 MHz dipole antenna . . . . . 15.3.4.4. 2600130082 - Hyperion-II - 868 MHz magnetic base antenna 15.3.4.5. 2600130021 - Himalia - 2.4 GHz dipole antenna . . . . . . . . . . . . . 103 103 104 105 106 107 16. Reference design 16.1. EV-Board . . . . . . . .
22.6. Product life cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 22.7. Property rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 22.8. General terms and conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 131 23. Legal notice 23.1. Exclusion of liability . . . . . . . . . 23.2. Suitability in customer applications 23.3. Trademarks . . . . . . . . . . . . . 23.4. Usage restriction . . . . . . . . . . . . . . . . . . . . . . . . . . .
1. Introduction The Calypso WLAN module is a compact WLAN radio module based on IEEE 802.11 b/g/n with a fully featured TCP/IP stack. The edge castellated connections, smart antenna configuration and an easy-to-use AT-style command interface enables easy integration of Calypso into any embedded application. The module supports IPv4 as well as IPv6 and implements several commonly used network applications like SNTP, DHPv4, DHCPv6, mDNS, HTTP(S), MQTT out-of the box.
1.2. Block diagram Figure 1: Block diagram 1.3. Ordering information WE order code Former order code Description 2610011025000 AMB5201-TR WLAN module in T&R packaging 2610011025009 AMB5201-DEV 3 pcs WLAN module 2610019225001 AMB5201-EV EV kit for WLAN module Table 1: Ordering information Calypso reference manual version 1.2 www.we-online.
2. Electrical specifications Unless otherwise stated, all the values given here were measured on the Calypso evaluation board under the following conditions:T=25°C, VDDS=3.6V, internal DC-DC converter active and 50 Ω conducted. 2.1. Recommended operating conditions Description Min. Typ. Max. Unit VCC 2.1 3.3 3.
Min Description Typ. Max Unit TX current consumption at max output power 230 mA RX current consumption 76 mA Low power mode 10 µA Peak calibration current, VCC=2.1V 670 mA Peak calibration current, VCC=3.3V 450 mA Table 4: Power consumption 2.4. Radio characteristics Description Min Max output power Input sensitivity (1 Mbit) Max Unit 16 18 dBm -92 dBm Max input level, 802.11b -4 dBm Max input level, 802.11g -10 dBm Frequencies -94 Typ.
Standard Modulation and coding Peak Data rate 802.11b DBPSK(DSSS) DQPSK(DSSS) DQPSK(CCK) DQPSK(CCK) 1 Mbps 2 Mbps 5.5 Mbps 11 Mbps 802.11g BPSK(OFDM) coding rate 1/2 BPSK(OFDM) coding rate 3/4 QPSK(OFDM) coding rate 1/2 QPSK(OFDM) coding rate 3/4 16-QAM(OFDM) coding rate 1/2 16-QAM(OFDM) coding rate 3/4 64-QAM(OFDM) coding rate 2/3 64-QAM(OFDM) coding rate 3/4 6 Mbps 9 Mbps 12 Mbps 18 Mbps 24 Mbps 36 Mbps 48 Mbps 54 Mbps 802.
2.5. Pin characteristics Min Property Typ. RF Pin input voltage Max Unit 2.1 V GPIO Voltage Input high 0.65 × VCC VCC V GPIO Voltage Input low -0.5 0.35 × VCC V GPIO Voltage Output high 0.8 × VCC VCC V GPIO Voltage Output low 0 0.2 × VCC V /RESET Voltage Input low 0.6 V Pin output current sunk by any I/O and control pin, drive mode dependant 2 mA Pin output current sourced by any I/O and control pin, drive mode dependant 2 mA Table 7: Pin characteristics 2.6.
Tx power index TX power [dBm] Average current [mA] 0 13.97 260.15 1 12.59 255.95 2 11.62 249.5 3 11.53 251.17 4 10.57 189.35 5 9.47 184.4 6 8.93 182.3 7 8.96 182.3 8 8.89 182.27 9 8.88 182.22 10 8.81 182.29 11 8.86 182.2 12 8.88 182.17 13 8.89 182.18 14 8.92 182.2 15 8.93 182.11 Table 8: TX power vs current consumption, conducted measurement of continuous data transmission, rate 1Mbps (DSSS) Calypso reference manual version 1.2 www.we-online.
Tx power index TX power [dBm] Average current [mA] 0 11.74 119.74 1 10.48 118.95 2 9.46 118.36 3 8.36 117.91 4 8.87 103.10 5 8 102.29 6 6.80 101.73 7 5.83 101.29 8 4.93 100.84 9 3.93 100.59 10 2.88 100.30 11 1.98 100.18 12 1.09 100.02 13 0.75 100 14 0.73 100 15 0.64 100 Table 9: TX power vs current consumption, conducted measurement of continuous data transmission, rate 54Mbps (OFDM) Calypso reference manual version 1.2 www.we-online.
3. Pinout 1 34 23 22 14 13 ANT RF GND VCC STATUS_IND_0 STATUS_IND_1 /RESET RESERVED BOOT APP_MODE_0 APP_MODE_1 RESERVED GND GND RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED RESERVED GND GND /RTS /CTS RESERVED WAKE_UP RESERVED URXD UTXD GND Figure 2: Pinout (top view) Calypso reference manual version 1.2 www.we-online.
No Function Description 1 ANT RF connection to PCB antenna (see section 4.1) 2 RF 50Ω RF connection to external antenna or onboard antenna via ANT (see section 4.
No Function Description 23 GND Negative supply voltage 24 GPIO10 Unused, output LOW, do not connect if not needed 25 GPIO11 Unused, output LOW, do not connect if not needed 26 GPIO14 Unused, output LOW, do not connect if not needed 27 GPIO15 Unused, output LOW, do not connect if not needed 28 GPIO16 Unused, output LOW, do not connect if not needed 29 GPIO17 Unused, output LOW, do not connect if not needed 30 JTAG_TDI Debug line (locked), do not connect 31 JTAG_TDO Debug line (lo
4. Quick start guide The Calypso WLAN module comes pre-flashed, tested and ready-to-use out-of-the-box. This chapter describes steps to quickly build a prototype system and test the capabilities of the module. 4.1. Antenna connection Calypso ’s smart antenna configuration enables the user to choose between two antenna options: 4.1.1. On-board PCB antenna The Calypso has an on-board PCB antenna optimzed for operation in the 2.4 GHz band.
4.3. Power up Set and hold the /RESET pin to LOW. After the supply voltage to the module has stabilized, the /RESET pin shall be held LOW level for another ∆t of at least 200 ms to ensure a safe start-up. Before releasing the /RESET pin, make sure that the appropriate voltage levels are applied on pins App_Mode_0 and App_Mode_1 according to the desired application mode (see 5.2). Also make sure that the host’s UART TX line to the module is configured as a logic HIGH level during module boot-up.
4.5. Quick start example This section is intended to help the user set-up a quick WLAN network consisting of an access point and two Calypso modules and exchange data between the two modules. Minimal pin and antenna connections have to be done on both the modules as described in sections 4.2 and section 4.1. It is recommended to use the Calypso evaluation kit for quick tests. 4.5.1. Prerequisites The following hardware is required to go through the quick start example. 1. Two Calypso evaluation boards. 2.
Figure 4: Quick start setup 4.5.4. Start-up 1. Connect the Calypso EV boards to the laptop/PC via USB. 2. The power LED indicates that supply voltage is active. The FTDI driver for the converter IC on the evaluation board has to be installed and/or updated. On correct driver installation, the EV board appears as a virtual COM port. 3. Open an instance of the serial port emulator with COM port settings 921600 baud, 8e1 for each WLAN module connected to the PC via USB. 4.
+ e v e n t s t a r t u p :2610011025000 ,0 x31000019 , c8 : f d : 1 9 : 0 5 : 5 4 : b4 , 1 . 0 . 0 4.5.5. Connect to an access point 1. In this example an access point with the following settings is used. SSID : WE_calypso Security method : WPA2_PSK Key : calypsowlan 2. Type in the following command into the terminal to connect to the access point.
3. Now the server listens for connection request on the specified port with the following command. AT+ l i s t e n =0 ,10 OK 4.5.7. Creating a TCP client Module B should be configured as a TCP client 1. Create a TCP socket using the following command. The modules returns a socket ID. AT+ s o c k e t =INET ,STREAM, TCP +socket :0 OK 2. Initiate the connection to the server with a connect command with the correct server address and port. AT+connect =0 ,INET , 8 8 8 8 , 1 9 2 . 1 6 8 . 1 .
5. Receiving the message at A AT+ r e c v =1 ,0 ,5 OK +recv :1 ,0 ,5 , h e l l o OK Calypso reference manual version 1.2 www.we-online.
5. Functional description The Calypso WLAN module is intended to be used as a radio sub-system in order to provide WLAN (IEEE 802.11) communication capabilities to system. The UART acts as the primary interface between the module and a host micro-controller. The module can be fully configured and operated using a set of AT-commands over UART. Once configured, the module independently manages WLAN connectivity allowing the host controller to utilize its resources elsewhere.
5.2. Modes of operation When active, the Calypso can be in one of the following operation modes. The transition to/from the modes occurs due to one of the following reasons. • Command from the host. • Position of the App_Mode_x pins during boot up • /Reset signal • WAKE_UP signal or time event Figure 5: Modes of operation Calypso reference manual version 1.2 www.we-online.
5.2.1. BootUp Based on the voltage level on the pins App_Mode_0 and App_Mode_1, the module boots up in one of the following modes. APP_MODE_1 APP_MODE_0 Description 0 0 AT command normal mode, see chapter 7 0 1 OTA mode, see chapter 12 1 0 Provisioning mode, see chapter 9 1 1 AT command terminal mode, see chapter 7 Table 14: Application modes A 0 indicates logic LOW level, 1 indicates logical HIGH level. 5.2.2.
6. Host connection The Calypso is intended to be used as a radio module in a system, interfaced with a host micro-controller. The use of industry standard UART as the primary interface ensures a very minimal requirement set on the host MCU. As a result of this, the module can be designed in with most host controllers from a 8051 to the more advanced ARM core architecture. Figure 6: Host Interface 6.1. UART parameters The Calypso implements the standard UART interface with the following parameters.
6.2. Hardware flow control The hardware flow control is disabled in the standard firmware which leads to a restriction on the UART data rate to 921600 Baud. The UART flow control can only be enabled during firmware creation (i.e. at compile time). A change of the flow control mode during runtime is currently not possible. With the hardware flow control enabled on request (see chapter 14 ) through /RTS and /CTS, the UART baudrate can be increased up to 3 Mbps. 6.3.
7. The command interface The command interface on the Calypso enables full control over the module using ASCII based AT styled commands. In order to support easy integration with a wide range of microcontrollers, two different modes of the command interface are implemented. The user can choose one of the following modes by setting the two APP_MODE_x pins to the corresponding levels as described in section 5.2. 1. Terminal mode : In this mode the module behaves like a standard serial terminal.
• Commands can have parameters in which case the delimiter "=" separates the command name from the list of parameters. • AT commands can be entered in upper or lower case with optional whitespace between the arguments. • Further, each parameter is separated from the next with a "," delimiter. A comma shall not be followed by a whitespace. • In cases where a parameter is optional or ignored, it could be left empty. Nevertheless the "," delimiter has to be present. An empty parameter looks like "„".
8. AT commands In this chapter, various commands used to configure and control the Calypso module are described. 8.1. Device commands The commands under device category provide access to generic module properties like communication interface, time and date settings and version information. Additionally, basic device operations like start, stop, reboot and sleep are described in this section. 8.1.1. Start and stop commands The start and stop commands control the state of the 802.
Request Response AT+test OK or error code Arguments: None Arguments: None Table 18: AT+test 8.1.3. Reboot This command performs a software reset on the module. The module internally puts the NWP to hibernate before restarting from the reset vector. Request Response AT+reboot OK or error code Arguments: None Arguments: None Table 19: AT+reboot It is recommended to use this command whenever possible instead of hard reset (a falling edge on the /Reset pin). 8.1.4.
Factory reset operation can take up to 30 seconds to complete. The module responds with an "OK" only after this time period. Resetting or powering off the module during this operation can result in permanent damage to the module. A reset is performed automatically after the restore operation. 8.1.5. Sleep The sleep command puts the module into the lowest possible power mode (hibernate) resulting in a current consumption of less than 10µA.
Request Response AT+get=[ID],[option] +Get:[value1]...
Request Response AT+set=[ID],[option], [value1],...[valueX] OK (or error) Arguments: ID option values general persistent time 1=enable, 0=disable hh,mm,ss,dd,mm,yyyy UART baudrate parity baudrate (see 6.1) 0=none, 1=even, 2=odd Table 23: AT+set 8.2. WLAN commands In this section, all the commands necessary to configure the WLAN settings of the module are described. 8.2.1. Set mode The Calypso can be operated as a WLAN station, access point or in P2P (Wi-Fi direct) mode.
8.2.2. Scan The scan function enables the user to perform a scan and discover devices on all the enabled channels. The module returns a list of up to 30 devices. The first scan command initiates a scan and hence returns an error code SL_ERROR_WLAN_GET_NETWORK_LIST_EAGAIN (-2073). A further scan command returns the list of available access points Request Response AT+wlanScan=[index],[count] +wlanscan: ...
Request Response AT+wlanConnect=[SSID], [BSSID], [SecurityType], [SecurityKey], [SecurityExtUser], [SecurityExtAnonUser], [SecurityExtEapMethod] OK or error code Arguments: - SSID : Name of the AP - BSSID : MAC address of the AP (optional) - SecurityType: OPEN, WEP, WEP_SHARED ,WPA_WPA2 , WPA_ENT ,WPS_PBC, WPS_PIN - SecurityKey : password (optional if not used) - SecurityExtUser: Enterprise user name parameters (Ignored in case WPA_ENT was not selected) - SecurityExtAnonUser: Enterprise anonymous user n
Request Response AT+wlanProfileAdd=[SSID], [BSSID], [SecurityType], [SecurityKey], [SecurityExtUser], [SecurityExtAnonUser], [SecurityExtEapMethod],[priority] +wlanProfileAdd: OK or error code Arguments: - SSID : Name of the AP - BSSID : MAC address of the AP (optional) - SecurityType: OPEN, WEP, WEP_SHARED ,WPA_WPA2 , WPA_ENT ,WPS_PBC, WPS_PIN - SecurityKey : password (optional if not used) - SecurityExtUser: Enterprise user name parameters (Ignored in case WPA_ENT was not selected) - S
8.2.5. WLAN settings In this section commands to read and modify the WLAN modes in different modes are described. All the WLAN settings are non-volatile. Request Response AT+wlanSet=[ID],[option],[value1],...
Request Response AT+wlanGet=[ID],[option] +Get:[value1]...[valueX] (or error) OK Arguments: Arguments: see table 31 ID option general COUNTRY_CODE STA_TX_POWER SCAN_PARAMS P2P CHANNEL_N_REGS Connection AP Role, Status, security, SSID, BSSID, device name SSID CHANNEL HIDDEN_SSID SECURITY PASSWORD MAX_STATIONS MAX_STA_AGING Table 32: AT+wlanGet 8.2.6.
Request Response AT+wlanPolicySet=[ID],[option],[value] OK (or error) ID option value connection Auto,Fast or P2P scan Hidden_SSID Disable_Scan scan interval in seconds PM Normal, low latency, low power or long sleep Maximum sleep time in ms only for long sleep option P2P CLIENT, GROUP_OWNER, NEGOTIATE ACTIVE, RAND_BACKOFF PASSIVE, Table 33: AT+wlanPolicySet Request Response AT+wlanPolicyGet= [Type] +wlanPolicyGet:[option],[value] or error code Arguments: connection, scan, PM or P2P Ar
• Link-Global IPv6 : The IPv6 global address can be acquired similar to the LLA stateless(MSB 64 bits from RA messages),statefull or static. IPv6 LLA must have a prefix - Fe80::/64 IPv6 global address have a prefix - 2000::/3 Due to its inherent properties, it is recommended not to enable IPv6 addressing in power critical applications.
Request Response AT+NetCfgSet=[ID],[option],[value1],...
8.4. Socket commands Communication between peers in a network is done using sockets. Calypso complies with the industry standard BSD sockets which provides IP based connection interface for data transfer. In this section, all the commands necessary to utilize the socket features are described. 8.4.1.
8.4.1.2. UDP socket UDP does not require a connection to exchange data among network peers. UDP does not have client and server as either can initiate communication by sending a packet with the corresponding destination address (see figure 8). Calypso supports a connection-oriented UDP mode where a client drops all the datagrams except the ones from the connected server. In this case the client work flow is similar to TCP ( see figure 7). Figure 8: UCP socket work flow 8.4.1.3.
Figure 9: SSL/TLS handshake The SSL/TLS protocol requires certificates for authentication and a trusted root certificate catalog to verify the certificates. The calypso provides secure key storage option through the encrypted file system (see section 8.5). A trusted root certificate catalog is present on board with a set of well known trusted root CAs (see appendix C). 8.4.3. Socket operations In this section, the AT commands used to perform various operations on a socket is described.
Request Response AT+socket=[family],[type],[protocol] +socket:[socketID] or error Arguments: - family : INET or INET6 - Type : STREAM or DGRAM - protocol : TCP, UDP or SEC Table 38: AT+socket (create a socket) Request Response AT+close=[socketID] +close:[socketID] or error Arguments: socketID :socket descriptor Table 39: AT+close (close a socket) Request Response AT+bind=[socketID],[family],[localPort],[localAddress] OK or error Arguments: socketID: socket descriptor - family : INET or INET6 -
Request Response AT+connect=[socketID], [family], [remotePort], [remoteAddress] +connect:[remotePort], [remoteAddress] or error Arguments: socketID : socket descriptor family : INET or INET6 remotePort : Port of the peer to connect to remoteAddress : Address to connect to Table 42: AT+connect Request Response AT+accept=[socketID],[family] +accept:[clientSocketID],[family],[clientPort], [clientAddress] or error Arguments: socketID:socket descriptor family : INET or INET6 Table 43: AT+accept Request
Request Response AT+setSockOpt=[socketID],[levle],[option],[value1],...
Request Response level option value IP MULTICAST_TTL: Set the timeto-live value of outgoing multicast packets ADD_MEMBERSHIP:UDP socket, join a multicast group DROP_MEMBERSHIP:UDP socket, leave a multicast group value1: Number of hops Value1: IPv4 multicast address Value2: Multicast interface address Value1: IPv4 multicast address Value2: Multicast interface address Table 46: AT+setSockOpt continued.
Request Response AT+getSockOpt=[socketID],[level],[option] +getSockOpt:[value1],...[valueX] or error Arguments: socketID: socket descriptor level : SOCKET or IP option : see table 45 and 46 timeout usec: Time in microseconds Table 48: AT+getSockOpt 8.4.5. Socket data exchange Once a socket is created and set up the data transfer can be done using send and receive commands using the commands described in this section.
Request Response AT+recvFrom=[socketID],[family],[remotePort], [remoteAddress], [format], [length] +recvFrom:[socketID], [length],[data] or error Arguments: socketID : socket descriptor family : INET or INET6 remotePort : Port of the peer to connect to remoteAddress : Address to connect to format : data format 0=binary, 1=base64 (binary to text encoding) length : Max number of bytes to receive Table 50: AT+recvFrom The module allocates memory for data reception, depending on the length field of the rec
Request Response AT+sendTo=[socketID],[family],[remotePort], [remoteAddress], [format], [length], [data] OK or error Arguments: socketID : socket descriptor family : INET or INET6 remotePort : Port of the peer to connect to remoteAddress : Address to connect to format : data format 0=binary, 1=base64 (binary to text encoding) length : number of bytes to send (max 1460) data: date to send Table 52: AT+sendTo 8.5.
Minimize the number of writes to flash to ensure data endurance A file creation/deletion updates the FAT table. Rewrite/overwrite files when possible Switch off the NWP when performing a file operation Care needs to be taken to have a clean and stable supply voltage especially during flash writes in a battery powered applications. A drop in voltage during a erase cycle may lead to corruption of the file system 8.5.1. File system operations Calypso reference manual version 1.2 www.we-online.
Request Response AT+FileGetFileList +FileGetFileList:[fileName], [maxFileSize], [properties], [fileBlocksAlloc] or error Arguments: fileName : File name maxFileSize : Max file size properties: Bit mask - open_write - open_read - must_commit - bundle_file - pending_commit - pending_bundle_commit - not_failsafe - not_valid - sys_file - secure - nosignature - public_write - public_read fileBlocksAlloc : Allocated blocks Table 53: AT+FileGetFileList 8.5.2.
Request Response AT+fileOpen=[fileName],[options],[fileSize] +fileOpen:[fileID],[secureToke] or error Arguments: fileName : full file path options: READ - Read a file (no bit mask) WRITE - Open for write (optionally bitmask with CREATE) CREATE - Create a new file (optionally bitmask with WRITE or OVERWRITE) CREATE_FAILSAFE CREATE_SECURE CREATE_NOSIGNATURE (for secure files only) CREATE_STATIC_TOKEN (for secure files only) CREATE_VENDOR_TOKEN (for secure files only) CREATE_PUBLIC_WRITE (for secure files
Request Response AT+fileDel=[fileName],[secureToke] OK or error Arguments: FileName: Full path to file secureToken : Token assigend from AT+FileOpen (optional) Table 56: AT+fileDel Request Response AT+fileGetInfo=[fileName],[secureToke] +FileGetInfo:[Flags],[FileSize], [AllocatedSize],[Tokens],[storageSize], [WriteCounter] or error Arguments: FileName: Full path to file secureToken : Token assigend from AT+FileOpen (optional) Table 57: AT+fileGetInfo Request Response AT+fileRead=[fileID],[offset]
Request Response AT+fileWrite=[fileID],[offset],[format],[length], [data] +FileWrite:[numberOfReadBytes] or error Arguments: fileID :ID assigned from AT+FileOpen offset : Offset to specific block Format : 0=binary, 1=Base64 Length : Number of bytes to write Data Table 59: AT+fileWrite The module allocates memory for data read/write depending on the length field of the command. If not enough memory can be allocated an error is returned. We recommend to use a maximum length field of 1460. 8.6.
Request Response AT+netAppStart=[AppBitMap] OK or error Arguments: Bitmap - HTTP_SERVER, DHCP_SERVER, MDNS, DNS_SERVER Table 60: AT+netAppStart Request Response AT+netAppStop=[AppBitMap] OK or error Arguments: Bitmap - HTTP_SERVER, DHCP_SERVER, MDNS, DNS_SERVER Table 61: AT+netAppStop 8.6.2. SNTP client Calypso implements an on-board SNTP client with configurable server addresses. A list of up to three SNTP servers can be stored in the non-volatile memory.
Request Response AT+netAPPSet=[AppID],[option], [value1]...[valueX] OK or error Arguments: AppID : sntp_client Options : - enable, value: 0=disabled, 1=enabled - update_interval, value: minimum update interval in seconds - time_zone, value : UTC +/- minutes - server_address, value1:server index (0-2), value2:server address(IP addresses or URL) Table 63: AT+NetAPPSet Request Response AT+netappUpdateTime OK or error Synchronize device time with SNTP server Table 64: AT+netappUpdateTime 8.6.3.
Request Response AT+HttpDestroy=[index] OK or error Arguments: index - client handle Table 66: AT+HttpDestroy Request Response AT+HttpConnect=[index],[host],[flags],[private key], [cert], [ca] OK or error Arguments: index - client handle host - host name flags - bitmask (ignore_proxy, host_exist) private key - full path (optional) certificate - full path (optional) ca- full path (optional) Table 67: AT+HttpConnect Request Response AT+HttpDisconnect=[index] OK or error Arguments: index - client
Request Response AT+HttpSendReq=[index],[method],[uri],[flags],[format], [length], [data] OK or error Arguments: index - client handle method - get, post, head, options, put, del, connect uri - request URI string flags - chunk_start (Sets the request into chunked body) - chunk_end (Sets the request out of chunked body) - drop_body (Flushes the response body) format - data format for post/put (0=Bin,1=Base64) lenght - length of payload for post/put data - request payload for post/put Table 70: AT+HttpSen
Request Response AT+HttpGetHeader=[index],[option], [format], [length] +HttpGetHeader:[index],[format], [length],[data] Arguments: index - client handle option - see table 74 format - data format(0=Bin,1=Base64) length - max data legth index - client handle format - data format(0=Bin,1=Base64) length - actual data length data - value Table 73: AT+HttpGetHeader Header options res_age, res_allow, res_cache_control, res_connection, res_content_encoding, res_content_language, res_content_length, res_conte
Request Response AT+mqttCreate=[clientID], [flags], [server address], [server port], [security method], [cipher] [private key], [CA], [DH key], [protocol], [blocking send], [data format] +mqttCreate:[index] or error Arguments: index-client handle used for all other MQTT operations -client ID: MQTT client ID string -flags (bit mask): ip4 = IPv4 connection, ip6 = IPv6 connection, url = server address is an URL, sec = secure connection skip_domain_verify, skip_cert_verify, skip_date_verify -server address
Request Response AT+mqttConnect=[index] OK or error Arguments: index: client handle Table 77: AT+MqttConnect Request Response AT+mqttDisconnect=[index] OK or error Arguments: index: client handle Table 78: AT+MqttDisconnect Request Response AT+mqttPublish=[index],[topic],[QOS],[retain], [messageLength],[message] OK or error Arguments: - index: client handle - topic: topic string - QOS: QOS0, QOS1, QOS2 - retain: 0 = do not retain, 1 = retain - message length: max 1460 - message: payload Table 7
Request Response AT+mqttUnsubscribe=[index], [number of Topics], [topic1],[reserved1] ... [topicX],[reservedX] OK or error Arguments: - index: client handle - number of topics: max 4 - topic: topic string - reserved: leave empty Table 81: AT+MqttUnsubscribe Request Response AT+MqttSet=[index],[option], [value1],...
Request Response AT+netAPPPing=[family], [destination], [size], [delay], [timeout], [max], [flags] +netAPPPing:[packetsSent], [packetReceived], [RoundTripTime] or error Arguments: family : INET or INET6 destination : Destination IP address (0 to stop an ongoing ping) size : Size of ping in bytes delay : Delay between pings in milliseconds timeout : Timeout for each ping in milliseconds max : Number of pings to send (0 = forever) flag : 0 = report once all pings are done, 1 = report after every ping, 2=
Event: +eventgeneral=[ID],[value1],...[valueX] ID Values reset_request value1=Code value2=Software module - other - wlan - netcfg - netapp - security error value1=Code value2=Software module - other - wlan - netcfg - netapp - security Table 84: +eventgeneral event 8.7.2. WLAN events The WLAN event may be received in relation to a WLAN connection. Calypso reference manual version 1.2 www.we-online.
Event: +eventwlan=[ID],[value1],...[valueX] ID Values connect value1=SSID value2=BSSID disconnect value1=SSID value2=BSSID value3=Reason, see chapter B.1 sta_added value1=MAC sta_removed value1=MAC p2p_connect value1=SSID value2=MAC value3=GO device name p2p_disconnect value1=SSID value2=MAC value3=Reason, see chapter B.
Event: +eventwlan=[ID],[value1],...[valueX] ID Values provisioning_status value1=Provisioning status value2=Role value3=Status - disconnected - scaning - connecting - connected value4=SSID provisioning_profile_added value1=Provisioning status value2=SSID Table 86: +eventwlan event Calypso reference manual version 1.2 www.we-online.
8.7.3. Socket events The socket event may be received in relation to socket operation. Event: +eventsocket=[ID],[value1],...[valueX] ID Values tx_failed value1=SD value2=Status async_event value1=SD value2=Type - ssl_accept - rx_frag_too_big - other_side_close_ssl - connected_secured - wrong_root_ca value4=SSID value3=Value Table 87: +eventsocket event 8.7.4. NetApp events The NetApp event may be received in relation to network processor operation. Calypso reference manual version 1.2 www.we-online.
Event: +eventnetapp=[ID],[value1],...[valueX] ID Values ipv4_acquired value1=Address value2=Gateway value3=DNS ipv6_acquired value1=Address value2=DNS ip_collision value1=Address value2=DHCP MAC value3=Conflict MAC dhcpv4_leased value1=Address value2=Lease time value3=BSSID dhcpv4_released value1=Address value2=BSSID value3=Reason ipv4_lost value1=Status dhcp_ipv4_acquire_timeout value1=Status ipv6_lost value1=IP lost Table 88: +eventnetapp event 8.7.5.
Event: +eventmqtt=[ID],[value1],...[valueX] ID Values operation value1=Operation ID (connack, puback, suback, unsuback) Connack:value2= 8 bit MSB - ACK flags, 8 bit LSB Return code 0=connection accepted, 1=identifier rejected, 2=server unavailable, 3=bad username/password, 4=not authorised Puback:value2= Packet ID Suback:value2= Packet ID, value3 to valueX=return code per topic.
9. Provisioning To enable easy provisioning when integrated to an embedded system with limited HMI capabilities, the Calypso offers a provisioning mode. In this mode, the module acts as an AP and allows external devices with appropriate credentials to connect and access the on-board HTTPS server. The user can conveniently browse the settings web-page and configure the module using any web-browser. The web pages for provisioning require JavaScript. 9.1.
The domain "calypso.net" is local and hence cannot be verified by known root CAs. Hence, the on-board HTTPS server uses a self-signed certificate. As a result of this, the browser on the configuring device may a report security risk. In this case the user has to trust the certificate and proceed to the website in order to perform the provisioning operation on the WLAN module. Figure 10: Provisioning main page Click on the "Settings" button to open the settings menu.
Figure 11: Provisioning main page Press the button below to add the defined credential to the radio module. The radio module then prints on the UART the corresponding +eventwlan message. +eventwlan : p r o v i s i o n i n g _ p r o f i l e _ a d d e d , n o _ e r r o r , Calypso−P r u e f r o u t e r In default settings the setting "WLAN policy connection" (see chapter 8.2.6) is set to "auto", meaning that the device automatically tries to connect to the AP, that is defined in the module’s profiles.
10. Typical application use cases In this section some of the typical use cases for the Calypso module are considered and a simple example is described in each case. 10.1. UDP communication UDP is a connectionless transport layer protocol used to exchange data between peers in an IP network. Section 8.4 describes the basics of BSD sockets and figure 8 shows the work flow for UDP communication. 10.1.1. Prerequisites The following hardware is required to go through the quick start example. 1.
10.2. TCP communication Refer to section 4.5 for detailed description of creating a TCP server and client and data exchange between them. 10.3. Secure socket communication SSL/TLS layer provides added security features like server authentication and end-to-end encryption. This exampled describes creation of an SSL/TLS server as well as client on Calypso EV board and exchange of data between the two. The following hardware is required to go through the quick start example. 1. Two Calypso evaluation boards.
AT+ b i n d =0 ,INET , 9 9 9 9 , 1 9 2 . 1 6 8 . 1 . 1 4 0 OK AT+ l i s t e n =0 ,10 OK 10.3.2. Create an SSL/TLS client The module with IP address 192.168.1.168 is configured as SSL/TLS client. And connected to the server configured in the previous section. 1. Create a simple TCP socket with the following command. Note the socket ID for future reference. AT+ s o c k e t =INET ,STREAM, TCP +socket :0 2. The next step is to upgrade the socket to secure by updating the socket options.
4. Which is indicated by a +recv event in the client. + r e c v : 0 , 0 , 3 2 , YJaZ4yUGKRES7mE5ApBDo0zrFRtq56Jt OK 5. The client can reply to this message also using the AT+send (with socket ID "0" to address the server). AT+send =0 ,0 ,32 , i u w I H S i s 5 x T t t z f f b t f h j t f h 6 7 8 p S H J A OK 6. Which is indicated by a +recv event in the server with socket ID 1. +recv :1 ,0 ,32 , iuwIHSis5xTttzffbtfhjtfh678pSHJA OK 7. Close the sockets using the command and corresponding Socket ID.
Restart the network processor. AT+ s t o p =0 AT+ s t a r t And scan for P2P devices. AT+wlanscan =0 ,5 As soon as a P2P device has been found, the connection is setup. In case of the group owner, the output is as follows.
+eventwlan : p2p_devfound , calypso , 0 x98 : 0 x84 : 0 xe3 : 0 x f 6 : 0 x8c : 0 x1 , To setup a connection to the found P2P device a AT+wlanconnect command has to be placed, including the name of the peer device using the Push Button Configuration (PBC) for example. AT+wlanconnect=calypso , , P2P_PBC, , , , In case of the group owner, the output is as follows.
+filegetfilelist +filegetfilelist +filegetfilelist +filegetfilelist ... OK : / www/ images / i c o n / menu . png ,3656 ,2 : / www/ images / i c o n / w i r e l e s s . png ,3656 ,2 : / www/ o t a . html ,11848 ,6 : / www/ s e t t i n g s . html ,11848 ,6 To load a file onto the radio module a new file has to be generated on the radio module by using the AT+FileOpen command.
Figure 12: Test page 10.5.3. Accessing the web site in access point mode To configure the radio module as access point we use the command: AT+wlansetmode=AP OK In factory state the SSID of the radio module is "calypso" prepended by its MAC, the password is "calypsowlan" and the domain is "calypso.net". Furthermore, we like to use an own SSID "mySSID" and a new password "mypassword" to access the wireless network.
Figure 13: Test page Please note that the radio module provides up to 4 connections in AP mode. Calypso reference manual version 1.2 www.we-online.
11. Timing parameters This section describes the behaviour of the Calypso module during reset, sleep and wake-up operations. 11.1. Hard reset A hard reset on the Calypso module is done by asserting a low on the /RESET. On hardreset, the module reloads the application from the sFlash after verifying the image to ensure the integrity of the application. This contributes towards higher start up times of the application. Description Typ. Unit Ready after reset 2 sec Table 91: Start-up time 11.2.
12. Firmware update Calypso supports secure over-the-air firmware updates to enable easy update of the module’s firmware in the field. The module as a client connects to an infrastructure AP and a device (PC/tablet/smartphone) present in the same network can upload an encrypted image (provided by Würth Elektronik eiSos ) using the on-board web-server. 12.1. Prerequisites 1. An infrastructure AP with known SSID key for security must be active and connectable.
• In case of WLAN profile 0 being empty or no connection possible, the following message appears on the UART after a timeout of 5s. Please solve the connection issue before continuing. + e v e n t o t a : i n f o , " S t a r t i n g OTA update . . .
Figure 14: OTA webpage 12.2.3. Upload the update-package On the OTA page click on update button followed by choose file button. A file browser opens up. Browse to the location where the update packet is stored and select the same. Click on upload file to start the update process. During update the module outputs the OTA states on the UART. In this state the STATUS_IND_1 LED blinks at 2 Hz. Using browsers other than Chrome, the progress bar is found to not update correctly.
Figure 15: OTA webpage upload Figure 16: OTA in progress Calypso reference manual version 1.2 www.we-online.
12.2.4. Finalize the update On completion, the module outputs the following message on the UART and reboots. + e v e n t o t a : i n f o , " Received OTA f i l e n a m e 20181121135643 _CC3220SF_AMB5201_SerialWiFi_release . t a r , l e n = 440320 " + e v e n t o t a : i n f o , " Download complete " The boot-up after an OTA update may require additional time (up to 60 seconds) in comparison to a normal boot-up. In the browser click on finalize to complete the OTA process. After this step, the ota.
13. Firmware history Version 0.x.x "Engineering" Version 1.0.0 "Release" The Calypso firmware is based on SimpleLink Wi-Fi CC3220 Software development kit (SDK) from Texas Instruments with the corresponding features as well as known issues. The table 93 lists the version of different components used for the current firmware version. Known issues: • Command AT+MqttSet does not work as expected. It will be fixed in subsequent firmware versions. Description Version SimpleLink SDK 2.20.00.
14. Custom firmware 14.1. Custom configuration of standard firmware The configuration of standard firmware includes adoption of the non-volatile Usersettings (see chapter 6) to customer requirements and creating a customized product on base of the standard product with a unique ordering number for a specific customer that needs this configuration. For example if the UART baud rate shall be changed from the default value to another value.
The qualification(s) and certification(s) of the standard firmware cannot be applied to this customer firmware solution without a review and verification. 14.4. Contact for firmware requests Please contact your local field sales engineer (FSE) or wireless-sales@we-online.com for quotes regarding this topics. Calypso reference manual version 1.2 www.we-online.
15. Design in guide 15.1. Advice for schematic and layout For users with less RF experience it is advisable to closely copy the relating evaluation board with respect to schematic and layout, as it is a proven design. The layout should be conducted with particular care, because even small deficiencies could affect the radio performance and its range or even the conformity. The following general advice should be taken into consideration: • A clean, stable power supply is strongly recommended.
Again, no fixed values can be recommended, as they depend on the influencing circumstances of the application (antenna, interferences etc.). Figure 18: Layout • To avoid the risk of short circuits and interference there should be no routing underneath the module on the top layer of the baseboard. • On the second layer, a ground plane is recommended, to provide good grounding and shielding to any following layers and application environment.
Figure 19: Placement of the module with integrated antenna 15.2. Dimensioning of the micro strip antenna line The antenna track has to be designed as a 50Ω feed line. The width W for a micro strip can Figure 20: Dimensioning the antenna feed line as micro strip be calculated using the following equation: W = 1.25 × 5.98 × H e √ 50× r +1.41 87 ! − Tmet (1) Example: A FR4 material with εr = 4.3, a height H = 1000 µm and a copper thickness of Tmet = 18 µm Calypso reference manual version 1.2 www.
will lead to a trace width of W ∼ 1.9 mm. To ease the calculation of the micro strip line (or e.g. a coplanar) many calculators can be found in the internet. • As rule of thumb a distance of about 3×W should be observed between the micro strip and other traces / ground. • The micro strip refers to ground, therefore there has to be the ground plane underneath the trace. • Keep the feeding line as short as possible. 15.3.
15.3.2. Chip antenna There are many chip antennas from various manufacturers. The benefit of a chip antenna is obviously the minimal space required and reasonable costs. However, this is often at the expense of range. For the chip antennas, reference designs should be followed as closely as possible, because only in this constellation can the stated performance be achieved. 15.3.3. PCB antenna PCB antenna designs can be very different.
15.3.4. Antennas provided by Würth Elektronik eiSos 15.3.4.1. 2600130011 - Helike - 169 MHz dipole antenna Figure 21: 169 MHz dipole-antenna Specification Value Frequency range [MHz] 169 Impedance [Ω] 50 VSWR ≤ 2.1 Gain [dBi] 1 Dimensions (L x d) [mm] 320 x 15 Weight [g] 42 Connector SMA plug Operating Temp. [°C] -40 – +85 This antenna requires a ground plane which will influence the electrical parameters. Calypso reference manual version 1.2 www.we-online.
15.3.4.2. 2600130041 - Herse - 434 MHz dipole antenna Figure 22: 434 MHz dipole-antenna Specification Value Frequency range [MHz] 433 Impedance [Ω] 50 VSWR ≤ 1.5 Polarization Vertical Radiation Omni Gain [dBi] 0 Antenna Cover TPEE Dimensions (L x d) [mm] 90 x 12 Weight [g] 9.6 Connector SMA plug Operating Temp. [°C] -40 – +80 This antenna requires a ground plane which will influence the electrical parameters. Calypso reference manual version 1.2 www.we-online.
15.3.4.3. 2600130081 - Hyperion-I - 868 MHz dipole antenna Figure 23: 868 MHz dipole-antenna Ideally suited for applications where no ground plane is available. The 2600130081 antenna can be also used for 902MHz - 928MHz range. Specification Value Center frequency [MHz] 868 Frequency range [MHz] 853 – 883 Wavelength 0.5 wave VSWR ≤ 2.0 Impedance [Ω] 50 Connector SMA (Male) Dimensions (L x d) [mm] 142 x 10 Peak gain [dBi] -2.3 Operating temp.
15.3.4.4. 2600130082 - Hyperion-II - 868 MHz magnetic base antenna Well suited for applications where the RF is lead through a metal wall that could serve as ground plane to the antenna. Figure 24: 868 MHz magnet foot antenna with 1.5 m antenna cable The 2600130082 is a kind of λ/4 radiator and therefore needs a ground plane at the feeding point. Specification Value Frequency range [MHz] 824 – 894 VSWR ≤ 2.
15.3.4.5. 2600130021 - Himalia - 2.4 GHz dipole antenna Figure 25: 2.4 GHz dipole-antenna Due to the fact, that the antenna has dipole topology there is no need for an additional ground plane. Nevertheless the specification was measured edge mounted and 90° bent on a 100 x 100 mm ground plane. Specification Value Frequency range [GHz] 2.4 – 2.5 Impedance [Ω] 50 VSWR ≤ 2:1 Polarization Linear Radiation Omni-Directional Peak Gain [dBi] 2.8 Average Gain [dBi] -0.
16. Reference design Calypso was tested and certified on the corresponding Calypso evaluation board. For the compliance with the EU directive 2014/53/EU Annex I, the evaluation board serves as reference design. For the FCC it serves as trace design. This is no discrepancy due to the fact that the evaluation board itself does not fall within the scope of the EU directive 2014/53/EU Annex I as the module is tested on the evaluation board, which is also the recommended use.
16.1. EV-Board Figure 26: Reference design: Schematic, most important parts Calypso reference manual version 1.2 www.we-online.
Figure 27: Reference design: Layout Calypso reference manual version 1.2 www.we-online.
16.2. Design Guide for FCC ID R7T1001102 Figure 28: Close-up Layout Figure 29: Reference design: Stack-up • Top layer is used for routing and filled up with ground except underneath the module and the antenna free area. Calypso reference manual version 1.2 www.we-online.
• Second layer is ground, except the antenna free area. • Third layer is the supply layer, except antenna free area. Some routing is allowed, not dividing the supply layer in to many or to small parts. • Bottom layer is used for routing. Figure 30: Close-up Schematic Two variants of the Calypso are certified: • Using the inside the module integrated PCB antenna. Not placing C1, C14 and C15, but placing 0 Ohm for C13.
16.3. Application mode pins The pins APP_MODE_0 and APP_MODE_1 define at boot time which application mode is used during operation of the module (see chapter 5.2.1). To enable security updates of the firmware and/or HTTP server certificates via radio, the OTA mode or Provisioning mode may be used. To manually switch to OTA mode or provisioning mode, we strongly recommend to make the pins APP_MODE_0 and APP_MODE_1 accessible on the custom PCB.
17. Manufacturing information 17.1. Moisture sensitivity level This wireless connectivity product is categorized as JEDEC Moisture Sensitivity Level 3 (MSL3), which requires special handling. More information regarding the MSL requirements can be found in the IPC/JEDEC J-STD-020 standard on www.jedec.org. More information about the handling, picking, shipping and the usage of moisture/reflow and/or process sensitive products can be found in the IPC/JEDEC J-STD-033 standard on www.jedec.org. 17.2.
Package thickness Volume mm3 <350 Volume mm3 350-2000 Volume mm3 >2000 < 1.6mm 260°C 260°C 260°C 1.6mm - 2.5mm 260°C 250°C 245°C > 2.5mm 250°C 245°C 245°C Table 95: Package classification reflow temperature, PB-free assembly, Note: refer to IPC/JEDEC J-STD-020E It is recommended to solder this module on the last reflow cycle of the PCB. For solder paste use a LFM-48W or Indium based SAC 305 alloy (Sn 96.5 / Ag 3.0 / Cu 0.5 / Indium 8.9HF / Type 3 / 89%) type 3 or higher.
17.2.2. Cleaning Do not clean the product. Any residue cannot be easily removed by washing. Use a "no clean" soldering paste and do not clean the board after soldering. • Do not clean the product with water. Capillary effects can draw water into the gap between the host PCB and the module, absorbing water underneath it. If water is trapped inside, it may short-circuit adjoining pads. The water may also destroy the label and ink-jet printed text on it.
• Do not touch any exposed area of the antenna to avoid electrostatic discharge. Do not let the antenna area be touched in a non ESD-safe manner. • When soldering, use an ESD-safe soldering iron. 17.4. Safety recommendations It is your duty to ensure that the product is allowed to be used in the destination country and within the required environment. Usage of the product can be dangerous and must be tested and verified by the end user.
18. Physical dimensions 18.1. Dimensions Dimensions 19 * 27.5 * 3 mm Table 96: Dimensions 18.2. Weight Weight 3g Table 97: Weight Calypso reference manual version 1.2 www.we-online.
18.3. Module drawing 6,1 18,0 1,5 1,5 13 1 12,0 1,05 14 22 34 0,9 23 16,5 3,0 ±0,2 7,6 19,0 ±0,4 27,5 ±0,4 Figure 32: Module dimensions [mm] Calypso reference manual version 1.2 www.we-online.
18.4. Footprint 20,0 no metal 2,05 12,5 6,1 5,2 0,9 1,5 16,5 18,0 3,9 12,5 1,5 12,0 Figure 33: Footprint and dimensions [mm] Calypso reference manual version 1.2 www.we-online.
18.5. Antenna free area To avoid influence and mismatching of the antenna the recommended free area around the antenna should be maintained. As rule of thumb a minimum distance of metal parts to the antenna of λ/10 should be kept (see figure 33). Even though metal parts would influence the characteristic of the antenna, but the direct influence and matching keep an acceptable level. Calypso reference manual version 1.2 www.we-online.
19. Marking 19.1. Lot number The 15 digit lot number is printed in numerical digits as well as in form of a machine readable bar code. It is divided into 5 blocks as shown in the following picture and can be translated according to the following table. Figure 34: Lot number structure Block Information Example(s) 1 eiSos internal, 3 digits 439 2 eiSos internal, 2 digits 01 3 Hardware version, 3 digits V2.4 = 024, V12.
19.2. General labeling information The module labels may include the following fields: • Manufacturer identification WE, Würth Elektronik or Würth Elektronik eiSos • WE Order Code and/or article alias • Serial number or MAC address • Certification identifiers (CE, FCC ID, IC, ARIB,...) • Barcode or 2D code containing the serial number or MAC address The serial number includes the product ID (PID) and an unique 6 digit number. The first 1 to 3 digits represent the PID, then the ".
20. Information for Ex protection In case the end product should be used in Ex protection areas the following information can be used: • The module itself is unfused. • The maximum output power of the module is 18dBm. • The total amount of capacitivity of all capacitors is 91.1µF. • The total amount of inductivity of all inductors is 15.4µH. Calypso reference manual version 1.2 www.we-online.
21. Regulatory compliance information 21.1. Important notice EU The use of RF frequencies is limited by national regulations. The Calypso has been designed to comply with the R&TTE directive 1999/5/EC and the RED directive 2014/53/EU of the European Union (EU). The Calypso can be operated without notification and free of charge in the area of the European Union. However, according to the R&TTE / RED directive, restrictions (e.g. in terms of duty cycle or maximum allowed RF power) may apply.
21.2. EU Declaration of conformity EU DECLARATION OF CONFORMITY Radio equipment: Calypso / 2610011025000 The manufacturer: Würth Elektronik eiSos GmbH & Co. KG Max-Eyth-Straße 1 74638 Waldenburg This declaration of conformity is issued under the sole responsibility of the manufacturer. Object of the declaration: Calypso / 2610011025000 The object of the declaration described above is in conformity with the relevant Union harmonization legislation: Directive 2014/53/EU and 2011/65/EU.
21.3. FCC Compliance Statement FCC ID: R7T1001102 This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. (FCC 15.19) Modifications (FCC 15.
• A label must be affixed to the outside of the host product with the following statements: This device contains FCCID: R7T1001102 This equipment contains equipment certified under ICID: 5136A-1001102 • The final host / module combination may also need to be evaluated against the FCC Part 15B criteria for unintentional radiators in order to be properly authorized for operation as a Part 15 digital device.
– The OEM must sign the OEM Modular Approval Agreement. – The module must be used with only the following approved antenna(s). 21.6. Pre-certified antennas The Calypso is pre-certified with the following antennas. Product Certified antenna Calypso PCB antenna included in the Calypso Calypso -1 Dipol antenna as specified in chapter 15.3.4.5 It is only possible to connect an antenna by soldering. It is mendatory to follow chapter 16.2 when connecting an antenna.
22. Important information The following conditions apply to all goods within the wireless connectivity product range of Würth Elektronik eiSos GmbH & Co. KG : 22.1. General customer responsibility Some goods within the product range of Würth Elektronik eiSos GmbH & Co. KG contain statements regarding general suitability for certain application areas.
22.5. Product improvements Due to constant product improvement, product specifications may change from time to time. As a standard reporting procedure of the Product Change Notification (PCN) according to the JEDEC-Standard, we inform about major changes in hard- or firmware. In case of further queries regarding the PCN, the field sales engineer, the internal sales person or the technical support team in charge should be contacted. The basic responsibility of the customer as per section 22.1 and 22.
23. Legal notice 23.1. Exclusion of liability Würth Elektronik eiSos GmbH & Co. KG considers the information in this document to be correct at the time of publication. However, Würth Elektronik eiSos GmbH & Co. KG reserves the right to modify the information such as technical specifications or functions of its products or discontinue the production of these products or the support of one of these products without any written announcement or notification to customers.
Würth Elektronik eiSos GmbH & Co. KG products are neither designed nor intended for use in areas such as military, aerospace, aviation, nuclear control, submarine, transportation (automotive control, train control, ship control), transportation signal, disaster prevention, medical, public information network etc. . Würth Elektronik eiSos GmbH & Co. KG must be informed about the intent of such usage before the design-in stage.
24. License agreement for Würth Elektronik eiSos GmbH & Co. KG connectivity product firmware and software Agreement between You and Würth Elektronik eiSos GmbH & Co. KG The following terms of this license agreement for the usage of the Würth Elektronik eiSos GmbH & Co. KG wireless connectivity product firmware are a legal agreement between you and Würth Elektronik eiSos GmbH & Co. KG and/or its subsidiaries and affiliates (collectively, "Würth Elektronik eiSos ").
control, ship control), transportation signal, disaster prevention, medical, public information network etc. You shall inform Würth Elektronik eiSos about the intent of such usage before design-in stage. In certain customer applications requiring a very high level of safety and in which the malfunction or failure of an electronic component could endanger human life or health, you must ensure to have all necessary expertise in the safety and regulatory ramifications of your applications.
24.6. Limitation of liability Any liability not expressly provided by Würth Elektronik eiSos shall be disclaimed. You agree to hold us harmless from any third-party claims related to your usage of the Würth Elektronik eiSos ’ products with the incorporated Firmware. Würth Elektronik eiSos disclaims any liability for any alteration, development created by you or your customers as well as for any combination with other products. 24.7.
A. Wi-Fi certificate The section contains the Wi-Fi certificate for Calypso . Wi-Fi CERTIFIED™ Interoperability Certificate This certificate lists the features that have successfully completed Wi-Fi Alliance interoperability testing. Learn more: www.wi-fi.org/certification/programs Certification ID: WFA81685 Date of Last Certification January 22, 2019 Company Wurth Elektronik eiSos GmbH & CO.
Wi-Fi CERTIFIED™ Interoperability Certificate Certification ID: WFA81685 Page 2 of 2 Security WPA™ – Enterprise, Personal WPA2™ – Enterprise, Personal EAP Type(s) EAP-TLS EAP-TTLS/MSCHAPv2 PEAPv0/EAP-MSCHAPv2 EAP-FAST Wi-Fi CERTIFIED™ b Wi-Fi CERTIFIED™ g Wi-Fi CERTIFIED™ n 2.4 GHz 1 Spatial Stream 2.4 GHz Short Guard Interval Greenfield Preamble Wi-Fi Direct® 2.4 GHz WMM® Wi-Fi Protected Setup™ 2.4 GHz PIN Push-Button (PBC) Calypso reference manual version 1.2 www.we-online.
B. Error codes The section briefly describes the meaning of error codes returned by Calypso in response to commands. B.1.
SL_ERROR_BSD_ENSOCK (−10L ) / * The system l i m i t on t h e t o t a l number o f open socket , has been reached * / SL_ERROR_BSD_EAGAIN (−11L ) / * Try again * / SL_ERROR_BSD_EWOULDBLOCK SL_ERROR_BSD_EAGAIN SL_ERROR_BSD_ENOMEM (−12L ) / * Out o f memory * / SL_ERROR_BSD_EACCES (−13L ) / * Permission denied * / SL_ERROR_BSD_EFAULT (−14L ) / * Bad address * / SL_ERROR_BSD_ECLOSE (−15L ) / * c l o s e s o c k e t o p e r a t i o n f a i l e d t o t r a n s m i t a l l queued packets * / SL_ERROR_BSD_EALREADY
SL_ERROR_BSD_ESEC_PROTOCOL_VERSION (−370L ) / * s s l / t l s a l e r t s * / SL_ERROR_BSD_ESEC_INSUFFICIENT_SECURITY (−371L ) / * s s l / t l s a l e r t s * / SL_ERROR_BSD_ESEC_INTERNAL_ERROR (−380L ) / * s s l / t l s a l e r t s * / SL_ERROR_BSD_ESEC_USER_CANCELLED (−390L ) / * s s l / t l s a l e r t s * / SL_ERROR_BSD_ESEC_NO_RENEGOTIATION (−400L ) / * s s l / t l s a l e r t s * / SL_ERROR_BSD_ESEC_UNSUPPORTED_EXTENSION (−410L ) / * s s l / t l s a l e r t s * / SL_ERROR_BSD_ESEC_CERTIFICATE_UNOBTAIN
SL_ERROR_BSD_ESEC_ASN_RSA_KEY_E (−643L ) / * ASN key i n i t e r r o r , i n v a l i d i n p u t * / SL_ERROR_BSD_ESEC_ASN_OBJECT_ID_E (−644L ) / * ASN o b j e c t i d e r r o r , i n v a l i d i d * / SL_ERROR_BSD_ESEC_ASN_TAG_NULL_E (−645L ) / * ASN t a g e r r o r , n o t n u l l * / SL_ERROR_BSD_ESEC_ASN_EXPECT_0_E (−646L ) / * ASN expect e r r o r , n o t zero * / SL_ERROR_BSD_ESEC_ASN_BITSTR_E (−647L ) / * ASN b i t s t r i n g e r r o r , wrong i d * / SL_ERROR_BSD_ESEC_ASN_UNKNOWN_OID_E (−648L ) / *
SL_ERROR_BSD_ESEC_DOMAIN_NAME_MISMATCH (−722L ) / * peer s u b j e c t name mismatch * / SL_ERROR_BSD_ESEC_WANT_READ (−723L ) / * want read , c a l l again * / SL_ERROR_BSD_ESEC_NOT_READY_ERROR (−724L ) / * handshake l a y e r n o t ready * / SL_ERROR_BSD_ESEC_PMS_VERSION_ERROR (−725L ) / * pre m s e c r e t v e r s i o n e r r o r * / SL_ERROR_BSD_ESEC_WANT_WRITE (−727L ) / * want w r i t e , c a l l again * / SL_ERROR_BSD_ESEC_BUFFER_ERROR (−728L ) / * malformed b u f f e r i n p u t * / SL_ERROR_BSD_ESEC
SL_ERROR_WLAN_TRANSCEIVER_ENABLED (−2072L ) SL_ERROR_WLAN_GET_NETWORK_LIST_EAGAIN (−2073L ) SL_ERROR_WLAN_GET_PROFILE_INVALID_INDEX (−2074L ) SL_ERROR_WLAN_FAST_CONN_DATA_INVALID (−2075L ) SL_ERROR_WLAN_NO_FREE_PROFILE (−2076L ) SL_ERROR_WLAN_AP_SCAN_INTERVAL_TOO_LOW (−2077L ) SL_ERROR_WLAN_SCAN_POLICY_INVALID_PARAMS (−2078L ) SL_ERROR_WLAN_INVALID_COUNTRY_CODE (−2164L ) SL_ERROR_WLAN_NVMEM_ACCESS_FAILED (−2165L ) SL_ERROR_WLAN_OLD_FILE_VERSION (−2166L ) SL_ERROR_WLAN_TX_POWER_OUT_OF_RANGE (−2167L ) SL_ERRO
SL_ERROR_PENDING_TXRX_STOP_TIMEOUT_EXP (−4118L ) / * Timeout e x p i r e d b e f o r e c o m p l e t i n g a l l TX \RX * / SL_ERROR_PENDING_TXRX_NO_TIMEOUT (−4119L ) / * No Timeout , s t i l l have pending TX \ RX * / SL_ERROR_INVALID_PERSISTENT_CONFIGURATION (−4120L ) / * p e r s i s t e n c y c o n f i g u r a t i o n can o n l y be s e t t o 0 ( d i s a b l e d ) o r 1 ( enabled ) * / B.6.
SL_ERROR_FS_WRONG_INPUT_SIZE (−10278L ) SL_ERROR_FS_BUNDLE_FILE_SHOULD_BE_CREATED_WITH_FAILSAFE (−10279L ) SL_ERROR_FS_BUNDLE_NOT_CONTAIN_FILES (−10280L ) SL_ERROR_FS_BUNDLE_ALREADY_IN_STATE (−10281L ) SL_ERROR_FS_BUNDLE_NOT_IN_CORRECT_STATE (−10282L ) SL_ERROR_FS_BUNDLE_FILES_ARE_OPENED (−10283L ) SL_ERROR_FS_INCORRECT_FILE_STATE_FOR_OPERATION (−10284L ) SL_ERROR_FS_EMPTY_SFLASH (−10285L ) SL_ERROR_FS_FILE_IS_NOT_SECURE_AND_SIGN (−10286L ) SL_ERROR_FS_ROOT_CA_IS_UNKOWN (−10287L ) SL_ERROR_FS_FILE_HAS_NOT_B
SL_ERROR_FS_INVALID_LENGTH_FOR_READ (−10339L ) SL_ERROR_FS_WRONG_FILE_OPEN_FLAGS (−10340L ) SL_ERROR_FS_FILE_NOT_EXISTS (−10341L ) SL_ERROR_FS_IGNORE_COMMIT_ROLLBAC_FLAG (−10342L ) / * commit r o l l b a c k f l a g i s n o t supported upon c r e a t i o n * / SL_ERROR_FS_INVALID_ARGS (−10343L ) SL_ERROR_FS_FILE_IS_PENDING_COMMIT (−10344L ) SL_ERROR_FS_SECURE_CONTENT_SESSION_ALREADY_EXIST (−10345L ) SL_ERROR_FS_UNKNOWN (−10346L ) SL_ERROR_FS_FILE_NAME_RESERVED (−10347L ) SL_ERROR_FS_NO_FILE_SYSTEM (−10348L
SL_ERROR_SETUP_FAILURE (−30738L ) SL_ERROR_HTTP_SERVER_ENABLE_FAILED (−30739L ) SL_ERROR_DHCP_SERVER_ENABLE_FAILED (−30740L ) SL_ERROR_WPS_NO_PIN_OR_WRONG_PIN_LEN (−30741L ) Calypso reference manual version 1.2 www.we-online.
C. Root certificate catalog The following list of root CA can be verified using the on-board root certificate catalog.
GeoTrust Global CA GeoTrust Primary Certification Authority - G2 GeoTrust Primary Certification Authority - G3 GeoTrust Primary Certification Authority GeoTrust Universal CA 2 GeoTrust Universal CA GlobalSign ECC Root CA - R4 GlobalSign ECC Root CA - R5 GlobalSign Root CA - R2 GlobalSign Root CA - R3 GlobalSign Root CA Go Daddy Root Certificate Authority - G2 Hellenic Academic and Research Institutions RootCA 2011 Hongkong Post Root CA 1 IdenTrust Commercial Root CA 1 KISA RootCA 1 Microsec e-Szigno Root CA
VeriSign Class 3 Public Primary Certification Authority - G3 VeriSign Class 3 Public Primary Certification Authority - G4 VeriSign Class 3 Public Primary Certification Authority - G5 VeriSign Class 4 Public Primary Certification Authority - G3 VeriSign Universal Root Certification Authority Visa Information Delivery Root CA Calypso reference manual version 1.2 www.we-online.
List of Figures 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. Block diagram . . . . . . . . . . . . . . . . . . . . . . . . Pinout (top view) . . . . . . . . . . . . . . . . . . . . . . Power up . . . . . . . . . . . . . . . . . . . . . . . . . . Quick start setup . . . . . . . . . . . . . . . . . . . . . . Modes of operation . . . . . . . . . . . . . . . . . . . . . Host Interface . . . . . . . . . . . . . . . . . . . . . . .
9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. 56. TX power vs current consumption, conducted data transmission, rate 54Mbps (OFDM) . . . . Pinout . . . . . . . . . . . . . . . . . . . . . . . Minimal pin configuration . . . . . . . . . . . . Quick start addresses and roles . . . . . . . . . Key features . . . . . . . . . . . . . . . . . . . . Application modes . . . .
57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. 80. 81. 82. 83. 84. 85. 86. 87. 88. 89. 90. 91. 92. 93. 94. 95. AT+fileGetInfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AT+fileRead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AT+fileWrite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AT+netAppStart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
more than you expect Internet of Things Contact: Würth Elektronik eiSos GmbH & Co. KG Division Wireless Connectivity & Sensors Rudi-Schillings-Str. 31 54296 Trier Germany Tel.: +49 651 99355-0 Fax.: +49 651 99355-69 www.we-online.
