cancel
Showing results for 
Search instead for 
Did you mean: 

Bi-directional communication with STWLC38 / STWBC86 - message buffer always 0's

Hello,

We completed a test of bi-driectional communication of the Proprietary Packet feature (PP) for a mass market client using the STWLC38 (RX) and STWBC86 (TX).

We're able to consistently receive the data of 5 bytes reliability from the RX to the TX. 

In the other direction though, we haven't gotten it to work as the existing bi-directional communication PDF is well, not very specific. 

On the RX side of things, the message buffer at 0x0190 is always filled with 0's, even though 0x0088 interrupt bit 5 (

RX MSG RCVD LTCH) is set to 1.

 

The document states

"The difference here is that STWBC86 does not add the checksum automatically, the user must provide it with the message. The checksum is calculated as a XOR of the message bytes, including the header."

So we assume the message is then constructed as (first byte sent): 1 byte header, 5 bytes message, 1 byte xor

The header is set to 6f in this case, not 5f (?)

0x6f, 0x11, 0x22, 0x33, 0x44, 0x55, 0x7e
 
When the message is inspected on the RX side, at address 0x0190 with a 7 byte read, the contents is always 0. We wait for the interrupt to be latched, which takes about 70ms. We do wait on the TX side for 10ms from the time of interrupt to set the TX message content and send the reply.
 
Anyone ever get this working or expert @willzhou ?
0 REPLIES 0