[CLUE-Tech] Wireless Barcoding thru Linux Port

[Dave W]

> As I said, you don't want any getty at all.  What program is going to
> talk to this device?

This simple basic program is an example of what the Worthington people said
would work. I just have to figure how to open the com port from our 3rd
party Thoroughbred software we are using. And by the way thanks for your
help:)
Dave W2:)

 10 DIM P$(10)
>
> 20 OPEN "COM1:9600,N,8,1,RS,DS,CS,CD" AS #1
>
> 30 P$(1)="@B1 at C1@1,7,0,ENTER THE"; this sends line and row
>
> 40 P$(2)="@C3@@3,2,1,ITEM"
>
> 60 B$="";T1$="" ;initialize varaible
>
> 70 IF EOF(1) GOTO 70 ;wait for Byte to read
>
> 80 A$=INPUT(1,#1) ; input a byte
>
> 90 IF RIGHT(A$,1)=CHR(13) THEN 110 ;if CR goto 110
>
> 100 B$=B$+A$; GOTO 70 ; else concat to B$,get another ch
>
> 110 IF RIGHT(B$,1)=CHR(19) THEN 180 ;base initilized message
>
> 120 IF RIGHT(B$,1)=CHR(14) THEN 210; sign out message
>
> 130 IF RIGHT(B$,1)=CHR(15)
>
> THEN T1$=LEFT(B$,1)+P$(1)+P$(2) ;if sign in, 1st two
> messages
>
> I=2; GOTO 150
>
> 140 T1$=LEFT(B$,1)+P$(1)
>
> 150 T$=T1$+CHR(4) ;add EOT terminator
>
> 160 PRINT #1,T$ ;send a message to termial
>
> 170 I=I+1; IF I=4 THEN I=2
>
> 180 PRINT "TRICODER/BASE DATA : ",B$ ;display data recieved
>
> 190 PRINT "HOST RESPONSE: ",T1$ ; display data transmitted
>
> 200 GOTO 60 ;wait for another message
>
> 210 PRINT "TRICODER " ; LEFT$(B$,1); "SIGNED OUT"
>
> 220

*****************************************
----- Original Message -----
From: "David Anselmi" <anselmi at americanisp.net>
To: <clue-tech at clue.denver.co.us>
Sent: Thursday, January 30, 2003 5:08 PM
Subject: Re: [CLUE-Tech] Wireless Barcoding thru Linux Port


> That's it, I'm leaving.  Bad enough we have too many Daves around here,
> now we got two Dave Ws. ;-)
>
> Dave W wrote:
>
> > 1. There can be No operating system management.
> >     (no Logins,etc) except bufffering.
>
> That means the OS isn't doing anything with the serial device.  In other
> words, not running getty (or its cousins) on it.  Just make sure there
> is no getty line in /etc/inittab for /dev/ttyS3.
>
> As to buffering, I don't know about that (but perhaps the default is
> good enough).  You can look at the setserial man page -- that's the only
> one I know of for serial port devices.  There might be more in the
> kernel docs.
>
> > I have been editing the /etc/inittab file (trying to be careful) and
trying
> > different options for this port thru 'man agetty' and it gets confusing.
I
> > am familiar with most areas where linux uses the devices like
> > /sbin/init.d/serial and others.
>
> As I said, you don't want any getty at all.  What program is going to
> talk to this device?
>
> Dave
>
> _______________________________________________
> CLUE-Tech mailing list
> CLUE-Tech at clue.denver.co.us
> http://clue.denver.co.us/mailman/listinfo/clue-tech
>