PI Server 3.4.380.70 (3.4.380 SP1) is released. This is the first service pack release to PI Server 3.4.380, and also an upgrade to all versions of the PI Server prior to PI Server 2010.
PI Server 3.4.380.36 (September, 2009) was the first release to deliver full integration with Microsoft Windows Integrated Security (WIS), as part of a new security model. As with the original 3.4.380 release, Windows Security is recommended but not required with PI Server 3.4.380 SP1, and can be enabled gradually over time without any disruption to users.
PI Server 3.4.380 SP1 is a complete setup kit that can upgrade existing systems, or install new configurations. This service pack release includes a total of 109 fixes and 37 minor changes or enhancements, which together increase the overall reliability and maintainability of your PI System. For all systems earlier than 2010, PI Server 3.4.380 SP1 is the most stable and most secure PI Server version, and is highly recommended for all customers. The fixes and enhancements in PI Server 3.4.380 SP1 are cumulative and address issues present not only in 3.4.380, but also in earlier versions of the PI Server.
PI Server 3.4.380 SP1 is recommended for all customers who have not upgraded to PI Server 2010, particularly if any of the following scenarios apply:
Running on 64-bit system with more than 2GB RAM
Running on VM with heavy Host CPU load
Installing on Windows Server 2008 R2 Core
Using High Availability over unreliable networks
Using Windows security over unreliable networks
Authenticating with Windows security on Citrix
Writing to PI archives stored on SAN/NAS
Sending large amounts of out-of-order events
Making large archive summary calls
Executing many batch queries
Applying VSS backups with large number of archives
Using COM Connectors
See the Release Notes for a complete list of changes, as well as information on how to plan your deployment.
28 April 2011
Difference Between a Null Modem and Straight Through Serial Cable
taken from:
http://digital.ni.com/public.nsf/allkb/1EE0DD8AF67922FA86256F720071DECF
The null modem cable is frequently called a crossover cable. It is used to allow two serial Data Terminal Equipment (DTE) devices to communicate with each other without using a modem or a Data Communications Equipment (DCE) device in between. For this to happen, the Transmit (TXD) pin of one device needs to be connected to the Receive (RXD) pin of the other device. To enable handshaking between the two devices, the Request to Send (RTS) pin of one device must be connected to the Clear to Send (CTS) pin of the other device. Because these pins are "crossed" on the two cable terminals, the name crossover cable is used.
A straight-through cable is used to connect a DTE device to a DCE device. The TXD-RXD and RTS-CTS pins are not cross-connected in this case, hence the term straight through cable.
The built-in serial port on a PC is a DTE device. Modems and printers are examples of DCE devices. Note that an instrument with serial interface could be either a DTE or a DCE device. It is best to check the user manual of the instrument to find out the device type. For more information regarding DTE and DCE devices, please see the links below.
To tell if your cable is null modem or straight though, you can search the part number at ni.com, the product description will tell if it is null modem. Alternatively you can use a hand held DMM to test continuity on the individual pins of your serial cable. If every pin is electrically connected to the corresponding pin on the other end, i.e.: pin 1 to pin1, pin 2 to pin 2, etc. then the cable is straight through.
http://digital.ni.com/public.nsf/allkb/1EE0DD8AF67922FA86256F720071DECF
The null modem cable is frequently called a crossover cable. It is used to allow two serial Data Terminal Equipment (DTE) devices to communicate with each other without using a modem or a Data Communications Equipment (DCE) device in between. For this to happen, the Transmit (TXD) pin of one device needs to be connected to the Receive (RXD) pin of the other device. To enable handshaking between the two devices, the Request to Send (RTS) pin of one device must be connected to the Clear to Send (CTS) pin of the other device. Because these pins are "crossed" on the two cable terminals, the name crossover cable is used.
A straight-through cable is used to connect a DTE device to a DCE device. The TXD-RXD and RTS-CTS pins are not cross-connected in this case, hence the term straight through cable.
The built-in serial port on a PC is a DTE device. Modems and printers are examples of DCE devices. Note that an instrument with serial interface could be either a DTE or a DCE device. It is best to check the user manual of the instrument to find out the device type. For more information regarding DTE and DCE devices, please see the links below.
To tell if your cable is null modem or straight though, you can search the part number at ni.com, the product description will tell if it is null modem. Alternatively you can use a hand held DMM to test continuity on the individual pins of your serial cable. If every pin is electrically connected to the corresponding pin on the other end, i.e.: pin 1 to pin1, pin 2 to pin 2, etc. then the cable is straight through.
19 April 2011
Subscribe to:
Posts (Atom)