Sponsored Content
Top Forums Shell Programming and Scripting Communicating with ethernet to serial LED sign - is this feasible? Post 303042853 by jgt on Wednesday 8th of January 2020 12:07:32 PM
Old 01-08-2020
Device address probably should be one, not zero.

The concept of device address stems from RS485 serial communications that allow for daisy chained devices.


Are there possibly dip switches or a ROM config process to set the device address?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to use 2 Proccess communicating with each other using 2 pipe

Hi, Guys ... I want to know how to use to 2 processes (A & B) communicating with each others through 2 pipes (Pipe1 & Pinpe2) : such that process A write to Pipe1 and Process B read from Pipe1 and process B write to Pipe2 and Process A read from Pipe2 . Does anyone have an idea about... (1 Reply)
Discussion started by: someone33
1 Replies

2. Shell Programming and Scripting

Sign on/Sign off logging script

I'd like to make a script that I can execute every time I sign on to my linux box that keeps track of the time and allows to me to add a remark to a file. So basically once I log in, I run the script, and it outputs the date and time to a text file (log.txt). But that isn't my problem. I need... (1 Reply)
Discussion started by: Glider
1 Replies

3. UNIX for Advanced & Expert Users

Communicating with Serial Port

I am using system running on red hat linux 4. I had connected health measuring machine to the serial port and configured it stty -F /dev/ttyS0 9600 -parenb cs8 -cstopb this machine requires a command to be passed to it for giving output. I am unable to pass command hexa format(0x68) to the... (4 Replies)
Discussion started by: netsavant
4 Replies

4. UNIX for Dummies Questions & Answers

Communicating Via Terminals With Other Computers

Hello, I would like to know if it is possible to communicate between two terminals on seperate computers for free - e.g. not using proprietary software or using the built in UNIX terminals on operating systems of the UNIX flavor. Thanks, photray94 (2 Replies)
Discussion started by: photray94
2 Replies

5. AIX

how to know my serial port is communicating and running fine

i want to know that my serial port ( pci slot with 2 port ) is working fine and communicating is there any way to know the serialport is working and communicating? please help (3 Replies)
Discussion started by: pchangba
3 Replies

6. Ubuntu

Ubuntu 9.04 Serial application to telnet to serial device

Hello! I am working on an application which reads environmental instruments which have serial ports. The application requires a serial port to be present to talk to the device (i.e. /dev/ttyS0 ). In some instances the environmental devices will be 100's of yards away from the computer, so a... (5 Replies)
Discussion started by: mvona
5 Replies

7. Programming

ERROR while communicating with gmail

$./a.out smtp.gmail.com 25 220 mx.google.com ESMTP 9sm2923369yxf.23 250 mx.google.com at your service 220 2.0.0 Ready to start TLS after handshake Common Name: smtp.gmail.com after get cert dn -----BEGIN SSL SESSION PARAMETERS-----... (0 Replies)
Discussion started by: darshan.ghumare
0 Replies

8. IP Networking

Need a bridge from an ethernet interface to a serial interface

This is my situation DOS pc serial cable (sl0) Linux Pc eth1 192.168.0.10 <-------------------->192.168.0.2 <------------>192.168.0.1 (router) I connected the linux pc and the dos pc with a SLIP (serial line internet protocol), so they can communicate in the sl0 interface. ... (3 Replies)
Discussion started by: mghis
3 Replies

9. Programming

Child threads communicating with main thread via pipes

I have a simple client/server program I am using for learning purposes. I have it setup so that after server is setup and listening it than goes into a loop where it accepts incoming client connections. After each connection, the client socket is than passed to a thread routine where it can be... (3 Replies)
Discussion started by: Majortom71
3 Replies

10. Shell Programming and Scripting

Script to send serial commands over ethernet

Hi there, I have a Debian server (192.168.1.1) connected through ethernet to a RS232 device servers (192.168.1.5) that is then connected through RS232 to a Video Projector. The idea is that I want to send commands to the video projector (eg. turn on/off) via the device server. According to... (4 Replies)
Discussion started by: chebarbudo
4 Replies
IEEE1284_GET_DEVICEI(3) 					     Functions						   IEEE1284_GET_DEVICEI(3)

NAME
ieee1284_get_deviceid - retrieve an IEEE 1284 Device ID SYNOPSIS
#include <ieee1284.h> ssize_t ieee1284_get_deviceid(struct parport *port, int daisy, int flags, char *buffer, size_t len); DESCRIPTION
This function is for retrieving the IEEE 1284 Device ID of the specified device. The device is specified by the port to which it is attached, and optionally an address (daisy) on the daisy chain of devices on that port. daisy should be -1 to indicate that the device is not participating in a IEEE 1284.3 daisy chain, meaning it is the last (or only) device on the port, or should be a number from 0 to 3 inclusive to indicate that it has the specified daisy chain address (0 is next to the port). The flags parameter should be a bitwise union of any flags that the program wants to use. Available flags are: F1284_FRESH Guarantee a fresh Device ID. A cached or OS-provided ID will not be used. The provided buffer must be at least len bytes long, and will contain the Device ID including the initial two-byte length field and a terminating zero byte on successful return, or as much of the above as will fit into the buffer. RETURN VALUE
A return value less than zero indicates an error as below. Otherwise, the return value is the number of bytes of buffer that have been filled. A return value equal to the length of the buffer indicates that the Device ID may be longer than the buffer will allow. E1284_NOID The device did not provide an IEEE 1284 Device ID when interrogated (perhaps by the operating system if F1284_FRESH was not specified). E1284_NOTIMPL One or more of the supplied flags is not supported in this implementation, or if no flags were supplied then this function is not implemented for this type of port or this type of system. This can also be returned if a daisy chain address is specified but daisy chain Device IDs are not yet supported. E1284_NOTAVAIL F1284_FRESH was specified and the library is unable to access the port to interrogate the device. E1284_NOMEM There is not enough memory. E1284_INIT There was a problem initializing the port. E1284_INVALIDPORT The port parameter is invalid. NOTES
Unless the F1284_FRESH flag is given, the library will try to find the device's ID as unobtrusively as possible. First it will ask the operating system if it knows it, and then it will try actually asking the device for it. Because of this, the Device ID may be partially computed (the length field, for example) or even partially missing if the operating system has only remembered some parts of the ID. To guarantee that you are getting the bytes that the device sent, use F1284_FRESH. Be aware that the operating system may allow any user to inspect the Device IDs that it provides, whereas device access is normally more restricted. The initial two-byte length field is a big-endian 16 bit unsigned integer provided by the device and may not be accurate. In particular, it is meant to indicate the length of the entire string including the length field itself; however, some manufacturers exclude the length field or just set the length field to some arbitrary number greater than the ID length. AUTHOR
Tim Waugh <twaugh@redhat.com> Author. COPYRIGHT
Copyright (C) 2001-2003 Tim Waugh [FIXME: source] 06/17/2014 IEEE1284_GET_DEVICEI(3)
All times are GMT -4. The time now is 11:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy