Low Power RF Proprietary Software & SimpliciTI

SIMPLICITI, help with message sizeof!

Berto Otero — Sat, 21 Nov 2009 15:41:47 GMT

Hi,

I'm working with the IAR Workbench, using simpliciti 1.1.0 with the ap_as_data_hub as reference. I have two smartRF04 and six CC2430EM.

I'm trying to develop a star network with one access point and it will have over 20 end devices.

I need to know if I can send a 16 bits message from each end devices to the access point because the simpliciti msg [ ] definition it's 8 bits size.

(smplStatus_t SMPL_Send(linkID_t lid, uint8_t *msg, uint8_t len)).

thanks for your help

Berto

Statically create a connection with SMPL_Commission

R.Nouna — Thu, 07 May 2009 13:57:00 GMT

HI all,

I will use the new properties of SimpliciTI to save more power at Startup time and without linking and joining. Have any one example using the SMPL_commission?.

can I create the connection Table at build time ? if Yes how?

I think I can have different Nodes withe different Adress but some Application port. is it correct?

I use SimpliciTI 1.1.0 with eZ430-RF2500.

Thanks

cc2510 problem of wake up whit sleep timer (samples powemode2.c library swrc117)

Alex — Wed, 18 Nov 2009 09:34:15 GMT

I try to send in low-power PM2 a cc2510 as sample powermode2.c

consumption should be at 35 uA, but after passing a 1.6 mA and no wake up with sleep timer

wake up oonly with a external interrupt

The following is the configuration of the linker
/ / IXDATA
-D_IXDATA_START = 0xF001
-D_IXDATA_END = 0xFDA1

/ / The internal XDATA is used as XDATA.
-D_XDATA_START = _IXDATA_START
-D_XDATA_END = _IXDATA_END

if Set EA = 0 remains low 0.15uA but clearly I can not wake up with the sleep timer

Help please

SimpliciTI 1.1 IAR address setting bug

Dragker — Wed, 18 Nov 2009 14:40:39 GMT

Hi. This forum is a nice place where I have found some solutions earlier that is why I decided to post here one of my own. Today I have faced a problem - I have tried to use construction like

SMPL_Ioctl(IOCTL_OBJ_ADDR, IOCTL_ACT_SET, &lAddr);

to change the addess of the device in SimpliciTI. (I know, it is possible to set the adress in smpl_config.dat, but I will need random address generation that is why I was using this construction)

After it, I had figured out that this construction is not working! If I will call a construction like

SMPL_Ioctl(IOCTL_OBJ_ADDR, IOCTL_ACT_GET, &lAddr2);

immediately after SET, I will get the specified adress back, but if I will try to call it after NWK initialization (I mean SMPL_Init(...) function) the adress would be always 0.0.0.0. (and it looks like it would be used in network) After that, spending on this thing about 4 hours I had find a clue (luckily I had swrc133, where this construction is still working...). As far as I understand, the reason of this problem is the CHANGE IN nwk_globals.c file.

In latest version of function nwk_globalsInit looks like:

void nwk_globalsInit(void)
{

memset(&sAPAddress, 0x00, sizeof(addr_t));
memset(&sMyRAMAddress, 0x00, sizeof(addr_t));

/* populate RAM address from ROM default if it hasn't laready been set
* using the IOCTL interface.
*/
if (!sRAMAddressIsSet)
{
memcpy(&sMyRAMAddress, &sMyROMAddress, sizeof(addr_t));
sRAMAddressIsSet = 1; /* RAM address is now valid */
}

return;
}

in old one:

void nwk_globalsInit(void)
{

memset(&sAPAddress, 0x00, sizeof(addr_t));
if (!sRAMAddressIsSet)
memset(&sMyRAMAddress, 0x00, sizeof(addr_t));

/* populate RAM address from ROM default if it hasn't laready been set
* using the IOCTL interface.
*/
if (!sRAMAddressIsSet)
{
memcpy(&sMyRAMAddress, &sMyROMAddress, sizeof(addr_t));
sRAMAddressIsSet = 1; /* RAM address is now valid */
}

return;
}

