From: John B. <jb...@Tr...> - 2005-01-13 11:17:02
|
Hello There has recently been some discussion in info-Labview about a royalty free serial functionality in LabVIEW. I would be interested in working on this. There are already some libraries available, posted by others on the web in different places. I am interested in working on this. Is OpenG a suitable forum for this task? How do I set about it? Yours Sincerely John -- John Brohan National Instruments LabVIEW expert in Montreal Traders Micro "We connect all sorts of things to computers" 317 Barberry Place DDO Montreal PQ Canada H9G 1V3 Tel (514)995-3749 jb...@Tr... http://www.TradersMicro.com |
From: Jim K. <jk...@ja...> - 2005-01-13 17:08:23
|
John, OpenG is a great forum work on such a thing. I can help you get a project started. -Jim > -----Original Message----- > From: ope...@li... > [mailto:ope...@li...] > On Behalf Of John Brohan > Sent: Thursday, January 13, 2005 3:17 AM > To: ope...@li... > Subject: OpenG Serial drivers > > Hello > There has recently been some discussion in info-Labview about > a royalty > free serial functionality in LabVIEW. I would be interested > in working > on this. There are already some libraries available, posted > by others on > the web in different places. I am interested in working on this. Is > OpenG a suitable forum for this task? How do I set about it? > > Yours Sincerely > John > -- > John Brohan National Instruments LabVIEW expert in Montreal > Traders Micro "We connect all sorts of things to computers" > 317 Barberry Place DDO Montreal PQ Canada H9G 1V3 Tel (514)995-3749 > jb...@Tr... http://www.TradersMicro.com > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > OpenGToolkit-Developers mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers > |
From: John B. <jb...@Tr...> - 2005-01-13 19:06:30
|
Hi Jim Thanks for your offer, I have LV 6.1 and I'd like to try to get some royalty free Serial drivers written! How do I start? Yours Sincerely John Jim Kring wrote: > John, > > OpenG is a great forum work on such a thing. I can help you get a project > started. > > -Jim > > > >>-----Original Message----- >>From: ope...@li... >>[mailto:ope...@li...] >>On Behalf Of John Brohan >>Sent: Thursday, January 13, 2005 3:17 AM >>To: ope...@li... >>Subject: OpenG Serial drivers >> >>Hello >>There has recently been some discussion in info-Labview about >>a royalty >>free serial functionality in LabVIEW. I would be interested >>in working >>on this. There are already some libraries available, posted >>by others on >>the web in different places. I am interested in working on this. Is >>OpenG a suitable forum for this task? How do I set about it? >> >>Yours Sincerely >>John >>-- >>John Brohan National Instruments LabVIEW expert in Montreal >>Traders Micro "We connect all sorts of things to computers" >>317 Barberry Place DDO Montreal PQ Canada H9G 1V3 Tel (514)995-3749 >>jb...@Tr... http://www.TradersMicro.com >> >> >>------------------------------------------------------- >>The SF.Net email is sponsored by: Beat the post-holiday blues >>Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. >>It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt >>_______________________________________________ >>OpenGToolkit-Developers mailing list >>Ope...@li... >>https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers >> > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > OpenGToolkit-Developers mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers > -- John Brohan National Instruments LabVIEW expert in Montreal Traders Micro "We connect all sorts of things to computers" 317 Barberry Place DDO Montreal PQ Canada H9G 1V3 Tel (514)995-3749 jb...@Tr... http://www.TradersMicro.com |
From: Jim K. <jk...@ja...> - 2005-01-13 23:25:53
|
John, This project is a great idea. First, it is something that many people need (even if they are not aware of it). Secondly, it addresses LabVIEW licensing issues, which are a hot button right now. To get started, please draft a document that describes: (1) the problem which this project aims to address (2) goals and scope of the project (3) use cases for the software (4) requirements for the software (5) one or more proposed designs and the benefits of the designs with respect to other possible design choices. Don't worry about leaving certain things out of the document. You can simply leave place-holders in the document for content that will be added later. This document will form the basis for others to contribute ideas, and enable us all to have a shared understanding of the problem and an agreed upon solution. I will create a CVS module (a new project in our networked source Code control system) where we can share our project files. Please sign up for an account on SourceForge.net so that I can give you access to the repository. I will do this tonight. In the next week, or so, we will be going live with a new discussion forum at OpenG.org, which will make collaborative discussions a whole lot easier. Once we go live, we can create discussion threads dedicated to this project, and really begin to has out our ideas. Also, please identify and make a list of other project team members so that we can come up with a communication plan and keep everyone in the loop. Personally, I know that there are many companies who would be eager and willing to participate in this project. Let's try to coordinate and get as many people involved as possible. Regards, -Jim Kring John Brohan wrote: > Hi Jim > > Thanks for your offer, I have LV 6.1 and I'd like to try to get some > royalty free Serial drivers written! How do I start? > > Yours Sincerely > John > > Jim Kring wrote: >> John, >> >> OpenG is a great forum work on such a thing. I can help you get a >> project >> started. >> >> -Jim >> >> >> >>>-----Original Message----- >>>From: ope...@li... >>>[mailto:ope...@li...] >>>On Behalf Of John Brohan >>>Sent: Thursday, January 13, 2005 3:17 AM >>>To: ope...@li... >>>Subject: OpenG Serial drivers >>> >>>Hello >>>There has recently been some discussion in info-Labview about >>>a royalty >>>free serial functionality in LabVIEW. I would be interested >>>in working >>>on this. There are already some libraries available, posted >>>by others on >>>the web in different places. I am interested in working on this. Is >>>OpenG a suitable forum for this task? How do I set about it? >>> >>>Yours Sincerely >>>John >>>-- >>>John Brohan National Instruments LabVIEW expert in Montreal >>>Traders Micro "We connect all sorts of things to computers" >>>317 Barberry Place DDO Montreal PQ Canada H9G 1V3 Tel (514)995-3749 >>>jb...@Tr... http://www.TradersMicro.com >>> >>> >>>------------------------------------------------------- >>>The SF.Net email is sponsored by: Beat the post-holiday blues >>>Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. >>>It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt >>>_______________________________________________ >>>OpenGToolkit-Developers mailing list >>>Ope...@li... >>>https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers >>> >> >> >> >> >> ------------------------------------------------------- >> The SF.Net email is sponsored by: Beat the post-holiday blues >> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. >> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt >> _______________________________________________ >> OpenGToolkit-Developers mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers >> > > -- > John Brohan National Instruments LabVIEW expert in Montreal > Traders Micro "We connect all sorts of things to computers" > 317 Barberry Place DDO Montreal PQ Canada H9G 1V3 Tel (514)995-3749 > jb...@Tr... http://www.TradersMicro.com > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > OpenGToolkit-Developers mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers > -- Jim Kring James Kring, Inc. jk...@ja... 415.720.5972 phone 415.366.3299 fax http://www.jameskring.com |
From: Kevin V. <k.v...@ve...> - 2005-01-14 01:12:16
|
I saw this thread start up and I was itching to jump in but I haven't had much time. I started working on something like this a several months back before I got swamped with work. What actually gave me the idea was when I had to recompile the source code for Scantool. net's OBDII interface. Long story short, they use an API for doing serial I/O under DOS, Linux and SunOS called DZComm. Pretty slick. It's on sourceforge: http://dzcomm.sourceforge.net/ My master plan was to use Call Library Nodes to tap into the functions in the libdzcom.so shared library (like with the Comedi library). I made 9 VIs but I don't think I ever tested all of them. I recall a few working... Should be easy to finish all the functions if there's no complex data structures. Here are some other serial port projects that didn't seem to be as useable but worth mentioning: Columbo Simple Serial Library http://sourceforge.net/projects/cssl/ ezV24 http://sourceforge.net/projects/ezv24/ Have fun, kevin |
From: Jim K. <jk...@ja...> - 2005-01-14 03:38:44
|
It might be possible to port DZComm over to Mac OS X, if anyone is willing to do it. -Jim > -----Original Message----- > From: ope...@li... > [mailto:ope...@li...] > On Behalf Of Kevin Valentine > Sent: Thursday, January 13, 2005 5:12 PM > To: ope...@li... > Subject: Re: OpenG Serial drivers > > I saw this thread start up and I was itching to jump in but I > haven't > had much time. I started working on something like this a several > months back before I got swamped with work. What actually gave me > the idea was when I had to recompile the source code for Scantool. > net's OBDII interface. Long story short, they use an API for doing > serial I/O under DOS, Linux and SunOS called DZComm. Pretty slick. > > It's on sourceforge: > http://dzcomm.sourceforge.net/ > > My master plan was to use Call Library Nodes to tap into the > functions in the libdzcom.so shared library (like with the Comedi > library). I made 9 VIs but I don't think I ever tested all > of them. > I recall a few working... Should be easy to finish all the > functions > if there's no complex data structures. > > Here are some other serial port projects that didn't seem to be as > useable but worth mentioning: > > Columbo Simple Serial Library > http://sourceforge.net/projects/cssl/ > > ezV24 > http://sourceforge.net/projects/ezv24/ > > Have fun, > kevin > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > OpenGToolkit-Developers mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers > |
From: Jim K. <jk...@ja...> - 2005-01-14 00:35:35
|
Assuming that we are legally allowed do distribute the files, aggregating them on OpenG.org is fine with me. There are many mechanisms for doing this. I recommend that we create a forum topic and attach the documents to the initial forum posting. This will allow others to download the documents and directly start a discussion. If we are not allowed to (re)distribute the files, then I recommend hyperlinking to the files, rather than posting them on OpenG.org. Please wait to post any files to OpenG.org until we "go-live" with the new discussion forums. The new forums will provide a lot of nice features. We have only a few minor things to do before we are ready. Regards, -Jim Martin Henz wrote: > > John Brohan wrote: > >> Thanks for your offer, I have LV 6.1 and I'd like to try to get some >> royalty free Serial drivers written! How do I start? > >> Jim Kring wrote: >>> John, >>> >>> OpenG is a great forum work on such a thing. I can help you get a >>> project >>> started. >>> > > Also, many thanks to you Jim. > > Let me explain, what we discussed on Info-LabVIEW and in > private mail. (John, please reply to this posting, if > something is not correct.) > > At first, we would like to collect some existing royality > free and open source solutions for the serial port > communication. > > > Scott Hannahs has a set of serial drivers maybe from > Albert Geven. These VIs are interfacing to the legacy > serial port driver which officially exists until LabVIEW > 6.1. > > I have written serial port interface written for the > windows operating system. All mayor functionality are > inside a DLL which is written in C. The functions in this > DLL are handling the labview data types (error cluster, LV > strings, LV booleans...). Not all functions are actually > tested, so this interface is actually a beta version. > > As Scott Hannahs explained: > >> What is needed is a CROSS PLATFORM serial interface. > > So we need developers esp. for Mac OS and Linux. > > Anyway, we would like to start this project. At first, we > need a little piece space on a web or ftp server, where we > can temporarily store the collected packages for our own use. > I can also store this on my own server, but I prefer to > store the packeges on openg.org if this is possible. > > John Brohan will stay in contact to Jim Kring who tells him > how we can start the project on OpegG.org > > The next steps would be the examination of the collected > packages. Then we'll decide what we exactly want to do. > > > -- > Martin Henz > > > > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > OpenGToolkit-Developers mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opengtoolkit-developers > -- Jim Kring James Kring, Inc. jk...@ja... 415.720.5972 phone 415.366.3299 fax http://www.jameskring.com |
From: Martin H. <mar...@mh...> - 2005-01-14 11:23:53
|
Jim Kring wrote: > Assuming that we are legally allowed do distribute the files, aggregating > them on OpenG.org is fine with me. There are many mechanisms for doing > this. I recommend that we create a forum topic and attach the documents > to the initial forum posting. This will allow others to download the > documents and directly start a discussion. > If we are not allowed to (re)distribute the files, then I recommend > hyperlinking to the files, rather than posting them on OpenG.org. Thank's, thats a great idea. > Please wait to post any files to OpenG.org until we "go-live" with the new > discussion forums. The new forums will provide a lot of nice features. > We have only a few minor things to do before we are ready. I think, that the VISA discussion started a long time ago - since LabVIEW 4.1 or so. And I remember that I don't like some of the legacy serial port driver disatvantages since the time I moved from LabVIEW 2.5.1 on MAc to 3.1 on windows. We are not in hurry :-) -- 73 de Martin, DL5NAH |
From: Jim K. <jk...@ja...> - 2005-01-16 03:53:40
|
Martin Henz wrote: > > Jim Kring wrote: > > > Assuming that we are legally allowed do distribute the > > files, aggregating them on OpenG.org is fine with me. > > There are many mechanisms for doing this. I recommend > > that we create a forum topic and attach the documents > > to the initial forum posting. This will allow others > > to download the documents and directly start a > > discussion. > > > If we are not allowed to (re)distribute the files, then > > I recommend hyperlinking to the files, rather than posting > > them on OpenG.org. > > Thank's, thats a great idea. > > > Please wait to post any files to OpenG.org until we > "go-live" with the new > > discussion forums. The new forums will provide a lot of > nice features. > > We have only a few minor things to do before we are ready. > > I think, that the VISA discussion started a long time ago - > since LabVIEW 4.1 or so. And I remember that I don't like > some of the legacy serial port driver disatvantages since > the time I moved from LabVIEW 2.5.1 on MAc to 3.1 on > windows. > > We are not in hurry :-) > The new discussion forums are up and running. I have started a discussion topic called "OpenG Serial Drivers" here: http://forums.openg.org/viewtopic.php?t=12 If you already have an OpenG.org user account (from the old website), use the "I forgot my password" link to have your password reset and a new one emailed to you. Regards, -Jim |
From: Martin H. <mar...@mh...> - 2005-01-13 21:26:31
|
John Brohan wrote: > Thanks for your offer, I have LV 6.1 and I'd like to try to get some > royalty free Serial drivers written! How do I start? > Jim Kring wrote: >> John, >> >> OpenG is a great forum work on such a thing. I can help you get a project >> started. >> Also, many thanks to you Jim. Let me explain, what we discussed on Info-LabVIEW and in private mail. (John, please reply to this posting, if something is not correct.) At first, we would like to collect some existing royality free and open source solutions for the serial port communication. Scott Hannahs has a set of serial drivers maybe from Albert Geven. These VIs are interfacing to the legacy serial port driver which officially exists until LabVIEW 6.1. I have written serial port interface written for the windows operating system. All mayor functionality are inside a DLL which is written in C. The functions in this DLL are handling the labview data types (error cluster, LV strings, LV booleans...). Not all functions are actually tested, so this interface is actually a beta version. As Scott Hannahs explained: > What is needed is a CROSS PLATFORM serial interface. So we need developers esp. for Mac OS and Linux. Anyway, we would like to start this project. At first, we need a little piece space on a web or ftp server, where we can temporarily store the collected packages for our own use. I can also store this on my own server, but I prefer to store the packeges on openg.org if this is possible. John Brohan will stay in contact to Jim Kring who tells him how we can start the project on OpegG.org The next steps would be the examination of the collected packages. Then we'll decide what we exactly want to do. -- Martin Henz |
From: Scott H. <st...@ma...> - 2005-01-14 03:20:20
|
At 22:26 +0100 1/13/05, Martin Henz wrote: > Scott Hannahs has a set of serial drivers maybe from > Albert Geven. Yes, these are based on Albert's NLSerial library from phillips. > > What is needed is a CROSS PLATFORM serial interface. > >So we need developers esp. for Mac OS and Linux. Since OS X and linux use the same ioctl and unix read/write calls that are posix compatible it should be a single piece of code that is cross compiled. >The next steps would be the examination of the collected >packages. Then we'll decide what we exactly want to do. The trick will be deciding how to do a lot of the visa properties, opening and closing and locking resources. I have a VISA imitation framework that I used for my GPIB driver. This was sort of VISA looking thing but it worked. Properties are stored as strings as a key and data as a variant. It was kept in an array of visa resource names. That code is all Labview and certainly available as well to open G. At the base level it called into the GPIB driver, but it could call serial port primitives as well. It would be nice to keep as much of the code as possible in Labview and only stubs in platform specific libraries. There is a cute trick that Christophe Salzmann has for making fat libraries with multiple code objects for all platforms in it. -Scott |
From: Rolf K. <rol...@ci...> - 2005-01-14 08:27:02
|
Scott Hannahs wrote: > At 22:26 +0100 1/13/05, Martin Henz wrote: > > Scott Hannahs has a set of serial drivers maybe from > > Albert Geven. >=20 > Yes, these are based on Albert's NLSerial library from phillips. Just to be sure. I wonder if for the serpdrv (the translation driver on Windows ultimatively used by this library) might not be a similar issue with licensing. NI wanted to have runtime fees for LabVIEW executables at some time and then dropped that as far as you built executables which used NI hardware or the built-in serial port. With standard serial ports disappearing from PCs more and more this can get also an issue. On Mac Classic the serial port driver was simply a VI library calling into the Mac OS device driver interface so recreating the VIs would have been a complete solution as well as calling any other possible hardware which had a device driver installed. In the case of the Windows serpdrv driver, this one had quite some limitations. It is possible to use for simple device communication but a pain in the ass or impossible to do more complicated things. =20 > > > What is needed is a CROSS PLATFORM serial interface. > > > >So we need developers esp. for Mac OS and Linux. >=20 > Since OS X and linux use the same ioctl and unix read/write=20 > calls that are posix compatible it should be a single piece=20 > of code that is cross compiled. >=20 > >The next steps would be the examination of the collected > >packages. Then we'll decide what we exactly want to do. > > The trick will be deciding how to do a lot of the visa=20 > properties, opening and closing and locking resources. I=20 > have a VISA imitation framework that I used for my GPIB=20 > driver. This was sort of VISA looking thing but it worked.=20 > Properties are stored as strings as a key and data as a=20 > variant. It was kept in an array of visa resource names. >=20 > That code is all Labview and certainly available as well to=20 > open G. At the base level it called into the GPIB driver,=20 > but it could call serial port primitives as well. It would=20 > be nice to keep as much of the code as possible in Labview=20 > and only stubs in platform specific libraries. There is a=20 > cute trick that Christophe Salzmann has for making fat=20 > libraries with multiple code objects for all platforms in it. This is an interesting solution but maybe a little heavyweight. On the posititve side of it is the fact that most LabVIEW developers could contribute to it in one or the other way. My own solution where I have a quite finished framework written in C for at least Windows and Unix, but no hardware specific drivers yet, is to actually implement a fully VISA compatible external library with plugin DLLs for the different hardware interfaces. It is a very modular approach with the main library implementing the VISA interface, a support library providing platform independant services such as memory allocation, mutexes, ini file access, string handling, shared library access etc, and with each VISA resource type handled in one hardware driver module. =20 The main library could eventually be placed into the application folder and would be picked up by that application if it wants to use VISA. Until it is to that point where it really can replace VISA for some interfaces, its name could be changed to a different name than the standard VISA library name and a VISA compatible VI library with with Call Library Nodes could provide access to it. I'm willing to provide this code under an LGPL compatible license into an OpenG project of some sort if there is interest for it. Since it is a dynamically linked library, this would IMO provide for all potential users with a good solution. Rolf Kalbermatter |