software for custom guages, etc. - Page 3

ST43LTH · 07-06-2004, 09:30 AM

Any news on this? I would like to use my already-puchased scantool to interface to my carupter. Can anyone share the VB code that was used in the application on the first page.

Thanks

AdamR

Saurk · 07-15-2004, 01:18 AM

Quote: Originally Posted by superart

I know. I'm just saying, in the unlikely event that some people on this forum do have access to it, it is a wonderfull tool that is perfect for the job and shouldn't be overlooked.

For me, perdonally, its much more accessible than flash or flash studio pro, which were mentioned earlier.

I will try to make a preliminary mock-up tonight, and will try to post it.

Actually, LabView maybe ain't such a bad idea. You can compile LabView aps into a LabView executable (don't need to buy the $$$ license to run). I have LabView at work, but I haven't done any LabView programming in a while. Also, I'm not sure how to interface with the OBD-II line inputs, without using an expensive DAQ card.

Nobias · 07-15-2004, 05:38 AM

I have LabView at work also. They make a set of VB components, it's part of their product called Measurement Studio. I'll throw together a quick screenie when i get to work.

Nobias · 07-15-2004, 06:39 AM

Here's a shot of NI Component Works.

tech013 · 07-15-2004, 07:15 AM

that looks good but will it work?

Nobias · 07-15-2004, 08:03 AM

It's functional. You just feed the controls integer values. The switched and LEDs are booleans. I dont know how well the price will work though....

superart · 07-15-2004, 12:25 PM

Quote: Originally Posted by Saurk

Also, I'm not sure how to interface with the OBD-II line inputs, without using an expensive DAQ card.

LabView can accept data from the serial port. If you have a OBDII scanner or reader that feeds data to the serial port, LabView can read it. The only thing is, it gets it as a stream of bits, and you need a way to interpret those bits and convert it to a format that LabView can interpret and display. That shouldn't be too hard. I remember seeing a document that describes the bit layout of OBDII data. Ill try looking around and see if I can find it again.

Unfortunately, I don't have LabView installed on my computer, and my install disk is buried somewhere in my trunk of college stuff. And the trunk is in storage back at school. So I have no access to LabView until the end of August :-(

<Edit -- 7/15/04>
This isn't the document I was refering to, but is helpfull non the less. It seems to be pretty extensive and covers a lot of the things that OBDII has to offer.
http://www.obddiagnostics.com/obdinfo/info.html

Saurk · 07-15-2004, 08:30 PM

Quote: Originally Posted by Nobias

It's functional. You just feed the controls integer values. The switched and LEDs are booleans. I dont know how well the price will work though....

Its free!!! NI sells an application builder (my company has a license for this as well), so that you can build an executable that doesn't require the LabView license. My company has only 1 LabView development license, but many computers running LabView-written executables. Perfectly legal.

So, what I'm trying to say is that if 1 person can write the code, EVERYONE else could use it without a license, so long as someone has the application builder.

The down side is, you can't modify the executables. So, I'm not sure if it's possible to write such a LabView app that would work with all cars.

mobileh1 · 07-15-2004, 08:56 PM

Is there a download if this SDK? Id like to hook it up to my ODBII code?

Quote: Originally Posted by Nobias

It's functional. You just feed the controls integer values. The switched and LEDs are booleans. I dont know how well the price will work though....

Nobias · 07-16-2004, 05:43 AM

Quote: Originally Posted by superart

LabView can accept data from the serial port. If you have a OBDII scanner or reader that feeds data to the serial port, LabView can read it. The only thing is, it gets it as a stream of bits, and you need a way to interpret those bits and convert it to a format that LabView can interpret and display. That shouldn't be too hard. I remember seeing a document that describes the bit layout of OBDII data. Ill try looking around and see if I can find it again.

Unfortunately, I don't have LabView installed on my computer, and my install disk is buried somewhere in my trunk of college stuff. And the trunk is in storage back at school. So I have no access to LabView until the end of August :-(

<Edit -- 7/15/04>
This isn't the document I was refering to, but is helpfull non the less. It seems to be pretty extensive and covers a lot of the things that OBDII has to offer.
http://www.obddiagnostics.com/obdinfo/info.html

My screenie was labview components in VB. So if you can get data into VB you can format it and pump it to those control no problem.

Quote: Originally Posted by Saurk

Its free!!! NI sells an application builder (my company has a license for this as well), so that you can build an executable that doesn't require the LabView license. My company has only 1 LabView development license, but many computers running LabView-written executables. Perfectly legal.

So, what I'm trying to say is that if 1 person can write the code, EVERYONE else could use it without a license, so long as someone has the application builder.

The down side is, you can't modify the executables. So, I'm not sure if it's possible to write such a LabView app that would work with all cars.

LabView apps are NOT FREE. They require a runtime to run and the runtime is supposed to be licensed. Just because the runtime works with out a key doesn't mean it's legally free.

Quote: Originally Posted by mobileh1

Is there a download if this SDK? Id like to hook it up to my ODBII code?

The request for demo is at http://volt.ni.com/niwc/common.jsp?p...o_visual_basic. If you drop me a pm and i'll dig out an old demo disk and email you the ocxes.

superart · 07-16-2004, 10:51 AM

Quote: Originally Posted by Nobias

My screenie was labview components in VB. So if you can get data into VB you can format it and pump it to those control no problem.

I don't know about VB, but LabView has a serial port and serial port init VI that comes standard. I was planning on using that.

Then I would manipulate the bits with the logic VIs

I don't know which method would be easier or more streamlined, but I figure if there is no VB it's one less thing to provide overhead to the CPU and memory and its more portable.

Nobias · 07-16-2004, 11:34 AM

VB has Comm controls. There are a couple posts above that have sample vb apps already made . I would personally use VB and just use Labview graphical components, so no actual Labview VIs would be used. VB would probably have less overhead than the Labview VIs, since VB is a MS Product and it's runtime has a smaller footprint with less required pieces. If I had an interface I'd test both...

superart · 07-16-2004, 11:47 AM

Quote: Originally Posted by Nobias

VB would probably have less overhead than the Labview VIs, since VB is a MS Product and it's runtime has a smaller footprint with less required pieces. If I had an interface I'd test both...

yea, we all know that msft is famous for there efficient code that provides little to no overhead.

although what you say may well be true. Like I said, I don't know about VB, but regardless, if you made the app entirely in LabView, it would be way more portable than if you used VB. This would provide a solution to people who use linux and are looking for some good OBDII software.

Nobias · 07-16-2004, 11:57 AM

MS does have its flaws.....
but a $300 dollar labview runtime fee compared to $0 vb runtime fee. it all depends on how legal you want to be..

superart · 07-16-2004, 12:26 PM

how does the runtime work? Iv'e never compiled and run a LabView program, since all the computers Ive used it on have LabView Full installed.