12-28-2013
Controlling Peripheral Relay/Switch with Scripts
Has anybody worked with writing scripts with peripheral devices such as relays and/or switches? For example, writing a script that activates/deactivates a relay switch to turn devices on and off. Or maybe writing a script that checks the status of a peripheral on/off switch to provide a remote status of an open or closed door.
Are there universal USB/Ethernet peripherals available for stuff like this?
Last edited by sudo; 12-28-2013 at 09:55 PM..
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
How can I control the screen output when trying to read a large file onto the screen x number of lines at a time. I'm trying to use this is a bourne shell script. I want to display 10 lines of a file, pause the screen so that a user can read the file, and then display the next 10 lines of the file,... (6 Replies)
Discussion started by: jrdnoland1
6 Replies
2. UNIX for Dummies Questions & Answers
Working in SunOS 2.6 without the GUI, I am trying to find out what command line syntax I can use to reset the serial port. I have also been curious how to reset peripheral devices without having to reboot the machine. If anyone has a cheat sheet for that, that would be great! (1 Reply)
Discussion started by: mcherry
1 Replies
3. UNIX for Dummies Questions & Answers
I support an app that outputs alert and audit messages to one log file (vendor says they can't be separated). The script that I have written takes a copy (mv cmd) of the file to do the separation and reformatting. I have a problem that I loose records (messages are being written constantly, upto 3+... (5 Replies)
Discussion started by: nhatch
5 Replies
4. Programming
What is controlling terminal in the case of daemon process? (2 Replies)
Discussion started by: Madhu Babu
2 Replies
5. Filesystems, Disks and Memory
Hi guys,
Can anyone please tell me how I can control the I/O on my hardware devices in Suse Linux 8.1.
I find that everytime I am reading a CD, or copying from a CD, I am unable to listen to music of watch a movie.
Maybe this is intended to be like so, for the current high street technolgy... (1 Reply)
Discussion started by: bionicfysh
1 Replies
6. Shell Programming and Scripting
Any one know the below means :
ps: no controlling terminal
I had run a script in background :
nohup ./benchmark.sh &
and shutdown my windows system from where i connected through SSH
I am using bash:
The above script perfoms various tasks of Benchmarking Repositories
Today the... (3 Replies)
Discussion started by: sriram003
3 Replies
7. Solaris
I want to be able to use an account on a solaris 10 server, eg root@myhost
to act as a relay to forward mail to my domain account me@mycompany.com
The reason for this is to configure root@myhost as a mail relay on Brocade SAN switches - so that when a port goes bad i get an email alert.... (0 Replies)
Discussion started by: wibidee
0 Replies
8. Shell Programming and Scripting
hi,
how to access console of a switch having rj45 on switch side to db 9 female on pc side console cable which needs to be connected to one console server having rj11 on its side and db 9 female on other end.i.e. on switch side,console cable has rj45 and db 9 pin female connector on other side of... (1 Reply)
Discussion started by: pankajd
1 Replies
9. Red Hat
Why does removing "rhgb quiet" from the kernel boot parameters control whether or not the commands I enter are displayed in single user mode ?
For instance, if I do not remove "rhgb quiet", when I am in single user mode, whatever command I type will not be displayed on the screen.
The... (0 Replies)
Discussion started by: Hijanoqu
0 Replies
LEARN ABOUT DEBIAN
ieee1284_terminate
IEEE1284_NEGOTIATION(3) Functions IEEE1284_NEGOTIATION(3)
NAME
ieee1284_negotiate, ieee1284_terminate - IEEE 1284 negotiation
SYNOPSIS
#include <ieee1284.h>
int ieee1284_negotiate(struct parport *port, int mode);
void ieee1284_terminate(struct parport *port);
DESCRIPTION
These functions are for negotiating to and terminating from IEEE 1284 data transfer modes. The default mode is called compatibility mode,
or in other words normal printer protocol. It is a host-to-peripheral mode only. There are special modes that allow peripheral-to-host
transfer as well, which may be negotiated to using ieee1284_negotiate. IEEE 1284 negotiation is a process by which the host requests a
transfer mode and the peripheral accepts or rejects it. An IEEE 1284-compliant device will require a successful negotiation to a particular
mode before it is used for data transfer (but simpler devices may not if they only speak one transfer mode).
To terminate the special mode and go back to compatilibity mode use ieee1284_terminate.
These functions act on the parallel port associated with port, which must be claimed.
With a device strictly complying to IEEE 1284 you will need to call ieee1284_terminate in between any two calls to ieee1284_negotiate for
modes other than M1284_COMPAT.
AVAILABLE MODES
Uni-directional modes
o M1284_COMPAT: Compatibility mode. Normal printer protocol. This is not a negotiated mode, but is the default mode in absence of
negotiation. ieee1284_negotiate(port, M1284_COMPAT) is equivalent to ieee1284_terminate(port). This host-to-peripheral mode is used
for sending data to printers, and is historically the mode that has been used for that before IEEE 1284.
o M1284_NIBBLE: Nibble mode. This peripheral-to-host mode uses the status lines to read data from the peripheral four bits at a time.
o M1284_BYTE: Byte mode. This peripheral-to-host mode uses the data lines in reverse mode to read data from the peripheral a byte at a
time.
Bi-directional modes
o M1284_ECP: ECP mode. On entry to ECP mode it is a host-to-peripheral (i.e. forward) mode, but it may be set to reverse mode using
ieee1284_ecp_fwd_to_rev(3). It is common for PC hardware to provide assistance with this mode by the use of a FIFO which the host (or,
in reverse mode, the peripheral) may fill, so that the hardware can do the handshaking itself.
o M1284_EPP: EPP mode. In this bi-directional mode the direction of data transfer is signalled at each byte.
Mode variations
o M1284_FLAG_DEVICEID: Device ID retrieval. This flag may be combined with a nibble, byte, or ECP mode to notify the device that it
should send its IEEE 1284 Device ID when asked for data.
o M1284_BECP: Bounded ECP is a modification to ECP that makes it more robust at the point that the direction is changed. (Unfortunately
it is not yet implemented in the Linux kernel driver.)
o M1284_ECPRLE: ECP with run length encoding. In this mode, consecutive data bytes of the same value may be transferred in only a few
cycles.
RETURN VALUE
E1284_OK
The negotiation was successful.
E1284_NOTAVAIL
Negotiation is not available with this port type.
E1284_REJECTED
Negotiation was rejected by the peripheral.
E1284_NEGFAILED
Negotiation failed for some reason. Perhaps the device is not IEEE 1284 compliant.
E1284_SYS
A system error occured during negotiation.
E1284_INVALIDPORT
The port parameter is invalid (for instance, perhaps the port is not claimed).
AUTHOR
Tim Waugh <twaugh@redhat.com>
Author.
COPYRIGHT
Copyright (C) 2001-2003 Tim Waugh
09/18/2007 IEEE1284_NEGOTIATION(3)