After changing new file to old one, it looks the address setting started to work. I hope that this can help if someone would have same problems and that someone from SIMPILITI team would mention this post and remove this bug in next release.

Simpliciti Default Smartrf_settings, baud rate problem

Jose Carmelo Rangel Breña — Sun, 15 Nov 2009 20:30:16 GMT

Hi,
I am working on a data transmission system using simplicities, I need to place 5 measuring equipment within a room of 5x6 meters.

Required to transmit 20 bytes every 5ms or so, and I have modified some delays in the protocol and I reach the baud rate required for the application, I'm working with P2P communication.
But there is a problem when 2 or more peers are operating at the same time, is like an interference between them, is as if each receiver hears the transmission of any information that is not his, then I think the time it takes to process the packet of information not belonging to it, prevents any belonging process package. Due because of protocol layers relevant information that is not from the ID that the receiver expects, discarded information, but the time of reception was already assigned to it, and this causes losst information.

Because I'm using the maximum baud rate allowed by the protocol, I can't add a policy of repeating information or confirmation of received information. Due this once it has established the link between the sensor and its receptor, the download information is in one sense (sensor to RX-device).

To solve this problem I used the SMARTRF_STUDIO to generate configuration files (smartrf_CC2500.h) with different channels and trying to separate their center frequencies to channels that are widely used by wifi as CH5, CH15, CH20, etc..
But still the problem.

l like to know if anyone of you has tended to modify the default parameters brings simplicities in that file, or if anyone has any suggestions to solve this problem.

Thank you in advance for your suggest.

Radio settings (smartrf file)

trewq — Tue, 17 Nov 2009 18:57:15 GMT

I have until now used the same radio as the example in SimpliciTI, but know I changed to a 434Mhz radio.

Which settings in smart RF file is crucial for SimpliciTI to work?

Tried to just make a new file in smart RF studio but now I cannot get any connection between my peers....se file below

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

/* Chipcon */

/* Product = CC1101 */

/* Chip version = A (VERSION = 0x04) */

/* Crystal accuracy = 10 ppm */

/* X-tal frequency = 26 MHz */

/* RF output power = 10 dBm */

/* RX filterbandwidth = 101.562500 kHz */

/* Deviation = 19 kHz */

/* Datarate = 38.383484 kBaud */

/* Modulation = (1) GFSK */

/* Manchester enable = (1) Manchester enabled */

/* RF Frequency = 433.799622 MHz */

/* Channel spacing = 199.951172 kHz */

/* Channel number = 0 */

/* Optimization = - */

/* Sync mode = (2) 16/16 sync word bits detected */

/* Format of RX/TX data = (0) Normal mode, use FIFOs for RX and TX */

/* CRC operation = (1) CRC calculation in TX and CRC check in RX enabled */

/* Forward Error Correction = (0) FEC disabled */

/* Length configuration = (1) Variable length packets, packet length configured by the first received byte after sync word. */

/* Packetlength = 255 */

/* Preamble count = (2) 4 bytes */

/* Append status = 1 */

/* Address check = (0) No address check */

/* FIFO autoflush = 1 */

/* Device address = 0 */

/* GDO0 signal selection = ( 6) Asserts when sync word has been sent / received, and de-asserts at the end of the packet */

/* GDO2 signal selection = (41) CHIP_RDY */

/***************************************************************

* SmartRF Studio(tm) Export

* Radio register settings specifed with C-code

* compatible #define statements.

***************************************************************/

#ifndef SMARTRF_CC1101_H

#define SMARTRF_CC1101_H

#define SMARTRF_RADIO_CC1101

#define SMARTRF_SETTING_FSCTRL1 0x08

#define SMARTRF_SETTING_FSCTRL0 0x00

#define SMARTRF_SETTING_FREQ2 0x10

#define SMARTRF_SETTING_FREQ1 0xAF

#define SMARTRF_SETTING_FREQ0 0x42

