DLP-RFS-DK DLP Design, DLP-RFS-DK Datasheet
DLP-RFS-DK
Specifications of DLP-RFS-DK
Related parts for DLP-RFS-DK
DLP-RFS-DK Summary of contents
Page 1
... Long Range, Battery-Powered, Multi-Hop Sensor Networks 1.0 INTRODUCTION The DLP-RFS1231 is a low-cost module for transmitting and receiving digital data via radio frequency. All of the DLP-RFS1231’s electronics (including an antenna) reside on a single PCB, and all operational power is derived from a single supply voltage. ...
Page 2
... QUICK-START GUIDE This Quick-Start Guide is designed to work with our DLP-RFS1231 transceiver and DLP-RFS-BATT battery board Development Kit. (The part number for this kit is DLP-RFS-DK.) The kit contains two DLP-RFS1231 transceivers, two DLP-RFS-BATT battery boards and a Tag-Connect adapter for use with the Renesas E1 debugger (purchased separately). ...
Page 3
... A Logic 0 on Switch 1 of the dip switch means that the node will be a gateway or master node. The gateway or master node will set the radio for reception. When a valid packet is received, the packet is output to the USB port, the buzzer is sounded and the green LED on the battery board is flashed. Rev 1.1 (November 2012) DLP-RFS-DK 3 © DLP Design, Inc. ...
Page 4
... No Connect 8 VBAT 9 VBAT 10 RESET# No Connect 11 12 Ground 13 RESET# Ground 14 DLP-RFS1231 Module IO Pins Ground 1 2 TXD1 3 RXD1 4 P20 / ANI0 5 P61 6 P51 / INTP2 / SO11 7 P30 / INTP3 / SCK11 8 P60 9 P120 / ANI19 Rev 1.1 (November 2012 © DLP Design, Inc. ...
Page 5
... Ground 2.5 PROGRAM / DEBUG INTERFACE The Renesas E1 Device Programmer is required for programming and debugging the DLP-RFS1231 module. The E1 can be connected to the module via either the Tag-Connect interface or the standard 14-pin header. [Note that a male header (purchased separately) will need to be soldered to the PCB if the 14-pin header used ...
Page 6
... MECHANICAL 3.1 MECHANICAL DRAWING (Overall dimensions: 1.5 x 2.0 x 1.53 Inches) Note: thou = mils or 0.001 inches. 3.2 MOUNTING OPTIONS The DLP-RFS1231 module can be either surface mounted to a printed circuit board or connected using 0.1-inch spaced headers (0.025 sq-inch posts). Rev 1.1 (November 2012) 6 © DLP Design, Inc. ...
Page 7
... APPLICATION DEVELOPMENT – SimpleRF™ A software library is available for free download upon purchase of the DLP-RFS1231 that demonstrates reading the serial number, transmitting and receiving data packets and setting up simple point-to-point and star networks. The software design is divided into task-specific “managers” and a hardware-specific API. A manager provides specific functions related to the operation of the radio protocol ...
Page 8
... Those functions include firmware for initializing MCU hardware such as timers, communication ports, IO ports, interrupt handlers, etc. The API also has code for controlling these MCU devices during operation such as handling timer interrupts, sending and receiving data over the communication ports Rev 1.1 (November 2012) 8 © DLP Design, Inc. ...
Page 9
... Similar functions exist to register single-shot and elapsed-time events. For details on the Timer Manager functions, refer to Section 5.0.10. 4.1.9 INTERRUPT MANAGER The Interrupt Manager is used to control the enabling and disabling of interrupts, and it ensures that interrupts cannot be inadvertently enabled in nested function calls. Rev 1.1 (November 2012) 9 © DLP Design, Inc. ...
Page 10
... MAC Manager function call. This is only one example of how to implement a wireless sensor application. The potential applica- tions are limitless. Most of the resources of the RL78 MCU are available for the application to use. Rev 1.1 (November 2012) 10 © DLP Design, Inc. ...
Page 11
... TMessageComponent appMessageComponent uint8_t appMessage [64] uint8_t incomingMessageBuffer [64] enum { ... } appAction uint8_t sniffPackets uint16_t txPacketCount uint16_t rxPacketCount uint8_t adcValsIndex uint8_t adcCount uint8_t adcConversionCount uint8_t adcIndexMask uint8_t adcComplete uint16_t adcVals [ADC_ARRAY_SIZE] Rev 1.1 (November 2012) 11 © DLP Design, Inc. ...
Page 12
... Initializes the Message Manager. void msgRelease (uint8_t msgNo) Releases a managed message. uint8_t msgGetNew (void) Gets the handle to a new message. Function Documentation: void msgAdd (TMessageComponent * node, uint8_t msgNo) Adds a new item to the beginning of the message list. Rev 1.1 (November 2012) 12 © DLP Design, Inc. ...
Page 13
... NOTE: TESTS FOR FAILURE MUST TEST AGAINST A RETURN VALUE OF 0xFF. TMessageComponent* msgGetNext (TMessageComponent * currentNode) Gets the address of the next message in the list (front to back) . Parameters: currentNode Current node to use as a reference to get the next node Rev 1.1 (November 2012) 13 © DLP Design, Inc. ...
Page 14
... TMACMsgObject Defines the internal properties of a TMACMsg. union TMACMsg. Defines a MAC-layer message. Typedefs: typedef uint32_t TMACAddress Defines the MAC-layer address type. Enumerations: enum TMACPacketType { kMACUniAck = 0, kMACUniNoAck = 1, kMACMulti = 2, kMACACK = 3 } Defines the MAC-layer message types. Rev 1.1 (November 2012) 14 © DLP Design, Inc. ...
Page 15
... Sends an application packet using the MAC layer. void macReceivePacket (unsigned char *pkt, uint8_t bufferLength, TRxMode mode) Puts the MAC layer into receive mode. uint8_t macGetRXBufferIndex (void) Returns an index to the next byte in the receive buffer after the MAC bytes. Rev 1.1 (November 2012) 15 © DLP Design, Inc. ...
Page 16
... IDLE. 3. Transmission - If macSendPacket or macSendAppPacket is called, the reception is terminated. Once reception is terminated, macReceivePacket must be called again to restart reception. If you are using the NET layer, macReceivePacket() is called automatically when you call netReceivePacket(). Rev 1.1 (November 2012) 16 © DLP Design, Inc. ...
Page 17
... Valid pktType values: # kMACUniAck - Acknowledged Packet # kMACUniNoAck - Unacknowledged Packet # kMACMulti - Multicast Packet The function is blocking and will maintain control of the processor until the packet transmission is complete. Rev 1.1 (November 2012) 17 © DLP Design, Inc. ...
Page 18
... The current distribution contains a receiver-synchronized, 26-channel FHSS algorithm that can be used in addition to a single-frequency DTS mode of operation. Rev 1.1 (November 2012) 18 © DLP Design, Inc. ...
Page 19
... This function initializes the PHY layer. PHYAPI phySetTxChannel (uint8_t channel) Sets the radio transmit channel. PHYAPI phySetRxChannel (uint8_t channel) Sets the radio receive channel. void phySetHopTable (uint8_t tableIndex) Selects one of 256 possible hop tables. Rev 1.1 (November 2012) 19 © DLP Design, Inc. ...
Page 20
... Gets the current transmit channel number. uint8_t phyIsReadyToTransmit (void) Identifies if the PHY is ready to send a message. uint8_t phyIsReadyToReceive (void) Identifies if the PHY is ready to receive a message. Function Documentation: uint8_t* phyGetRxBuffer (void) Gets a pointer to the receive buffer. Rev 1.1 (November 2012) 20 © DLP Design, Inc. ...
Page 21
... In the pattern ISR, the radio will be reprogrammed to look for the actual start of packet sequence, and then the ISR will go into a hard loop looking for the start sequence. If the start sequence is found, a packet is received not found within the preset period of time, the radio is Rev 1.1 (November 2012) 21 © DLP Design, Inc. ...
Page 22
... A short preamble will cause the packet to be sent in DTS (single-channel) mode. A long preamble will cause the packet to be sent in FHSS mode. [See also: phyReceivePacket()] void phySetHopTable (uint8_t tableIndex) Selects one of 256 possible hop tables. Rev 1.1 (November 2012) 22 © DLP Design, Inc. ...
Page 23
... SX1231 radio IC. Generally, these functions would be used by the protocol stack to control the radio. The application would likely not need to call these functions directly, except in the case of automated testing in the manufacturing stage. Data Structures: struct freq_t Rev 1.1 (November 2012) 23 © DLP Design, Inc. ...
Page 24
... Gets the channel frequency in Hz. void rfSetDataPattern (uint8_t patternCount, uint8_t *patternBuffer) Sets up the pattern used for detection by the SX1231 receiver. void rfSendDataByte (unsigned char byte2send) Sends a data byte over the SX1231 radio. Rev 1.1 (November 2012) 24 © DLP Design, Inc. ...
Page 25
... The value of the register is returned by the function. void rfSetChannel (uint8_t channel) Sets the receiver channel and bandwidth. Parameters: channel Receiver channel; this is an indexed channel of 0-35 Rev 1.1 (November 2012) 25 © DLP Design, Inc. ...
Page 26
... SX1231 is in Sleep Mode # xeIDLE - SX1231 is in IDLE Mode # xeTX - SX1231 Mode # xeTXNOMOD - SX1231 Mode with no modulation (used for testing) # xeRX - SX1231 Mode void rfSetPA (uint8_t onOff) Turns the power amp on and off. Rev 1.1 (November 2012) 26 © DLP Design, Inc. ...
Page 27
... If a callback has not been registered, events will be ignored. Enumeration Type Documentation: enum TEventType Event Types - Not all events will propagate up to the application level. Many of the PHY Rx events are handled internally by the protocol stack. Rev 1.1 (November 2012) 27 © DLP Design, Inc. ...
Page 28
... The microcontroller API encompasses all functions necessary to interface with the managed microcontroller resources that are available to the application. This API provides low-level access to the interrupts, SPI, UART and timer. For the most part, these functions are used by other managers to provide higher-level control. Rev 1.1 (November 2012) 28 © DLP Design, Inc. ...
Page 29
... This function is called to configure INTP0 as an interrupt with the desired edge and priority settings. To enable this interrupt, call ucEnableInterrupt(intINTP0). To disable this interrupt, call ucDisableInterrupt(intINTP1). void ucConfigureINTP5 (uint8_t pedge, uint8_t nedge, uint8_t priority) Configures INTP5 as an interrupt. Rev 1.1 (November 2012) 29 © DLP Design, Inc. ...
Page 30
... Pointer to function to be called when the IRQ0 fires This function is called by an external module to subscribe to the IRQ0 event. The caller provides a pointer to an internal function that will handle the event. UCAPI ucINTP5RegisterCallback (TCallback callback) Registers callback function for the INTP5. Rev 1.1 (November 2012) 30 © DLP Design, Inc. ...
Page 31
... Exception Types: Functions void dbgThrowException (TException ex) Throws an exception. void dbgRegisterExceptionCallback (ExceptionCallback func) Registers a callback function to receive notification of exceptions. Rev 1.1 (November 2012) 31 © DLP Design, Inc. ...
Page 32
... Internal error detected during SPI configuration. kExReleasedInvalidTimer - An invalid timer handle was released. kExNoFreeTimerEvents - No more timer event slots are available. kExNoFreeElapsedTimers - No more elapsed timer slots are available. kExInvalidElapsedTimer - Invalid elapsed timer handle specified or not in use. Rev 1.1 (November 2012) 32 © DLP Design, Inc. ...
Page 33
... ExitISR (void) Called on exit from an ISR. Allows the semaphore to behave normally. uint8_t inISR (void) Returns the flag indicating whether we are currently in an ISR. void func1(void) { DisableInterrupts(); doSomething(); EnableInterrupts(); } void main(void) { DisableInterrupts(); func1(); doSomethingElse(); Rev 1.1 (November 2012) 33 © DLP Design, Inc. ...
Page 34
... Registers an elapsed timer. uint16_t tmrGetElapsedTime (uint8_t handle) Gets the elapsed time in milliseconds for the specified elapsed timer handle. void tmrReleaseElapsedTimer (uint8_t handle) Releases a previously registered elapsed timer. void tmrWait (uint16_t milliseconds) Waits a specified number of milliseconds. Rev 1.1 (November 2012) 34 © DLP Design, Inc. ...
Page 35
... Handle to the newly created elapsed timer (or 255 if no timers are available) This function is called to register a one-time timer event. If there are no timer handles available, the function will return 255. Otherwise, the function will return a handle to the newly registered timer event. Rev 1.1 (November 2012) 35 © DLP Design, Inc. ...
Page 36
... Determines if a byte has been received via the UART. uint8_t uart1KBHit (void) uint8_t uart0GetByte (void) Gets a byte from the UART receive buffer. uint8_t uart1GetByte (void) void uart0Initialize (void) Initializes the UART to a known state. Rev 1.1 (November 2012) 36 © DLP Design, Inc. ...
Page 37
... This function will send a "start-of-packet" (0x02) byte, the entire contents of the packet and an "end-of-packet" byte (0x03). The contents of the packet will be encoded to remove special marker byte values (0x00-0x03). [See also: phyGetRxBuffer()] uint8_t uart0SendByte (uint8_t data) Sends a byte using the interrupt-driven UART. Rev 1.1 (November 2012) 37 © DLP Design, Inc. ...
Page 38
... AGENCY IDENTIFICATION NUMBERS Compliance with the appropriate regulatory agencies is essential in the deployment of all transceiver devices. DLP Design has obtained modular approval for this RF product. As such, an OEM need only meet a few basic requirements in order to utilize their end product under this approval. Corresponding agency identification numbers are listed below: Rev 1 ...
Page 39
... PART NUMBER DLP-RFS1231 6.2 EXTERNAL ANTENNAS The DLP-RFS1231 is preapproved for use with both its on-board chip antenna and an external antenna (Part No. 0600-00048 made by Laird Technologies). Connection to the external antenna is made via a u.fl connector. 6.3 FCC/IC REQUIREMENTS FOR MODULAR APPROVAL Any changes or modifications to the DLP-RFS1231’s printed circuit board, on-board antenna or pre-approved external antenna could void the user’ ...
Page 40
... This product and its documentation are supplied on an as-is basis, and no warranty as to their suitability for any particular purpose is either made or implied. DLP Design will not accept any claim for damages whatsoever arising as a result of the use or failure of this product. Your statutory rights are not affected ...
Page 41
ANT 4 XTA VBAT1 VBAT2 VR_ANA VR_DIG VR_PA 5 XTB 9 VSS 3 P124/XT2 4 P123/XT1 VDD ...