did you have a chance to walk through the new puart_control project under app of the new sdk 2.2?
there is a "sample puart control protocol.pdf" inside this project folder that spelled out the use client control.exe and puart_control app to verify your design.
Yes. but I will try it again for double confirm.
please refer to my pm to you.
1 of 1 people found this helpful
We check the Client Control in puart_control. We found no implementation for ID_CANCEL_CONNECT.
DEFPUSHBUTTON "Cancel Connect",ID_CANCEL_CONNECT,195,23,100,14
It is strange.It look like some problem in BT stack.
I also use other case to test the invalid address problem.
Below is my test procedure and I use original puart_control to test.
1. Start Device Discovery.
1.1. The module found 78:a5:04:41:37:9a, and 88:0f:10:49:e1:ad
2. Power off 78:a5:04:41:37:9a
3. Use Connect button to connect 78:a5:04:41:37:9a.
4. We wait until timeout and log show "Scan:0"
5. Start Device Discovery again, Then you will found no function of Device Discovery.
6. I wait 5 min more. We still cannot SCAN. Then I power on the 78:a5:04:41:37:9a
7. The device will connect directly and scan back to normal.
Above is my test, For some exception, the TAG maybe power off or out-of-range after the module scan them. It should be have function to cancel the connect. But "blecen_Conn(NO_CONN, NULL, 0);" seem no useful.
Our SDK is 2.2.
i'm getting a distributor in your region to get in touch with you to look into this issue more closely. an air trace may be more meaningful to pinpoint the issue.
i used my tag3 to discover my sense.
1) Start Device Discovery
2) Found my sense
3) Power off my sense
4) Click "Connect" to try to connect to sense, to no avail of course
5) Wait till Scan:0
6) Start Device Discovery
i was able to repeat the above for a few times...
After I power up my sense, it auto-connects to the tag.
Then, I proceed to do a "Disconnect", with success.
btw, I am using the puart_control.c that comes with SDK 2.2.0 and not the one from my PM.
It is good to have your help.
For your procedures,
In 7), do you have find others devices ? In my case, I cannot find any device even others device are available.
>>> After I power up my sense, it auto-connects to the tag."
Yes, we have same situation (7. The device will connect directly and scan back to normal.).
No try-connect timeout...
Could you prepare two sense (A, B) ?
After try-connect to A (had been power off), could you connect to Sense B ?
Reset can be a work-a-round.
But that also mean that the puart_control cannot support multi-client. After reset the module, others connection will drop in the same time.
Is it possible to provide the patch in next release of WICED ?
i will try again on these scenarios on my thursday as i have customer appointments today.