#define SMARTRF_SETTING_MDMCFG4 0xCA

#define SMARTRF_SETTING_MDMCFG3 0x83

#define SMARTRF_SETTING_MDMCFG2 0x9A

#define SMARTRF_SETTING_MDMCFG1 0x22

#define SMARTRF_SETTING_MDMCFG0 0xF8

#define SMARTRF_SETTING_CHANNR 0x00

#define SMARTRF_SETTING_DEVIATN 0x34

#define SMARTRF_SETTING_FREND1 0x56

#define SMARTRF_SETTING_FREND0 0x10

#define SMARTRF_SETTING_MCSM0 0x18

#define SMARTRF_SETTING_FOCCFG 0x16

#define SMARTRF_SETTING_BSCFG 0x6C

#define SMARTRF_SETTING_AGCCTRL2 0x43

#define SMARTRF_SETTING_AGCCTRL1 0x40

#define SMARTRF_SETTING_AGCCTRL0 0x91

#define SMARTRF_SETTING_FSCAL3 0xE9

#define SMARTRF_SETTING_FSCAL2 0x2A

#define SMARTRF_SETTING_FSCAL1 0x00

#define SMARTRF_SETTING_FSCAL0 0x1F

#define SMARTRF_SETTING_FSTEST 0x59

#define SMARTRF_SETTING_TEST2 0x81

#define SMARTRF_SETTING_TEST1 0x35

#define SMARTRF_SETTING_TEST0 0x09

#define SMARTRF_SETTING_FIFOTHR 0x47

#define SMARTRF_SETTING_IOCFG2 0x29

#define SMARTRF_SETTING_IOCFG0D 0x06

#define SMARTRF_SETTING_PKTCTRL1 0x04

#define SMARTRF_SETTING_PKTCTRL0 0x05

#define SMARTRF_SETTING_ADDR 0x00

#define SMARTRF_SETTING_PKTLEN 0xFF

#endif

Why there is only 4 REs in a SimpliciTI network？

csg430 — Thu, 05 Nov 2009 03:51:48 GMT

Hello All，Now，I'm Trying to use SimpliciTI，but there is a question about the RE。

Why currently networks are limited to 4 Range Extenders？

Regards

Ive a bad english. Srry！

new problem about simpliciTI device RE?

32 32 — Mon, 16 Nov 2009 06:45:17 GMT

Hi sir:

thanks for your reply and email , and know I have another questions:

First : this RE code, can directly be used to realive the expansion of the distance, do not add the other myself code? I use physical radio ez430-CC2500. this is the part of the code follow:

