Hello,
I am trying to establish a link between Radicrafts MBUS3 demoboard and CC1101.I have configured CC1101 as given in Application note AN067 Appendix for S mode.I tried the same configuration with CC1101 demoboard but unable to receive any packets on CC1101.I am sending WMBUS packets for S2 mode from Radicrafts WMBUS demoboard.
Has anyone tried this ?
Did you already try to establish a link between two Radiocrafts Demo Boards?
If this works, the problem must be related to the configuration of CC1101.
All,
CC1101 with RC1180M3 in S and T modes works perfectly fine, I've tested it successfully in both TX and RX directions.
I suggest that you do several tests to find the problem.
Here you can use SRF7 Studio with TRXEB + CC1120/1EM or SRF4EB with CC1110EM board to receive the telegrams sent by the RC1180M3.
I have SRF7 config. files for TRXEB+CC1120 available, which will allow you to receive S- or T-mode telegrams (in HEX, not the Machester or 3-of-6 decoded packet).
What TI HW and SW do you have at hand?
Having more details will help me answer your question.
I am using SmartRF04 Evalation board using CC1101.
I configured CC1101 as given in AN067 for S mode
IOCFG2=0x06IOCFG1=0x2EIOCFG0=0x02 (TX) or 0x00 (RX)FIFOTHR=0x7SYNC1=0x76 (RX) or 0x54 (TX)SYNC0=0x96 (RX) or 0x76 (TX)PKTLEN=0xFFPKTCTRL1=0x0PKTCTRL0=0x0ADDR=0x0CHANNR=0x0FSCTRL1=0x8FSCTRL0=0x0FREQ2=0x21FREQ1=0x65FREQ0=0x6AMDMCFG4=0x6AMDMCFG3=0x4AMDMCFG2=0x5MDMCFG1=0x22MDMCFG0=0xF8DEVIATN=0x47MCSM2=0x7MCSM1=0x30MCSM0=0x18FOCCFG=0x2EBSCFG=0x6DAGCCTRL2=0x4AGCCTRL1=0x9AGCCTRL0=0xB2WOREVT1=0x87WOREVT0=0x6BWORCTRL=0xFBFREND1=0xB6FREND0=0x10FSCAL3=0xEAFSCAL2=0x2AFSCAL1=0x0FSCAL0=0x1FRCCTRL1=0x41RCCTRL0=0x0FSTEST=0x59PTEST=0x7FAGCTEST=0x3FTEST2=0x81TEST1=0x35TEST0=0x9
And sending packet from Radiocrafts demo board MBUS3 in S mode but I am not able to receive anything on CC1101.
Can you please help me with CC1101 configuration ?
Hi,
which SW are you using with SRF4EB?
There is the Packet Sniffer (which will NOT work with CC1101, you will need CC1110EM)!
And there is SRF7 Studio SW: http://www.ti.com/smartrfstudio
Here the Packet RX tab for CC1101 should work - ONLY after you configure it properly.
Things to set are PKTLEN=FIXED and set it to 16 Bytes for the beginning (as you do not know how long the S-mode telegrams are).
Make sure you set in SRF7 868.3MHz and 32.768 kcps set, RX BW=270kHz and the correct SYNC word for S-mode RX (0x76 0x96).
You'll have to play with the CC1101 RF settings a bit but it should work at the end.
Do NOT put the two devices (CC1101 and RC1180) too close to each other (<1m) or in such case use one board with Antenna and the other without.
Good luck!
I am using SmartRF Studio7 with SFR4EB ( CC1101 )
Actually I did not understood what do you mean by this
*/
/*
I am able see the packet in continous RX
But I am not able to receive packet on Packet RX tab.
I am sending packets from RCMBUS3 demo board in S2 mode
0x29, // IOCFG2 GDO2 Output Pin Configuration 0x2E, // IOCFG1 GDO1 Output Pin Configuration 0x00, // IOCFG0 GDO0 Output Pin Configuration 0x70, // FIFOTHR RX FIFO and TX FIFO Thresholds 0x76, // SYNC1 Sync Word, High Byte 0x96, // SYNC0 Sync Word, Low Byte 0x10, // PKTLEN Packet Length (15 bytes) 0x00, // PKTCTRL1 Packet Automation Control 0x00, // PKTCTRL0 Packet Automation Control (Fixed Packet length mode ) 0x00, // ADDR Device Address 0x00, // CHANNR Channel Number 0x08, // FSCTRL1 Frequency Synthesizer Control 0x00, // FSCTRL0 Frequency Synthesizer Control 0x21, // FREQ2 Frequency Control Word, High Byte 0x65, // FREQ1 Frequency Control Word, Middle Byte 0x6A, // FREQ0 Frequency Control Word, Low Byte 0x6A, // MDMCFG4 Modem Configuration 0x4A, // MDMCFG3 Modem Configuration (data rate 32.73013 kBaud) 0x05, // MDMCFG2 Modem Configuration 0x22, // MDMCFG1 Modem Configuration 0xF8, // MDMCFG0 Modem Configuration 0x47, // DEVIATN Modem Deviation Setting (Deviation 47KHz) 0x07, // MCSM2 Main Radio Control State Machine Configuration 0x30, // MCSM1 Main Radio Control State Machine Configuration 0x18, // MCSM0 Main Radio Control State Machine Configuration 0x2E, // FOCCFG Frequency Offset Compensation Configuration 0x6D, // BSCFG Bit Synchronization Configuration 0x04, // AGCCTRL2 AGC Control 0x09, // AGCCTRL1 AGC Control 0xB2, // AGCCTRL0 AGC Control 0x87, // WOREVT1 High Byte Event0 Timeout 0x6B, // WOREVT0 Low Byte Event0 Timeout 0xFB, // WORCTRL Wake On Radio Control 0xB6, // FREND1 Front End RX Configuration 0x10, // FREND0 Front End TX Configuration 0xE9, // FSCAL3 Frequency Synthesizer Calibration 0x2A, // FSCAL2 Frequency Synthesizer Calibration 0x00, // FSCAL1 Frequency Synthesizer Calibration 0x1F, // FSCAL0 Frequency Synthesizer Calibration 0x41, // RCCTRL1 RC Oscillator Configuration 0x00, // RCCTRL0 RC Oscillator Configuration 0x59, // FSTEST Frequency Synthesizer Calibration Control 0x7F, // PTEST Production Test 0x3F, // AGCTEST AGC Test
Can you please look at my register settings and correct me if I am missing some thing or doing some thing wrong ?
Thank You !!!
I've now tested with SRF4EB (Rev1.9) + CC1101EM using SRF7 Studio v1.8.0.
I also couldn't see the packets from the RC module in the Packet RX Tab so far but I didn't spend too much time. But I could make this work in the RF device commands tab, which proves that the CC1101 works and can properly receive the S-mode packets. I have attached a DOC file, with Screenshots for RC and SRF7, so you can see the proper configuration.
You only need to push SRX button (Send RX strobe) and then you should see the change to RSSI:NA.
Then you push the READ RX FIFO button and you should see the screenshot result as I have it in the attached DOC file.
You need for sure change the register PKTLEN to something like 0x10 (from 0xFF), as you do NOT know in advance how long your packet is. You need to decode the first 4 bytes to extract the packet length and then in your SW you can reprogram the FIFO length.
Note that this RX functionality is described in our AN067 AppNote (PDF), the C-code example is provided as well:
http://www.ti.com/general/docs/litabsmultiplefilelist.tsp?literatureNumber=swra234a
I hope this helps!
Could you check to see if the WMBUS module sends the sync work you expect on the receive side?
--PS. Thank you for clicking Verify Answer if this answered your question!