Author Topic: Serial Communication in WCL.NET  (Read 6681 times)

ashgie

  • Guest
Serial Communication in WCL.NET
« on: December 04, 2008, 02:17:07 PM »
Hey Mike,

We are testing the WCL.NET compared to the previous Bluetooth Framework, and are finding that a lot of the functionality is a lot more stable.
The appliance we use it for is to establish a serial connection. This all goes well, and we receive the stream over bluetooth.
However....
After about 30/40k of data received. The connection stops and upon sending a command to the device we get the exception back that the client is not connected. While the status still indicates that the client is active and connected. This is something we didnt encounter in the previous BT framework, and also via a simple terminal connection we dont encounter this problem.

Here is the code I use to open the port...if you need any more let me know.

Quote
           
mWclClient.BluetoothParams.Address = mBtDevice.Address;
mWclClient.BluetoothParams.Radio = mBtRadio;
mWclClient.BluetoothParams.Service = wclnet.wclUUIDs.SerialPortServiceClass_UUID;

mWclStatus = WS_OPENING;
parent.UpdateStatus("Radio [" + mBtRadio.Name + "] connecting to device [" + mBtDevice.Name(mBtRadio) + "].");
mWclClient.Open();

Greetings,
Marcel

Offline Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3055
  • Karma: 1000
    • Soft Service Company
Re: Serial Communication in WCL.NET
« Reply #1 on: December 04, 2008, 04:58:10 PM »
Good day!

The code looks correct. It is strange that the device drops the connection. Check the services of the device, may be it has more than 1 SPP service and first one drops the connection? Also the demo version has limitaion on send/receive data size.

ashgie

  • Guest
Re: Serial Communication in WCL.NET
« Reply #2 on: December 05, 2008, 12:21:05 PM »
Nope,

We're using the registered version of BS stack and have only one SPP. With BTFX it used to work.....
This is basically the last bit of the product setup we have to do and we're very anxious to be able to market the product.

Greetings...

Marcel

Offline Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3055
  • Karma: 1000
    • Soft Service Company
Re: Serial Communication in WCL.NET
« Reply #3 on: December 05, 2008, 01:45:55 PM »
I mean demo versin of the library.

ashgie

  • Guest
Re: Serial Communication in WCL.NET
« Reply #4 on: December 05, 2008, 02:43:56 PM »
No....registered dev. licence

Offline Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3055
  • Karma: 1000
    • Soft Service Company
Re: Serial Communication in WCL.NET
« Reply #5 on: December 05, 2008, 04:09:58 PM »
Hm. Very strange. I'll check it out.

ashgie

  • Guest
Re: Serial Communication in WCL.NET
« Reply #6 on: December 10, 2008, 01:17:01 PM »
Can you give me an ETA (estimate time of arrival) when you can tell me a bit more?
I have to finish up the R&D within a week and I hope I can tell WCL.NET is the way to go.

Greets

ashgie

  • Guest
Re: Serial Communication in WCL.NET
« Reply #7 on: December 16, 2008, 07:18:23 PM »
any idea?

Offline Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3055
  • Karma: 1000
    • Soft Service Company
Re: Serial Communication in WCL.NET
« Reply #8 on: December 16, 2008, 08:28:59 PM »
Good day!

I have checked the issue and unfortunatelly couldn't simulate it. Can you contact me by MSN to solve the problem online?

ashgie

  • Guest
Re: Serial Communication in WCL.NET
« Reply #9 on: December 17, 2008, 03:17:53 PM »
I've added you to msn...

Offline Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3055
  • Karma: 1000
    • Soft Service Company
Re: Serial Communication in WCL.NET
« Reply #10 on: December 17, 2008, 03:51:55 PM »
MSN is very strange. Just have got your add request (and some others which are about day old) even MSN is turned on always

ashgie

  • Guest
Re: Serial Communication in WCL.NET
« Reply #11 on: January 13, 2009, 10:55:43 AM »
Is that new version out yet?
Or, if not, when will it be?

Offline sander

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
Re: Serial Communication in WCL.NET
« Reply #12 on: January 16, 2009, 10:40:49 AM »
Mike,

We're waiting for news.... Could you please provide an estimate for the release date, as the last one has passed without so much as a word.

Best regards,
Sander

Offline Mike Petrichenko

  • Bluetooth Framework Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 3055
  • Karma: 1000
    • Soft Service Company

Offline sander

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
Re: Serial Communication in WCL.NET
« Reply #14 on: January 16, 2009, 03:11:01 PM »
Why did you not answer my question?

The download page indicates that the wcl.net version is still at 6.0.0.67, released 16.07.2008. When i download this link, I get a rar archive with a setup dated 18.09.2008. Do you want me to believe this is wcl.net version 6.2.0.0????
Also the news section that you linked to clearly indicates that only the VCL version of the new library has been released. There is no news regarding a new wcl.net version.

1- As you know (look in the topic, it says "WCL.NET") I am waiting for the .net version of the library.
2- As you know, we have uncovered a bug in the serial communication of the wcl.net v6.0.0.67. This bug has been discussed with you both in the forum and via msn. I will repeat the bug description: The client stops receiving data within 1 minute; the client indicates connected  = true, but when sending a new command over the link, the exception "client is not connected" is thrown.
3- You were supposed to test this, and see if the issue can be fixed.
4- Documentation for the .net version is missing; you were supposed to release the new version with .net documentation included.

So my question are:
- When will there be a new version of WCL.NET (.NET version)?
- Will this version include the promised documentation?
- When will you verify and fix the bug we have indicated?

Regards,
Sander

 

Sitemap 1 2 3 4 5 6 7 8 9