{ ioctlToken_t t; t.tokenType = TT_LINK;

t.token.linkToken = 0x78563412;

SMPL_Ioctl(IOCTL_OBJ_TOKEN, IOCTL_ACT_SET, &t); //set link token /* enable join context */

SMPL_Ioctl(IOCTL_OBJ_AP_JOIN, IOCTL_ACT_ON, 0); //use link token communiction }

second : If i need more RE ,i found the MAX number of RE is four , how can i do if i need more RE to extend distance? (CC2500) how many EDs can one RE connect?

third : There are more RE and more ED , how about the device of ED to choice the RE which it shoud to connect? I will appreciate for your reply!

some problem about simpliciTI -----------RE(Range Extenders)

32 32 — Fri, 13 Nov 2009 09:30:28 GMT

hello everyone !

i can't understand that how the RE(Range Extenders) works.If you know ,please explain about it exectly!

In addition,what's the MAX distance the simpliciTI procitol support?

If you have some good code about RE(Range Extenders) ,please sent one to we (my email : ayf0715@126.com), Thank you very much!!!

CC2520 at 2397MHz (and other non-802.15.4 frequencies)

pevo — Thu, 12 Nov 2009 18:37:04 GMT

According to its datasheet, CC2520 transceiver supports frequencies beyond what is defined by 802.15.4 -- specifically 2397MHz and 2507MHz.

I would like to test at these frequencies using SimpliciTI, two EDs and a packet sniffer, but Smart RF Studio does not allow me to select non-802.15.4 frequencies.

Is there an easy way to try transmitting at 2397MHz and get the packet sniffer to display the raw packets? (I realize that this is outside of the 802.15.4 spec, but for my application, compliance to the standard isn't required.

Thanks!

CC2510 using Simpliciti to support a 64byte payload

tomassetti — Tue, 10 Nov 2009 18:43:34 GMT

How would I set up Simpliciti to support a 64byte application payload with the CC2510 for a peer to peer connection?

the documentation seems to indicate that the max application payload that Simpliciti can support is 50. is this correct?

thanks for any advice or info.

Steve

Is SimpiciTI designed to take advantage of FEC?

tomassetti — Tue, 10 Nov 2009 23:15:48 GMT

Can FEC be used with a device such as the CC2510 running the SimpliciTI protocol? the documentation indicates that FEC requires a fixed packet length. Is this restriction compatible with SimpliciTI? IF so, is there example code showing how to enable FEC in a SimpliciTI project?

thanks for any info or recommendations

Steve

SimpliciTI and ASK modulation = CRASH????

ardoster — Fri, 13 Nov 2009 10:30:35 GMT

I continue my learning about SimpliciTI and its environment. Right now, I'm trying to run SimpliciTI using ASK modulation. To execute my tests, I'm using the preferred settings for ASK used in SmartRF Studio. Thus: 1,2Kbaud - ASK - 58KHz RX BW.

My surprise is that using this configuration, SimpliciTI doesn't run. I'm using this configuration with the AP Hub Example, which runs correctly using any other configuration different to ASK.

What's the problem? How is possible this? I need to change a parameter in SimpliciTI? What's wrong?

Could you help me, please?

Thanks you in advance

Regards

Download Wireless Sensor Monitor Using the eZ430-RF2500 (Rev. A)

crackmanworld — Wed, 11 Nov 2009 15:09:23 GMT

Hello everybody!

I need to download Wireless Sensor Monitor Using the eZ430-RF2500 (Rev. A), NOT B...REV. A! And i cannot find it...where can i download? I started a projecto with it and i need this version

tkns!

Suggestion for TI: SmartRFStudio on a Notebook PC

ChM — Fri, 13 Nov 2009 06:37:20 GMT

Suggestion: Allow next release of SmartRFStudio to use resizeable window frames, so it can run on a NoteBook-PC with a screen resolution of 1024*600.

Right now the lower part of the screen not possible to view.

(The NoteBook PC is handy to use for field tests)

RFTXRXIF Not Asserted Problem

jcia — Thu, 12 Nov 2009 09:37:59 GMT

Hi All,

I need to write a small RF protocol using the CC1111 Usb Dongle, I have all the USB Communication part done, I am starting the RF part but I have come across a trivial problem, the RFTXRXIF flag is never asserted, here is my code:

    RFTXRXIE = 1;                             //Enable RXTX Interrupt
    IEN2 |= 0x01                                //Enable General RF Interrupt
    RFIM |= IRQ_DONE;                   //Enable Packet Received/Transmitted Interrupt
    RFIF &= ~IRQ_DONE                //Clear Interrupts
    RFST = RFST_STX;                   /* Put radio in TX. */
    /* Wait for radio to enter TX. */
    while ((MARCSTATE & MARCSTATE_MARC_STATE) != MARC_STATE_TX);

           TxLength = sizeof(TxBuffer);

            for(i=0;i < TxLength;i++)
            {
              while(!RFTXRXIF);     //Wait for RFTXRXIF - Radio Ready to Receive Data
               RFTXRXIF = 0;          //Clear RXTX Interrupt Flag
               RFD = TxBuffer[i];     // Send the ith byte of TxBuffer
            }
             while(!(RFIF & IRQ_DONE));     //Wait for TX Complete

My code is stuck on the while(!RFTXRXIF); line, meaning RFTXRXIF is never asserted, could you provide any insight as to why this might be happening?

On my main routine I configure the radio with Freq, Packet length and all the other stuff needed for the radio, I also have :

// Enable interrupts
INT_GLOBAL_ENABLE(TRUE);

right before calling the transmit function.

Thanks for any help you can provide.

- jcia

Arbitrary length field configuration on CC1101

chuckwagon — Wed, 11 Nov 2009 13:29:58 GMT

The following is an excerpt from the CC1101 data sheet. Do we have an example piece of code that shows how to do this? If not, what about a pseudo-code?

Thanks in advance

The packet length register, PKTLEN, can be
reprogrammed during receive and transmit. In
combination with fixed packet length mode
(PKTCTRL0.LENGTH_CONFIG=0), this opens
the possibility to have a different length field
configuration than supported for variable
length packets (in variable packet length mode
the length byte is the first byte after the sync
word). At the start of reception, the packet
length is set to a large value. The MCU reads
out enough bytes to interpret the length field in
the packet. Then the PKTLEN value is set
according to this value. The end of packet will
occur when the byte counter in the packet
handler is equal to the PKTLEN register. Thus,
the MCU must be able to program the correct
length, before the internal counter reaches the
packet length.

How to use the accelerometer from CC2430DB (rev1.3)?

Luke Ng — Wed, 11 Nov 2009 08:44:03 GMT

Hi,

I am trying to write some code for the CC2430DB to get readings from the accelerometer, but i can't find which pin/ADC channel I should poll.

Also, I looked into the sample applications included with zstack 1.4.3 (Sample Application ver 1.2.1).

In my installation directory "..\Texas Instruments\ZStack-1.4.3-1.2.1\Components\hal\target\CC2430DB\"

there is a file defining the ADC HAL of the CC2430DB (hal_adc.c).

In the Constants Definition, it seems there are references to a temperature sensor! (AFAIK there is no temp sensor in CC2430DB, at least for the rev1.3)

:
:
#define HAL_ADC_CHN_GND     0x0c    /* GND */
#define HAL_ADC_CHN_VREF    0x0d    /* Positive voltage reference */
#define HAL_ADC_CHN_TEMP    0x0e    /* Temperature sensor */
#define HAL_ADC_CHN_VDD3    0x0f    /* VDD/3 */
#define HAL_ADC_CHN_BITS    0x0f    /* Bits [3:0] */
:
:

This file could be outdated, I'm not sure, but is there a more updated version of the CC2430DB component files where there are references to obtain readings for the accelerometer? Or does someone know the channel of the ADC I can poll? Thanks!

ez430-RF2500 SimpliciTI 1.1.0 Peer to Peer doesn't seem to compile

Dweinzierl — Tue, 10 Nov 2009 03:31:50 GMT

I am trying to compile the SimpliciTI 1.1.0 Peer to Peer example for ez430-RF2500.

I get a bunch of errors about bsp_board_defs.h, bsp.h, etc. when I try to compile the example "peer-to-peer" files. Almost like the project doesn't have all the include files included properly or the BSP format/architecture changed and this project didn't follow suit.

Is the source for ez430 out of step with SimpliciTI 1.1.0? Are there more includes that should be added to the project or?? I am running IAR4.11 and in the process of upgrading to 4.2.

I was able to compile and run the same example for CC2510 and had it work just fine.

Simple peer to peer with timer-control to the protocol addition ?

travolta fab — Mon, 09 Nov 2009 23:55:48 GMT

Hello Ti E2E community,

I am currently developing an application based on the CC2510-mini dev kit, which is a great deal to start with by the way.

Application development is simple, and already developed for the main big thing which is radio control & protocol thanks to the Simpliciti stack & simple peer2peer example.

In the swru237, ie CC1110 and CC2510 Mini DK Software Example User's Guide document, there is this sentence : "The slave node does not use PM3 to go to sleep after a period without receiving packets like the master node has. This is because it is intended to be on a fixed power source. However, with the introduction of a timer-control to the protocol, this can be implemented." ( extracted from the 5.3.2 Slave mode chapter)

I am looking at transmitting packets like every 5 secs for example, with the slave node off for most of this time, ie not always in RX mode.

Did anyone already have implemented such kind of timer ? what would be the recommendation ? what should the timer be programmed against, ie fixed sleep time value after each received packet ?, etc...

I am not asking for an already made piece of code ( if available great, i'll read it :), i would like to understand what is the best way to implement such a "timer-controlled protocol" in the simple peer to peer project.

Note: I hope the question have not been answered by the way in other post, i've browsed before posting, could not find an answer, if so, feel free to redirect me.

thanks for your support,

best regards,

fab.

CC2500 Current Consumption while sleeping

Dave — Fri, 23 Oct 2009 09:33:56 GMT

Hi everyone,

I was wondering if you could help me. I'm using an MSP430 and a CC2500 on a low power device. The problem I'm having is that the CC2500 is using allot of current while in sleep mode (I've measured it as being 1.49mA). I'm assuming that it's something I'm doing wrong in software because it says in the data sheet that the low power mode should be drawing allot less current.

I'm using the command SMPL_Ioctl(IOCTL_OBJ_RADIO, IOCTL_ACT_RADIO_SLEEP, 0) to put the radio to sleep. The command returns a SMPL_SUCCESS. I can see that the radio is going into some kind of a low power mode because before this command is executed the radio is drawing 3.121mA and after the command it draws 1.49mA, (Note it is in IDLE mode before putting it to sleep). Has anyone else had a similar problem and found a solution?

Dave

Procedure: Configure CC2511 USB Dongle to Monitor SimpliciTI Packets

Spitzer — Sun, 08 Nov 2009 05:04:23 GMT

Normal 0

Monitoring EZ430-RF2500 SimpliciTI Packets using CC2511 USB Dongle

The objective of this procedure is to monitor radio packets produced by the EZ340-RF2500 running the SimpliciTI Protocol. TI’s Packet Sniffer Application provides packet decode and traffic analysis capability but requires a radio platform to demodulate the signals. Since the EZ430-RF2500 platform does not support operation with the packet sniffer application, another radio platform must be selected and configured. The configuration of the radio platform is the subject of this procedure. This is not a unique solution; other radio platforms and flash programmers are available.

One radio platform compatible with both the RF2500 and the Packet Sniffer Application is the CC2511 USB Dongle. However, it is not compatible as shipped and must first be configured in order to communicate with the PC App. The combination of CC Debugger hardware and SmartRF Flash Programmer software will be used to flash the CC2511 USB Dongle with sniffer_fw_ccxx11.hex. The hex file is provided with the packet sniffer application and is found in the installation directory ~\Packet Sniffer\General\Firmware.

Normal 0

Install the Packet Sniffer Application from TI. This provides the application program, hex file for the CC2511 USB Dongle, and the drivers for the CC Debugger.
Install SmartRF Flash Programmer software from TI.
Connect and install the CC Debugger using the accompanying instructions.
Connect the CC2511 USB dongle to the PC USB port. Ignore the “USB Device Not Recognized” warning from the PC.
Connect the CC Debugger to the CC2511 USB Dongle’s Debug port using the 10-pin ribbon cable provided with the CC Debugger. The red wire on the ribbon cable connects to pin 1 of the debug port.
Look for a green LED on the CC Debugger to indicate connection with the CC2511. This communication link must be established to proceed. Push reset buttons and unplug connectors to make this happen.
Launch SmartRF Flash Programmer. The application UI contains tabs across the top for different connection types. Although the first two tabs appear to be valid, this procedure uses the first tab entitled “System-on-Chip”. A single entry appears in the window indicating the chip type as CC2511 and the EB type as CC Debugger. If this entry is not shown in the window, there probably is no connection with the target via the CC Debugger. Go back and try again.
Use the next window down to navigate to the hex file to be burned into the target. This hex file is provided in the Packet Sniffer installation package and is found in the installation directory under ~”\Texas Instruments\Packet Sniffer\General\Firmware\sniffer_fw_ccxx11.hex”.
Select the radio button under Actions for “Erase, program, and verify”.
Click the “Perform Actions” button. The status window should provide feedback for all three activities and indicate success. Also expect a green LED to illuminate on the target board. If not, go back and try again.
Unplug the CC Debugger and Terminate the SmartRF Flash Programmer App. The Dongle is now configured and ready to use.
Launch the Packet Sniffer App. Select the SimpliciTI Protocol and click the Start button. The bottom of the UI contains tabbed pages for configuration. The Setup tab shows a listing of connected devices used to monitor packets. There may be two entries for the CC2511: USB Dongle and CC Debugger. The CC Debugger entry will be present if the CC Debugger is still connected to the PC. Unplug the CC debugger and it will disappear, leaving the USB Dongle. Either way the USB Dongle entry is the desired choice.
Press the Start button at the top of the UI and monitor packets.

Note: "Normal 0" is inserted automatically and is likely a formatting artifact. It is not part of the procedure.

2.4 GHz Spectrum Analyzer w/Chipcon(TI) RSSI

johnw — Thu, 04 Dec 2008 01:58:01 GMT

Hello All,

Isn't is possible to take an existing Chipcon(TI) design with one of the parts that supports RSSI and make a 2.4 GHz Spectrum Analyzer application? You don't have to be modulation locked to get an accurate RSSI measurement, do you?

Regards,
johnw

Issues using SMPL_Unlink() with multiple connected EDs

pevo — Thu, 05 Nov 2009 15:29:10 GMT

Hi. I'm using SimpliciTI 1.1.0 and my code is based on the AP as Data Hub project. My network topology is star with one AP and up to five EDs. My EDs are expected to continuously send packets at a rate known to the AP (and the AP sends periodic heartbeats to each ED). In the scenario where an ED stops transmitting, I would like to Unlink the offending ED, and continue communicating with the other EDs.

My problem occurs when I Unlink an ED and decrement sNumCurrentPeers. Since the Link ID is simply stored in an array, when an ED that loses comm is unlinked then the array might no longer reflect the actual connected peers, and causes problems if I use sNumCurrentPeers in a for-loop to process messages from EDs. I think part of the the problem is that SMPL_Unlink gets passed a just a literal-value and not the linkID_t sLID pointer.

Here's an example:
1. Endpoint devices connect in this order: ED_a, ED_b, ED_c, ED_d, ED_e.
2. Link IDs are allocated by SimpliciTI: ED_a = 1, ED_b = 2, ED_c = 3 ... etc
2. And, sNumCurrentPeers = 5
3. Over time, ED_c loses comm
4. AP application code sends SMPL_Unlink(3) and decrements sNumCurrentPeers--
5. Now, the AP processing loop iterates for(i=0; i<sNumCurrentPeers; i++) { ... SMPL_Receive(sLID[i], msg, &len) ... }
6. Of course, now ED_e (at index 4) is no longer being processed, and ED_c (at index 2) is being sent heartbeats even though it's no longer connected

This issue with unlinking and tracking the number of peers seems like something that SimpliciTI should handle. Of course, I could handle it in my application code using a linked-list structure to record link IDs.

Does the behavior I describe make sense? Is the designer expected to handle this type of situation? Or, am I missing something?

Thanks!

Link ERROR using SRF05_8051 Projects of SimpliciTI 1.1.0

Carlos Jaccoud — Wed, 04 Nov 2009 21:00:59 GMT

When I try to build the Simple_Peer_To_Peer project, using IAR 7.51A and the SimpliciTI SRF05_8051 folder, I receive this Error Message:

Normal 0 21 false false false MicrosoftInternetExplorer4

Linking

Error[e12]: Unable to open file 'C:\Arquivos de programas\IAR Systems\Embedded Workbench 5.3\8051\config\

lnk51ew_cc2530b_PG2_0.xcl'

Error while running Linker

Can someone help me ?