Loading Profile...
Tibbo API
What's the deal with using the Tibbo API? I found the code samples in my program install directory and would like to integrate them into my .NET software product. However, I don't seem to be able to compile the examples. Is there any documentation available?
I’m indifferent
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?You've mentioned some program install directory. Which program do you mean?
-
Inappropriate?Thanks for your replies, guys.
This is the Tibbo device server toolkit for the DS202. There's a subfolder called 'samples' which seems to be suggesting you can use tvsp.dll to bypass the tibbo device manager and the virtual COM ports and interact with the DS202s directly from .NET code. This would be ideal because our target market is not tech savvy and the added step of setting up a virtual COM port is often a source of frustration. I tried to run the examples supplied but there's no documentation and it doesn't seem to be working as expected. Is this a product / feature which has been abandoned, or is there a better way of accomplishing my goal?
I had a look at the tibbo basic, but it seems to be more directed towards embedded firmware than the windows interface. Did I miss something? -
Inappropriate?Heya,
Yes, what you're talking about is the VSP's API, which of course has nothing to do with Tibbo BASIC.
Now, the VSPD does have an API, and the samples should basically work. BUT if you already have access to the source code for your client application, we would recommend using direct socket connection, rather than emulated COM ports.
Any reason not to do that? -
Inappropriate?Well the main reason is programmer ability... I've never written code to communicate using sockets before. Is there any documentation surrounding the specifics of talking to the tibbo devices or is it something that should be obvious (if i knew what I was talking about)..?
Sounds like I need to head to google. If you tell me it's possible then that's good enough for me! -
Inappropriate?Basically, it's plain old TCP or UDP socket communications. I don't know what you're coding with (vb?) but just about any example you read online about communicating via sockets is going to be applicable.
The gist of it is opening a connection to a certain IP/port, sending out some stuff, listening for incoming replies.
You can use our DS commands for testing. For example, if you send out the X command (http://docs.tibbo.com/soism/command_x...) you should get a nice, informative reply.
As an initial step, just to get a feel for the commands and working with UDP, you can grab I/O Ninja (http://ninja.tibbo.com) and open a UDP socket and start playing around with the commands until you manage to get the device to reply.
Once you got the device replying within I/O Ninja, you're going to know exactly what you should be sending and how. Then it's just a matter of implementing it via your language's communications facilities, which should be pretty easy (and generic, so you can really google it).
EMPLOYEE
EMPLOYEE
