search for: rxd

...I stopped now with configuration of genericups 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 |...

...genericups 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) 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...

...e(struct vmxnet3_rx_queue *rq, /* Immediate refill */ rbi->skb = new_skb; - rbi->dma_addr = pci_map_single(adapter->pdev, + rbi->dma_addr = dma_map_single(&adapter->pdev->dev, rbi->skb->data, rbi->len, PCI_DMA_FROMDEVICE); rxd->addr = cpu_to_le64(rbi->dma_addr); @@ -1267,7 +1275,7 @@ vmxnet3_rq_rx_complete(struct vmxnet3_rx_queue *rq, } if (rcd->len) { - pci_unmap_page(adapter->pdev, + dma_unmap_page(&adapter->pdev->dev, rbi->dma_addr, rbi->len, PCI_DM...

...e(struct vmxnet3_rx_queue *rq, /* Immediate refill */ rbi->skb = new_skb; - rbi->dma_addr = pci_map_single(adapter->pdev, + rbi->dma_addr = dma_map_single(&adapter->pdev->dev, rbi->skb->data, rbi->len, PCI_DMA_FROMDEVICE); rxd->addr = cpu_to_le64(rbi->dma_addr); @@ -1267,7 +1275,7 @@ vmxnet3_rq_rx_complete(struct vmxnet3_rx_queue *rq, } if (rcd->len) { - pci_unmap_page(adapter->pdev, + dma_unmap_page(&adapter->pdev->dev, rbi->dma_addr, rbi->len, PCI_DM...

...>> 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) > >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 >th...

>> 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

...| | | | | | | | CHASSIS 9<--------------//---------------------<5 SG | | | | | | | | TXD 2<--------------//---------------------<2 RXD | | | | | | | | RXD 1<--------------//---------------------<3 TXD | | | | | | | | - - +--<1 DCD | |...

...elps me. USB would be cool but I don't really need that, it just has to work. I have also found a document that shows the pinout of the com port (page 8) there: http://www.watfordcontrol.co.th/products/UPS/series_ae1/Catalog_A-19_A_E_engl(1999).pdf My question is, do I have to swap the TXD and RXD pins to get it working? I have tried to add the USB device address into the ups.conf and run the driver config tool thing. After a while it says: tcgetattr(/proc/bus/usb/004/002): Inappropriate ioctl for device After that I have tried the serial port, with a 1:1 cable, which didn't worked as w...

...???????? ? ? ? ? RxA 000000000000000000000000 ? Loop ? ? ? ? ? RxB 000000000000000000000000 ???????? ? ? ? ? RxC 000000000000000000000000 ? ? ? ? RxD 000000000000000000000000 ? If I make a call to one of the phone numbers in my block, the zttool output goes to this: ? Current Alarms: No alarms. ? ? ? ? Sync Source: Internally clocked ? ? ?...

...: Asterisk server hooked up to a digital T1 line (full 24-channel) via a Digium card. Verizon has turned on caller ID on the first line (I can guarantee it is on as I can hear the FSK tones on this line but not the others). Using zttool an ZapScan() I have determined the following: 1) The RxB/RxD bits toggle from 1 to 0 signaling a ring. 2) A short time later, via ZapScan() I can hear the FSK tone. 3) About the same time I hear the FSK tone I see the "Starting simple switch" line in the Asterisk console. 4) Next I see the second ring trigger in zttool and then Asterisk say &qu...

...esc { + u8 data[VMXNET3_HDR_COPY_SIZE]; +}; + + +struct Vmxnet3_TxCompDesc { + u32 txdIdx:12; /* Index of the EOP TxDesc */ + u32 ext1:20; + + u32 ext2; + u32 ext3; + + u32 rsvd:24; + u32 type:7; /* completion type */ + u32 gen:1; /* generation bit */ +}; + + +struct Vmxnet3_RxDesc { + u64 addr; + + u32 len:14; + u32 btype:1; /* Buffer Type */ + u32 dtype:1; /* Descriptor type */ + u32 rsvd:15; + u32 gen:1; /* Generation bit */ + + u32 ext1; +}; + +/* values of RXD.BTYPE */ +#define VMXNET3_RXD_BTYPE_HEAD 0 /* head only */ +#define VMXNET3_RXD_...

...esc { + u8 data[VMXNET3_HDR_COPY_SIZE]; +}; + + +struct Vmxnet3_TxCompDesc { + u32 txdIdx:12; /* Index of the EOP TxDesc */ + u32 ext1:20; + + u32 ext2; + u32 ext3; + + u32 rsvd:24; + u32 type:7; /* completion type */ + u32 gen:1; /* generation bit */ +}; + + +struct Vmxnet3_RxDesc { + u64 addr; + + u32 len:14; + u32 btype:1; /* Buffer Type */ + u32 dtype:1; /* Descriptor type */ + u32 rsvd:15; + u32 gen:1; /* Generation bit */ + + u32 ext1; +}; + +/* values of RXD.BTYPE */ +#define VMXNET3_RXD_BTYPE_HEAD 0 /* head only */ +#define VMXNET3_RXD_...

...esc { + u8 data[VMXNET3_HDR_COPY_SIZE]; +}; + + +struct Vmxnet3_TxCompDesc { + u32 txdIdx:12; /* Index of the EOP TxDesc */ + u32 ext1:20; + + u32 ext2; + u32 ext3; + + u32 rsvd:24; + u32 type:7; /* completion type */ + u32 gen:1; /* generation bit */ +}; + + +struct Vmxnet3_RxDesc { + u64 addr; + + u32 len:14; + u32 btype:1; /* Buffer Type */ + u32 dtype:1; /* Descriptor type */ + u32 rsvd:15; + u32 gen:1; /* Generation bit */ + + u32 ext1; +}; + +/* values of RXD.BTYPE */ +#define VMXNET3_RXD_BTYPE_HEAD 0 /* head only */ +#define VMXNET3_RXD_...

...esc { + u8 data[VMXNET3_HDR_COPY_SIZE]; +}; + + +struct Vmxnet3_TxCompDesc { + u32 txdIdx:12; /* Index of the EOP TxDesc */ + u32 ext1:20; + + u32 ext2; + u32 ext3; + + u32 rsvd:24; + u32 type:7; /* completion type */ + u32 gen:1; /* generation bit */ +}; + + +struct Vmxnet3_RxDesc { + u64 addr; + + u32 len:14; + u32 btype:1; /* Buffer Type */ + u32 dtype:1; /* Descriptor type */ + u32 rsvd:15; + u32 gen:1; /* Generation bit */ + + u32 ext1; +}; + +/* values of RXD.BTYPE */ +#define VMXNET3_RXD_BTYPE_HEAD 0 /* head only */ +#define VMXNET3_RXD_...

...esc { + u8 data[VMXNET3_HDR_COPY_SIZE]; +}; + + +struct Vmxnet3_TxCompDesc { + u32 txdIdx:12; /* Index of the EOP TxDesc */ + u32 ext1:20; + + u32 ext2; + u32 ext3; + + u32 rsvd:24; + u32 type:7; /* completion type */ + u32 gen:1; /* generation bit */ +}; + + +struct Vmxnet3_RxDesc { + u64 addr; + + u32 len:14; + u32 btype:1; /* Buffer Type */ + u32 dtype:1; /* Descriptor type */ + u32 rsvd:15; + u32 gen:1; /* Generation bit */ + + u32 ext1; +}; + +/* values of RXD.BTYPE */ +#define VMXNET3_RXD_BTYPE_HEAD 0 /* head only */ +#define VMXNET3_RXD_...

...esc { + u8 data[VMXNET3_HDR_COPY_SIZE]; +}; + + +struct Vmxnet3_TxCompDesc { + u32 txdIdx:12; /* Index of the EOP TxDesc */ + u32 ext1:20; + + u32 ext2; + u32 ext3; + + u32 rsvd:24; + u32 type:7; /* completion type */ + u32 gen:1; /* generation bit */ +}; + + +struct Vmxnet3_RxDesc { + u64 addr; + + u32 len:14; + u32 btype:1; /* Buffer Type */ + u32 dtype:1; /* Descriptor type */ + u32 rsvd:15; + u32 gen:1; /* Generation bit */ + + u32 ext1; +}; + +/* values of RXD.BTYPE */ +#define VMXNET3_RXD_BTYPE_HEAD 0 /* head only */ +#define VMXNET3_RXD_...

...pDesc { + uint32_t txdIdx:12; /* Index of the EOP TxDesc */ + uint32_t ext1:20; + + uint32_t ext2; + uint32_t ext3; + + uint32_t rsvd:24; + uint32_t type:7; /* completion type */ + uint32_t gen:1; /* generation bit */ +}; + + +struct Vmxnet3_RxDesc { + uint64_t addr; + + uint32_t len:14; + uint32_t btype:1; /* Buffer Type */ + uint32_t dtype:1; /* Descriptor type */ + uint32_t rsvd:15; + uint32_t gen:1; /* Generation bit */ + + uint32_t ext1; +}; + +/* values of RXD.BTYPE */ +#defi...

...pDesc { + uint32_t txdIdx:12; /* Index of the EOP TxDesc */ + uint32_t ext1:20; + + uint32_t ext2; + uint32_t ext3; + + uint32_t rsvd:24; + uint32_t type:7; /* completion type */ + uint32_t gen:1; /* generation bit */ +}; + + +struct Vmxnet3_RxDesc { + uint64_t addr; + + uint32_t len:14; + uint32_t btype:1; /* Buffer Type */ + uint32_t dtype:1; /* Descriptor type */ + uint32_t rsvd:15; + uint32_t gen:1; /* Generation bit */ + + uint32_t ext1; +}; + +/* values of RXD.BTYPE */ +#defi...

...is configured properly? After doing 'modprobe wct1xxp;ztcfg' I ran zttool. In the details for the T100P I saw: "Current Alarms: Red Alarm, Sync Source: Internally Clocked" ? TxA 00000000 ? TxB 11111111 ? TxC 00000000 ? TxD 11111111 ? RxA 00000111 ? RxB 11111010 ? RxC 00000000 ? RxD 00000000 Should the transmit and receive settings be mirror images of each other, or is this display correct given my situation? Unfortunately I don't understand what a good display would look like. On another topic, I've tried connecting to irc.freenode.net to join the #asterisk chann...

Hi, I'm trying to configure my ups with nut which is a locally made one. It uses a rs232 port to talk to the computer and comes with a software called "Powermanager Lite" which is provided by Richcomm and supports Windows, Linux and UNIX. According to the manual it uses the Richcomm circuitry to talk to the computer and uses a drycontact protocol. Unfortunately I couldn't