Sponsored Content
Top Forums Programming problem while having a communication with serial port????? Post 302143009 by arunchaudhary19 on Tuesday 30th of October 2007 05:27:44 AM
Old 10-30-2007
I am trying with minicom....
but its status is showing offline..........
CTRL-A Z for help | 9600 8N1 | NOR | Minicom 2.1 | VT102 | Offline
this line is seen at the bottom of minicom...........
please help how to send and recieve data through minicom.......
thanks & regards,
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Serial port communication

We're running SCO Unix Openserver 5.05 and I'm having trouble with serial communication between the com2 serial port and a handheld device. Downloading data from Unix to the handheld works perfectly, but the other way around creates a major problem. I don't know whether it's a buffer overflow or... (1 Reply)
Discussion started by: Aretha
1 Replies

2. UNIX for Advanced & Expert Users

Serial Communication in UNIX

Hi, I am working on serial communication on Unix. Can anyone guide me through it. The steps required for RS 232 communication and can i do serial communication even if i dont have super user previledges. Thankx, Vicky (1 Reply)
Discussion started by: Vicky
1 Replies

3. UNIX for Dummies Questions & Answers

serial communication

This isn't really a unix question, or even a programming question, but I hope you guys can help. I want to create a program to control the electricity on a model railway. I have created the program to that it sends characters over the serial cable, but now I need to do the switch that will... (1 Reply)
Discussion started by: KrazyGuyPaul
1 Replies

4. IP Networking

ip communication through serial connection

I have serial modem connection between two computers. We have to login the remote computer through ip address. How can I get the ip address in this connection? (1 Reply)
Discussion started by: pcsaji
1 Replies

5. Programming

Problem regarding serial port and multithreading

hello, I am creating a application in which I first open the serial port and then create the thread..for reading the data comming through that serial port. from that same thread I create another thread that is write thread means for writing on the serial port... I am continously polling again... (3 Replies)
Discussion started by: arunchaudhary19
3 Replies

6. UNIX for Dummies Questions & Answers

problem with serial port BSD

Hello all , i have change my system debian linux to freebsd( pcBSD) all working as well , but the serial does not work correctly. Under linux the problem does not appears. my problem is than my serial port does work . the first step than i have make is look with dmesg if my serial are... (0 Replies)
Discussion started by: pitbac23
0 Replies

7. Solaris

Serial port problem

I am working with solaris 9 sparc and I want to connect physical device in serial port but when I am connecting it,It is showing the error window saying-- So can any1 tell me the reason or is there any package I have to add to work with serial port??? (2 Replies)
Discussion started by: smartgupta
2 Replies

8. Programming

problem in coding for GSM interfacing using serial port

i am having some coding problem in c for interfacing the GSM module through serial port. i want to send/receive sms. i have done all the setting for the port and know the AT command to use in this but i am actually having problem in reading and writing from serial port how to handle the signal when... (1 Reply)
Discussion started by: harsh_it
1 Replies

9. Programming

Serial communication failing

edit: never mind; mods please delete. I finally got so frustrated I figured it couldn't be the code and it must be the device on the other end. After pulling it out of its cradle, I realized it was a different model number than the one I was using before, and wasn't accepting my... (1 Reply)
Discussion started by: DreamWarrior
1 Replies

10. SCO

Problem finding what is using a serial port

How can I determine what process is currently using a serial port? A good bit of google searching hasn't turned up anything useful, but it seems like there has to be a way to do this without too much difficulty. When I first started looking into this problem, I assumed that when a port was in... (2 Replies)
Discussion started by: jdsnatl
2 Replies
REMOTE(5)						      BSD File Formats Manual							 REMOTE(5)

NAME
remote -- remote host description file DESCRIPTION
The systems known by tip(1) and their attributes are stored in an ASCII file which is structured somewhat like the termcap(5) file. Each line in the file provides a description for a single system. Fields are separated by a colon (``:''). Lines ending in a character with an immediately following newline are continued on the next line. The first entry is the name(s) of the host system. If there is more than one name for a system, the names are separated by vertical bars. After the name of the system comes the fields of the description. A field name followed by an `=' sign indicates a string value. A field name followed by a `#' sign indicates a numeric value. Entries named ``tip*'' and ``cu*'' are used as default entries by tip(1), and the cu(1) interface to tip, as follows. When tip is invoked with only a phone number, it looks for an entry of the form ``tip300'', where 300 is the data rate with which the connection is to be made. When the cu interface is used, entries of the form ``cu300'' are used. CAPABILITIES
Capabilities are either strings (str), numbers (num), or boolean flags (bool). A string capability is specified by capability=value; for example, ``dv=/dev/harris''. A numeric capability is specified by capability#value; for example, ``xa#99''. A boolean capability is speci- fied by simply listing the capability. at (str) Auto call unit type. br (num) The data rate (bits per second) used for communications on the serial port. When a modem is used, the data rate used to commu- nicate with the remote modem may be different than this rate. This is a decimal number. The default rate is 9600 bits per second. cm (str) An initial connection message to be sent to the remote host. For example, if a host is reached through a port selector, this might be set to the appropriate sequence required to switch to the host. cu (str) Call unit if making a phone call. Default is the same as the `dv' field. di (str) Disconnect message sent to the host when a disconnect is requested by the user. du (bool) This host is on a dial-up line. dv (str) UNIX device(s) to open to establish a connection. If this file refers to a terminal line, tip(1) attempts to perform an exclu- sive open on the device to ensure only one user at a time has access to the port. el (str) Characters marking an end-of-line. The default is NULL. `~' escapes are only recognized by tip after one of the characters in `el', or after a carriage-return. fs (str) Frame size for transfers. The default frame size is equal to BUFSIZ. hd (bool) The host uses half-duplex communication, local echo should be performed. ie (str) Input end-of-file marks. The default is NULL. oe (str) Output end-of-file string. The default is NULL. When tip is transferring a file, this string is sent at end-of-file. pa (str) The type of parity to use when sending data to the host. This may be one of ``even'', ``odd'', ``none'', ``zero'' (always set bit 8 to zero), ``one'' (always set bit 8 to 1). The default is even parity. pn (str) Telephone number(s) for this host. If the telephone number field contains an @ sign, tip searches the file /etc/phones file for a list of telephone numbers (see phones(5)). tc (str) Indicates that the list of capabilities is continued in the named description. This is used primarily to share common capabil- ity information. FILES
/etc/remote The remote host description file resides in /etc. EXAMPLES
Here is a short example showing the use of the capability continuation feature. It defines a 56k modem connection on the first serial port at 115200 bits per second, no parity using the Hayes command set with standard line editing and end of file characters. The arpavax entry includes everything in the UNIX-57600 entry plus the phone number for arpavax (in this case an @ character so that it is retrieved from the environment). UNIX-57600: :dv=/dev/cuau0:el=^D^U^C^S^Q^O@:oe=^D:du:at=hayes:br#115200:pa=none: arpavax|ax: :pn=@:tc=UNIX-57600 SEE ALSO
cu(1), tip(1), phones(5) HISTORY
The remote file format appeared in 4.2BSD. BUGS
The tip(1) utility uses its own notion of the serial ports data rate rather than the system default for a serial port. BSD
October 20, 2003 BSD
All times are GMT -4. The time now is 07:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy