Page 2
*************** MUST READ Check for firmware updates Before using the product make sure you use the most recent firmware version, data sheet and user manual. This is especially important for Wireless Connectivity products that were not purchased directly from Würth Elektronik eiSos. A firmware update on these respective products may be required.
Page 4
Technique to spread a message on the radio spread spectrum ® Direct test mode Mode to test Bluetooth specific RF settings. Proteus-e populated on motherboard with USB EV (Board) Evaluation (Board) interface for test and evaluation purpose. Forward error Technique to correct received erroneous radio...
Proteus-e hardware (see chapter 13 ). Ultra small dimensions of 7 x 9 mm including a strongly miniaturized PCB antenna make the Proteus-e ideal for small form factor design. It is possible to connect an external anten- na, in case higher radio ranges are required.
With this, any beacon function can be realized. For more information see chapter 5.7 . Low power position sensing solutions: The TX power of any Proteus-e is always trans- mitted during advertising. With this, distance estimation and position sensing solutions can be realized conveniently.
2. Electrical specifications As not otherwise stated measured on the evaluation board of the Proteus-e with T=25°C, VDD=3V, f=2.44GHz, internal DC-DC converter in use. 2.1. Recommended operating conditions Parameter Min. Typ. Max. Unit Ambient temperature °C Supply voltage (VDD) Supply rise time (0V to 1.7V)
Internal pull ups or pull downs are configured at startup by the firmware installed in the SoC. The pull up on the /RESET pin cannot be disabled by firmware. Pins available to connect an external crystal in custom firmware. The standard firmware of Proteus-e does not implement this function.
UART_ENABLE / MODE_1 LED_1 Figure 7: Minimal pin connections The above image shows the steps to be performed to integrate the Proteus-e into a custom end device. 1. Supply voltage and ground Connect the VDD and GND pins to supply the radio module with power.
Page 24
If the module has to be connected to a PC, a converter (TTL to RS-232 or TTL to USB) has to be used. See chapter Pinout for details on all pins. Please refer to the Proteus-e evaluation board schemes for a reference design Reference design .
4.2. Antenna connection Proteus-e’s smart antenna configuration allows the user to choose between two antenna options. Detailed description on how to use them and what to consider for certification aspects is described in chapter 17 : 4.2.1. On-board PCB antenna The Proteus-e has an on-board PCB antenna optimized for strong miniaturization operating in the 2.4 GHz frequency band.
The quick start example in this chapter demonstrates how the UART communication with the Proteus-e works in command mode. In case the host sends a request message (i.e. CMD_ GET_REQ ) to the radio module, it responds with an confirmation message (i.e. CMD_GET_CNF ).
5. Functional description 5.1. Operation modes The Proteus-e module acts as a slave and can be fully controlled by an external host. The Proteus-e supports the following operating modes: • The command mode, where the Proteus-e can be controlled by the host controller via commands.
5.3. State indication using the LED pins The pin LED_1 of the Proteus-e can be used to determine the module state. The states described in Figure 9 result in the following pin behavior. The pins on the Proteus-e are active high.
The maximum transmission unit can be increased to allow the transmission of larg- er data packets. The Proteus-e allows an MTU of up to 247 bytes, which results in a maximum payload size (MPS) of 243 bytes. Not selecting a higher MTU will use ®...
5.7. Advertising of custom data The content of standard advertising and scan response packets of the Proteus-e is auto- matically defined. To place custom data in the advertising and scan response packet, the Proteus-e implements the user settings RF_AdvertisingData and RF_ScanResponseData .
5.9. Configure the module for low power consumption Depending on the application environment of the Proteus-e, the goal is to find the optimal trade-off between the module’s performance and its power consumption. Therefore, the main settings and operation modes that affect the current consumption are listed below: •...
2 MBit. To switch the phy after the connection has been setup the Proteus-e offers the command CMD_PHYUPDATE_REQ . As response to this request a CMD_ PHYUPDATE_IND is returned from the Proteus-e, that gives feedback if the connection was switched to the new phy, or if the connection partner rejected the request.
When the data is processed by the module a CMD_DATA_CNF is sent to the host. Additionally a CMD_TXCOMPLETE_RSP will follow as soon as the data has been sent. The receiving Proteus-e will get a CMD_DATA_IND message containing the transmitted pay- load data.
7.6. Switching GPIOs by remote control This chapter contains the commands to use the GPIO feature of the Proteus-e. Please refer to chapter 11 for a detailed description. 7.6.1. CMD_GPIO_LOCAL_WRITECONFIG_REQ This command configures the free GPIOs of the radio module. This is necessary to allow local and remote GPIO control.
So con- figure the RF_SecFlags of the peripheral to set the desired security level. When connecting from a Proteus-I,-II,-III to a Proteus-e, be sure that the same secu- rity mode is used.
None description The standard content of the scan response packet of the Proteus-e is automatically defined. This setting allows to put user content in the scan response packet. The value of this user setting is the raw data which is placed without modification in the scan response packet, after the standard content has been removed before.
The standard content of the advertising packet of the Proteus-e is automatically defined. This setting allows to put user content in the advertising packet. The value of this user setting is the raw data which is placed without modification in the advertising packet, after the standard content has been removed before.
® If a Bluetooth LE device (e.g. a smart phone) connects as central to a Proteus-e module (peripheral) and the connection interval settings do not coincide, the Proteus-e requests the smart phone to accept its settings after 5 s. If the cell phone does not accept the settings, it will be requested a further 3 times with a delay of 10 s.
Peripheral detection To establish a connection, the initiating device (central, i.e. smart phone) waits for an advertising packet, which was sent by the peripheral (Proteus-e) to which it wants to connect to. As soon as such an advertising packet has been received, the central sends a connection request to the chosen peripheral.
The following table contains the measured maximum throughput values for user payload. The test setup is as follows: • A Proteus-e radio module and a Proteus-III radio module connected to a fast micro controller (STM32 on NUCLEO-L476RG) • Radio mode as specified in the table below (1 Mbit/s or 2 Mbit/s) •...
UART is transmitted by the Proteus-e to the connected Bluetooth LE enabled device. On the other hand, all data received by radio is send from the Proteus-e to the connected host without additional header data. Since the commands of the com- mand interface are no longer valid, a Proteus-e cannot be configured when running in...
10.3. More information 10.3.1. UART • The data sent to the UART is buffered in the Proteus-e up to a maximum payload of 243 Bytes. When no new byte was received for 20 ms, the data will be transmitted ®...
To use the remote GPIO control feature of the Proteus-e, the GPIOs of interest must be configured first. This can be done in two ways. Either by the local host (see figure 14 ), when ®...
11.1. Supported GPIO_IDs for remote and local control The following GPIOs of the Proteus-e are supported for remote and local access. GPIO_1 SWDIO URXD SWDCLK UTXD BUSY/ /RESET UART_ENABLE MODE_1 LED_1 GPIO_ID Supported functions GPIO_1 Input, Output GPIO_2 Input, Output Table 24: Supported GPIO_IDs Proteus-e reference manual version 0.3...
The UUID is a unique number identifying a Bluetooth LE profile and thus describing its functions. The Proteus-e using its standard UUID is compatible to all devices that imple- ment the SPP-like profile, whichever device it is integrated. To suspend this interoperability, the user settings RF_SPPBaseUUID , RF_SPPServiceUUID , RF_SPPTXUUID and RF_SPPRXUUID can be used to modify the UUID of the SPP-like profile.
14.1. Firmware flashing using the production interface The Proteus-e offers a serial wire debug and programming interface (SWD) for module flash access. This interface can be used by customers to erase the entire chip and install their own firmware.
European Conformity the evaluation board serves as reference design. When reusing Würth Elektronik eiSos FCC or IC certification it is mandatory to follow the trace design. Complete layout and schematic information can be found in the manual of the Proteus-e evaluation board.
Table 29: Weight 19.3. Light sensitivity Inside the Proteus-e a light sensitive WLCSP package is used. This package is sensitive to visible and near infrared light. As the chip is not completely shielded on the sides, any mounting without enclosure could lead to malfunction. This should be taken into account when designing an enclosure for the end device.
Special Interest Group (SIG) must be qualified by the SIG to obtain the corresponding Declaration ID. ® Due to the qualification of the Proteus-e as end product no further Bluetooth tests are re- ® quired. The only arising expenses are those for purchasing a Bluetooth Declaration ID.
R&TTE directive 1999/5/EC and the RED directive 2014/53/EU of the European Union (EU). The Proteus-e can be operated without notification and free of charge in the area of the Eu- ropean Union. However, according to the R&TTE / RED directive, restrictions (e.g. in terms of duty cycle or maximum allowed RF power) may apply.
The OEM must ensure that the following conditions are met. • The Proteus-e will be used at a distance of at least 10 mm. • End users of products, which contain the module, must not have the ability to alter the firmware that governs the operation of the module.
Since the firmware application created by integrators of the Proteus-e cannot be controlled by Würth Elektronik eiSos, the module integrator will have to take over this responsibility. This process is called "change in ID" for FCC and "multiple listing"...
Need help?
Do you have a question about the Proteus-E and is the answer not in the manual?
Questions and answers