Best Interface Option

This is the place for any magazine-related discussions that don't fit in any of the column discussion boards below.
Post Reply
ele1200
Posts: 49
Joined: Mon Nov 11, 2002 1:01 am
Contact:

Best Interface Option

Post by ele1200 » Mon Mar 03, 2003 3:49 pm

Hey,<p>I am looking to interface a called ID decoder chip to my computer. The chip's output is serial data, 1200 baud, 1 stop, 8 data for a total of 10 bits. Should i go into the serial port directly with this or convert it parallel with a UART and go to the parallel? I want to use VB to record the data and process it, so which is the best way to go? Any Alternatives?

chessman
Posts: 292
Joined: Tue Jan 14, 2003 1:01 am
Location: Issaquah, WA
Contact:

Re: Best Interface Option

Post by chessman » Mon Mar 03, 2003 6:41 pm

I personally would go with a UART converting it to parallel because it makes it much easier to write software. The code required is a lot more simple to read a full byte of data instead of reading in the serial data.

Colinr
Posts: 33
Joined: Wed Oct 23, 2002 1:01 am
Location: UK
Contact:

Re: Best Interface Option

Post by Colinr » Tue Mar 04, 2003 5:35 am

just to equal the balance i suggest you stick to the serial data and feed it in to a serial port (you may need to convert to RS232 levels first ) Visual Basic must still have some form of "open Com" commands to configure the serial port and and some form of input commpan to read from the port ( I have not programed in basic since Q basic so can not confirm this)<p>Colin

rshayes
Posts: 1286
Joined: Tue Mar 04, 2003 1:01 am
Contact:

Re: Best Interface Option

Post by rshayes » Tue Mar 04, 2003 6:05 am

Connecting to the serial port would only require a single RS-232 interface chip. Connecting to the parallel port would require a UART, some logic for timing, and at least 8 data buffers and a couple more for control signals.<p>Visual Basic appears to be different from QuickBasic in the way the serial port is controlled. It appears to use a routine called an "ActiveX control". The one for serial communication may be MSCOMM.OCX. I would look for information on the Microsoft web site.

ljbeng
Posts: 99
Joined: Mon Jan 13, 2003 1:01 am
Location: South Central NE
Contact:

Re: Best Interface Option

Post by ljbeng » Tue Mar 04, 2003 6:19 am

VB is great for using serial data. There are many commands for monitoring, sending and receiving serial data and it supports all the normal baud rates. Parallel data into VB is another story. You would need extra third-party components to get the data in and out of the port. But once you have the necessary drivers, parallel is just as easy as serial. I don't know what kind of through-rate you can get with VB and the parallel port but I would think using the serial port is the best way to go.<p>[ March 04, 2003: Message edited by: ljbeng ]</p>

vapor
Posts: 10
Joined: Wed Feb 12, 2003 1:01 am
Location: North of Dallas
Contact:

Re: Best Interface Option

Post by vapor » Sun Mar 09, 2003 5:37 pm

It would probably be easier to read the port data via a C or C++ program. <p>If you cannot read parallel directly into VB, then write a C routine to read the parallell port and then transfer it to the VB ap.
lost-in-code

Post Reply

Who is online

Users browsing this forum: No registered users and 9 guests