Hi Troy,
Thanks for you inquiry.
Could you try installing the current Spokes 2.8.2 version from:
Once this is installed please retest the issue and see if you still receive this error message.
If you do, please increase the Plantronics Spokes log level (follow these instructions), and supply us the log file.
Thanks,
Lewis.
This is already installed. I will try increasing the Spokes log level and attach the file.
Hi,
I need to work with Plantronics Blackwire C310 in a Gigabyte tablet model.
In this tablet after some time the talk button stops sending events.
All I need to do is press Talk button a number of times, and it eventually fails.
When it fails, Talk button generates the audible feedback when pressed but DOES NOT generate any of:
DeviceEventSink::TalkPressed
DeviceEventSink::ButtonPressed
DeviceListenerEventSink::ButtonPressed
After the failure occurs it does NOT come back to normal by any number of successive pressings of the Talk button.
But when any of the other buttons (Volume Up, Volume Down or Mute) is pressed one single time the Talk button comes back to normal operation.
The other buttons were not seen failing any time. Only the Talk button presents this failure.
The failure happens when I install the Spokes_RT.msi, but does not happen (or maybe is much more rare) when Full Spokes is installed.
The failure was not seen yet in Lab with some other PC models.
I obtained a log in the level Very High (attached). The test was as follows:
In the tablet I ran SpokesSDKComSample and pressed successively the Talk button until it failed.
Obs: I found out that pressing keyboard space inside the program, somehow makes the failure happen faster.
Then I pressed the inactive Talk button for some times, pressed a Volume button one time and then for some times the "brought back to life" Talk button.
In my test I used Spokes 2.8.38701.2 (both Spokes_RT and full Spokes), and Windows 7 Professional.
Thanks.
Hi Julio,
What you have reported sounds like a possible bug in Spokes_RT. The issue has been referred to our test lab for further investigation.
Thanks for your report and continuous support to PDC.
WEI
.
Hi Lewis,
This is a great news !
Will test it and let you know if everything is ok :-)
cheers
Hi,
An update of the report:
In other tablets, the failure was observed also with the Full Spokes installed.
It is not an issue restricted only to Spokes_RT.msi deployment.
Is there any workaround to this failure I could try while the development does not address this issue ?
Thanks.
Hi Julio,
I am not aware of any work around at this time.. However the good news is it will be fixed in the soon to be released next release of the SDK.
Thank you for your patience.
Wei Chu
HEllo is it possible to enable push to talk on the voyager legend pro Bluetooth headset .
Hi Marco,
Yes - it is possible to use some of the headset state events that can be produced by the Voyager Legend UC to tell your push to talk application to connect.
For example, button presses and/or wearing sensor.
Could you describe to me on what platform your application runs so I can advise the best approach?
We have had a vendor in the past using a button press event for their mobile push-to-talk application...
Thanks,
Lewis.
I have a Voyager Legend without a dongle.
I searched the forum for 'dongle' and from what I read it seems that certain functions won't work without it. e.g. Proximity detection
However I didn't find anything that stated clearly that the SDK absolutely required that the dongle be used.
Could someone please let me know if the dongle is absolutely required?
And if it is, I suppose my next question wil be, 'Does anyone know if the dongle can be purchased separately?'.
Thanks in advance.
Hi Dan,
The short answer is yes, the dongle is needed for the SDK features to work on a Windows PC. We do sell the dongle separately. The dongle is called a BT300. Here is the direct link to where you can find it on our webpage. Plantronics | BT300 .
I am adding or technical expert Lewis Collins for a more detailed answer if needed, but basically, the dongle allows the SDK commands to be passed between headset and computer. Additionally, for use in VoiP and other PC voice communications, the dongle gives an much, much better audio experience, as the voice quality is excellent with the dongle.
Thanks!
Greg.
Hi Dan,
Yes, Greg's answer is a good one. BT300 needed for Plantronics SDK features on Windows and Mac today. You can use the Voyager Legend without a dongle with the native Bluetooth stack of various mobile devices and Apple Mac. This would allow you to utilize Bluetooth audio gateway and HFP (Hands-free-profile) functionality.
Thanks,
Lewis.
Just in case anyone is still having issues with a Single Instance app, if you change the remoting mechanism that is used from an IPC channel to a WCF named pipe (net.pipe://localhost/) then this will enable the Spokes runtime to work.
Regards
Ben
Hi Ben,
Thanks for sharing your tip with everyone! Really appreciated! Cheers!
Greg.
Hello, We're developing a Linux module for the Calisto P240. Could you send me the HID 1.0/2.0 specifications for this device??
Best regards,
Sergio.
I would like to set a sidetone level on a DA40 headset to 0 (zero). Is there a way how to do it via Plantronics SDK?
I have searched through the SpokesSDK reference document, but could not find a method which such a functionality.
Many thanks.
Hi Sergio,
I see Lewis Collins has reached out to you via email.
For other folks looking for information on the resolution of this issue, please refer to the comments section from this post. Interacting with the Plantronics devices without the SDK . To summarize, we don't publicly post the HID Spec, but will review each request on a case-by-case basis.
Thanks!
Hi Ecko,
I am sorry, but our SDK does not currently support sideetone or any other audio volume level control.
Wei Chu
I recently deployed a fix for an integration using the Spokes 2.7 .NET API (didn't want to change the framework version for a fix) and the SDK includes a Plantronics.UC.Uility but the application crashes upon load. I believe it's the COM API (we're restricted to .NET 3.5)
[Error] PlantronicsAddIn.OnLoad:
Top Exception
Type=System.IO.FileNotFoundException
Source=Plantronics.UC.Common
Message=Could not load file or assembly 'Plantronics.Utility, Version=2.8.38701.2, Culture=neutral, PublicKeyToken=a8048bce41894b6e' or one of its dependencies. The system cannot find the file specified.
StackTrace:
at Plantronics.UC.Common.SessionManager.Init()
at Plantronics.UC.Common.SessionManager.get_Instance()
at HeadsetIntegration.PlantronicsAddIn.OnLoad(IServiceProvider serviceProvider)
I do not have this file anywhere, only Plantronics.UC.Utility. I see the version discrepancy, but I didn't see it in the 2.8 SDK either. Unfortunately I'm new to this case so I'm not super familiar with the customer's environment. Is Plantronics.Utility part of a different SDK, or is there something that I'm missing?
Thank you!
Hello,
Could you confirm which Plantronics SDK or Spokes Software version(s) were present on the build machine?
The end-user's machine must have either the same Plantronics SDK or Spokes Software version was used on the build machine, or a newer version, but cannot have an older version.
By the way, the Spokes 2.x COM Service .NET Interop API requires .NET Framework 4.0.
However, the Spokes 2.x Plantronics SDK or Spokes Software itself only request .NET Framework 3.5 (for example if you are not using Spokes .NET Interop API).
Hope it helps, let us know!
Thanks,
Lewis.