Displaying 11 results from an estimated 11 matches for "pin4".
Did you mean:
pin
2015 Nov 16
2
Contact-closure UPS
...icups driver.
Working cable (direct cable pin1-pin1 ... pin9-pin9) connection on Windows:
PIN | PC | UPS
__________________________________________________________________________________
Pin1 | DCD | described as DTR (must keep Hi)
Pin2 | RxD | AC Power fail (NO, connected to pin4 UPS ground in case of AC failure)
Pin3 | TxD | N/A
Pin4 | DTR | UPS ground
Pin5 | GND | Battery low (NO, connected to pin4 UPS ground in case of LB)
Pin6 | DSR | 1. described as UPS RxD and 2. 3 seconds Hi (UPS shutdown)
Pin7 | RTS | UPS ground
Pin8 | CTS | N/...
2005 May 16
1
2 servers via PRI
...ood day all
How do i set a connection between 2 asterisk servers via PRI
In Bri I would set one to NT and TE
How shoud the zapata.conf and zaptel.conf look
And how should the cable be?
All I got on the web was to set one to "pri_net"...this cant be all?
And the cable
> pin1 <--> pin4> pin2 <--> pin5> pin3 <--> pin6> pin4 <--> pin1> pin5
<--> pin2> pin6 <--> pin3> pin5 <--> pin8> pin8 <--> pin7
Please Help and advice
Thanks Altus
2006 Jan 20
1
Hardwiring a Tellabs echo canceller - help req
...ect I
wired it up incorrectly, so I thought I'd see if anyone can point me in the
right direction. Digium tech support pointed me to this doc for a standard
T1 cable:
http://www.arcelect.com/RJ48C_and_RJ48S_8_position_jack_.htm
which looks like it means:
pin1 = recieve ring
pin2 = recive tip
pin4 = send ring
pin5 = send tip
So I treated the bottom part of the diagram like a noraml cat5 cable &
connected it in this way:
Zap side | 2572 side
--------------------
pin 1 <=> pin 25
pin 2 <=> pin 21
pin 4 <=> pin 10
pin 5 <=> pin 6
on the T1 side I have:
T1 side...
2015 Nov 16
0
Contact-closure UPS
...ble (direct cable pin1-pin1 ... pin9-pin9) connection on Windows:
>
> PIN | PC | UPS
> __________________________________________________________________________________
> Pin1 | DCD | described as DTR (must keep Hi)
> Pin2 | RxD | AC Power fail (NO, connected to pin4 UPS ground in case of AC failure)
The genericups driver does not have a setting to use the PC RxD line as a contact-closure input. It seems to be possible if the other software is using it, but genericups can only send a BREAK signal (rather than receiving it).
> Pin3 | TxD | N/A
> Pi...
2015 Nov 21
2
Contact-closure UPS
...y.
>
>If you have a multimeter, you could check pin 9 on the UPS relative to pin 4/7 to see if it is being driven negative.
I mesured it and on DC and it shows 0 V (zero V).
May be the information (pls. see attachment) that UPS PIN1 should bee keept HI is mandatory. Should I connect it to PC PIN4 DTR?
OR
I need to follow with contact closure cable?
Best regards,
Robert SZAKSZ.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Infosec_UPS_connector.PNG
Type: image/png
Size: 51305 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermai...
2003 Jun 11
6
Testing two E400P with E1 cross-cable
...r cable-->| Span2 |
| Span3 |--E1 crossover cable-->| Span3 |
| Span4 |--E1 crossover cable-->| Span4 |
+-------+ +-------+
The basic configuration seems ok, since zttool shows the links are OK.
I'm using this UTP cat5 cross-cable (not shielded):
pin1 <--> pin4
pin2 <--> pin5
pin3 <--> pin6
pin4 <--> pin1
pin5 <--> pin2
pin6 <--> pin3
pin5 <--> pin8
pin8 <--> pin7
I'm not really sure this is correct, since I've found only how to
connect pins 1,2,4 and 5. The other pins are connected as I supposed it
sh...
2015 Nov 16
2
Contact-closure UPS
...n1-pin1 ... pin9-pin9) connection on Windows:
>>
>> PIN | PC | UPS
>> __________________________________________________________________________________
>> Pin1 | DCD | described as DTR (must keep Hi)
>> Pin2 | RxD | AC Power fail (NO, connected to pin4 UPS ground in case of AC failure)
>
>The genericups driver does not have a setting to use the PC RxD line as a contact-closure input. It seems to be possible if the other software is using it, but genericups can only send a BREAK signal (rather >than receiving it).
>
>> Pin3 |...
2006 Jan 21
2
Tellabs 2572 EC Photos here.
...ect I wired it up incorrectly, so I thought I'd see if anyone can
point me in the right direction. Digium tech support pointed me to this
doc for a standard
T1 cable:
http://www.arcelect.com/RJ48C_and_RJ48S_8_position_jack_.htm
which looks like it means:
pin1 = recieve ring
pin2 = recive tip
pin4 = send ring
pin5 = send tip
So I treated the bottom part of the diagram like a noraml cat5 cable &
connected it in this way:
Zap side | 2572 side
--------------------
pin 1 <=> pin 25
pin 2 <=> pin 21
pin 4 <=> pin 10
pin 5 <=> pin 6
on the T1 side I have:
T1 side...
2015 Nov 21
0
Contact-closure UPS
> On Nov 21, 2015, at 2:43 AM, R?bert SZAKSZ <robert at szaksz.eu> wrote:
>
> I mesured it and on DC and it shows 0 V (zero V).
> May be the information (pls. see attachment) that UPS PIN1 should bee keept HI is mandatory. Should I connect it to PC PIN4 DTR?
Certainly possible. blazer_ser and nutdrv_qx should set DTR high and RTS low by default, but that can be adjusted.
> OR
>
> I need to follow with contact closure cable?
If the UPS is capable of the smart protocol, I still think that is worth trying first. But it's up to you....
2015 Nov 21
2
Contact-closure UPS
>> On Nov 21, 2015, at 2:43 AM, R?bert SZAKSZ <robert at szaksz.eu> wrote:
>>
>> I mesured it and on DC and it shows 0 V (zero V).
>> May be the information (pls. see attachment) that UPS PIN1 should bee keept HI is mandatory. Should I connect it to PC PIN4 DTR?
>
>Certainly possible. blazer_ser and nutdrv_qx should set DTR high and RTS low by default, but that can be adjusted.>
I will try to make both cables, but UPS PIN9 (TX) doesn't answer it seems like no power on it.
>>
>> OR
>>
>> I need to follow with con...
2015 Nov 20
2
Contact-closure UPS
No progress has been made:
cable is UPS - PC
6 - 3
7 - 5
9 - 2
for ./blazer_ser -DDDDD -a infosec
0.000000 send_to_all: SETINFO driver.parameter.port "/dev/ttyS1"
0.000323 debug level is '5'
0.103068 send_to_all: SETINFO device.type "ups"
0.103104 send_to_all: SETINFO driver.version "2.7.3"
0.103118 send_to_all: SETINFO