Apple

Hi David,

sorry, but I’m using BLED112 via Windows. As most of our development here is under Windows, I’m only using the Mac to do the iPhone application.

UPDATE: The value missing error I reported in the second paragraph was due to a bug I introduced. My apologies! So just ignore this part of the message, please.

Using a 20 bytes value, I was able to transmit new values in a 927 to 1060 bytes per second rate. But I need at least a 1440 bytes per second rate to transmitt all my sensor data realtime. How can I improve this?

Kind regards,

Eric Nielsen

From: David Murphy

Sent: Monday, July 02, 2012 3:29 PM

To: Eric Nielsen

Cc: email@hidden

Subject: Re: Bluetooth LE losing indicated values

Hi Eric,

I don't mean to hijack the thread, but I'd be very interested to know if you're using the BLED 112 directly via OS X, and if so how this is achieved.

Thanks,

-David Murphy

On 2 Jul 2012, at 20:06, Eric Nielsen wrote:

Hello.

I’m using iPhone 4S to communicate with Bluegiga’s BLED112 (USB dongle). BLED112 is acting as server, having one indicated characteristic value which the iPhone, as client, receives as is updated. I’ve programed the server side to first send a connection_update command with interval_min and interval_max of 20 ms and 40 ms, wait for new connection_status event, then write to the value once, and then write new values after receiving attclient_indicated events.

At the server side, every new value sent is logged, and at the client side, every value received is also logged. What happens is that for each 2 values sent, iPhone receives only the first one. Or, looking at the server side, for each value iPhone receives, it looks like it is sending two value confirmations. Or, iPhone is losing every other packet. When the server sends the connection_update command, it receives the new connection properties only at the second connection_status event, so I’m gessing iPhone sends its responses twice... How do I solve this?

Also, my tests showed that iPhone receives a maximum of 20 bytes per value -- larger values got truncated. Is that correct?

Kind regards,

Eric Nielsen

References:
	>Bluetooth LE losing indicated values (From: Eric Nielsen <email@hidden>)
	>Re: Bluetooth LE losing indicated values (From: David Murphy <email@hidden>)