Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronic Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

API for hardware controlling under Windows

Status
Not open for further replies.

jabidof

Member level 5
Joined
Jul 25, 2003
Messages
80
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,286
Activity points
674
Hello everybody,

I'd like to develop an API to ease the usage of a COM port connected hardware. I'm not sure where to start and I have many issues to be solved before I begin with soft coding.

1. Which programming language shall I use and what consequences will it have? As I said, i'd like to offer the API on the windows platfom, typically for the .NET framework.

2. More generally, to what shall I pay attention when dealing with API programming. I've never done such a development. How does it change from other programming type?

3. Any links to tutorial, books, etc. for API development are greatly appreciated.

Thanks for your help.
 

dharmeshpitroda

Member level 2
Joined
Mar 5, 2007
Messages
46
Helped
5
Reputation
10
Reaction score
1
Trophy points
1,288
Activity points
1,565
I think WINIO and GIVEIO will helps you,

search for it,

its free and gove you direct acess to hardware with this you can do whatever you needed to do with PORT
 

jhbbunch

Full Member level 4
Joined
Feb 21, 2006
Messages
199
Helped
17
Reputation
34
Reaction score
3
Trophy points
1,298
Activity points
2,902
You sound like another case of trying to run before you can walk. Anyway, .NET has a comm class built into it. So if you want to make a dll or API based on an already existing class go ahead but I think you are wasting your time.
 

jabidof

Member level 5
Joined
Jul 25, 2003
Messages
80
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,286
Activity points
674
Partially agreed. Imagine you want to distribute some hardware but not the protocol. A DLL is just what should be developped?
 

Status
Not open for further replies.
Toggle Sidebar

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Top