This product is no longer available and has been replaced by: LOGGERLINK. Some accessories, replacement parts, or services may still be available.
| Services Available | |
|---|---|
| Repair | No |
| Calibration | No |
| Free Support | No |
Overview
Current Version: 2.33
PConnectCE software supports communications between a Campbell Scientific datalogger and a PocketPC or Windows Mobile device. PConnectCE allows you to go into the field carrying only your PDA and cables instead of having to lug a laptop computer to communicate with your datalogger and collect your data.
Read MoreImages
Detailed Description
PConnectCE can be used to collect data from the datalogger, and transfer the data to an office PC. Collected data are transferred to the PC during the ActiveSync® process. This process also synchronizes program files between the handheld and the PC.
Functions supported by PConnectCE includes the capability to:
- Create unique station files for each datalogger
- Collect data from the datalogger
- Display real-time datalogger measurements. Measurements are updated every two seconds.
- Set datalogger flags, ports, and clock
- Access the datalogger terminal mode
- Transfer datalogger programs between the datalogger and handheld
- Display Final Storage data in tabular or comma-separated format
- Communicate using a direct serial connection, RF401-series Spread Spectrum Radio, or Bluetooth
- Graph one element from any array
- Communicate at baud rates of 38,400 bps (CR800, CR850, CR1000, CR23X, CR3000) and 9,600 bps (all other dataloggers)
DCE/DTE Information
PConnectCE ships with connectors and cables that assume the PDA acts as a DCE device (data communications equipment), with the 9-pin cable terminating in a female connection. Some PDAs act like a DTE device (data terminal equipment) and the 9-pin cable terminates in a male connection. If this is the case, for communication via the CS I/O port, you will most likely use an SC32B (purchased separately) in place of the PDA-to-CSI/O connector that ships with the software. To communicate via the datalogger's RS-232 port, the PDA's serial cable can be plugged in directly to the datalogger's RS-232 port (or a standard serial cable can be used if extended cable length is required). There may be exceptions, however, to this general rule. If you have questions about the RS-232 capabilities of your handheld device, check with the device manufacturer.
Specifications
| Current Version | Version 2.33 began shipping in May 2008. |
| Software Requirements |
|
| PDA Operating System | Microsoft Pocket PC or Windows Mobile |
| Operating Temperature | -25° to +50°C |
| CE Compliance | CE Compliant |
| PDA to RS-232 Cable Length | 38.0 cm (15.0 in.) |
| PDA to RS-232 Cable Weight | 75 g (2.6 oz) |
| PDA to CS I/O Connector Dimensions | 2.3 x 4.1 x 7.6 cm (0.9 x 1.6 x 3.0 in.) |
| PDA to CS I/O Connector Weight | 41 g (1.6 oz) |
Compatibility
Please note: The following shows notable compatibility information. It is not a comprehensive list of all compatible products.
Dataloggers
| Product | Compatible | Note |
|---|---|---|
| 21X (retired) | ||
| CR10 (retired) | ||
| CR1000 (retired) | The CR200X-series and CR1000 dataloggers require PConnectCE version 2.0 or higher. | |
| CR10X (retired) | For the CR510, CR10X, and CR23X, support for both the mixed-array and PakBus® data logger operating systems is provided in PConnectCE version 2.0 or higher; prior versions only supported the mixed-array OS. | |
| CR200X (retired) | The CR200X-series and CR1000 dataloggers require PConnectCE version 2.0 or higher. | |
| CR206X (retired) | The CR200X-series and CR1000 dataloggers require PConnectCE version 2.0 or higher. | |
| CR211X (retired) | The CR200X-series and CR1000 dataloggers require PConnectCE version 2.0 or higher. | |
| CR216X (retired) | The CR200X-series and CR1000 dataloggers require PConnectCE version 2.0 or higher. | |
| CR23X (retired) | For the CR510, CR10X, and CR23X, support for both the mixed-array and PakBus® data logger operating systems is provided in PConnectCE version 2.0 or higher; prior versions only supported the mixed-array OS. | |
| CR295X (retired) | The CR200X-series and CR1000 dataloggers require PConnectCE version 2.0 or higher. | |
| CR3000 (retired) | The CR3000 requires PConnectCE version 2.1 or higher. | |
| CR500 (retired) | ||
| CR5000 (retired) | ||
| CR510 (retired) | For the CR510, CR10X, and CR23X, support for both the mixed-array and PakBus® data logger operating systems is provided in PConnectCE version 2.0 or higher; prior versions only supported the mixed-array OS. | |
| CR800 (retired) | The CR800 and CR850 require PConnectCE version 2.2 or higher. | |
| CR850 (retired) | The CR800 and CR850 require PConnectCE version 2.2 or higher. | |
| CR9000 (retired) | ||
| CR9000X (retired) |
Additional Compatibility Information
Data Logger Considerations
Data Logger Interfacing
- PDA-to-CS I/O connector or PDA-to-RS232 cable.
--OR--
- SC-IRDA Infrared Interface connects to the CS I/O port (not compatible w/CR200(X)-series)
PDA Requirements
- Operating system: Microsoft Pocket PC or Windows Mobile®
- Must be capable of serial communication
- If using the SC-IRDA, the PDA must have an IRDA port and an IR chip set compatible with the SC-IRDA.
- For Bluetooth communication, the handheld must be Bluetooth enabled.
- Pocket PCs or Mobile Handhelds Tested by Campbell Scientific
Communication Requirements
PDA Connection for Serial Communication
PDA-to-serial cable or cradle (one end of the cable/cradle must terminate in a 9-pin serial connector) is required. The cable/cradle connects to the PDA-to-CS I/O connector or PDA-to-RS232 cable via the 9-pin serial connector. This cable/cradle may be included with the PDA, or it may need to be purchased as a separate accessory from the PDA manufacturer or a third party supplier.
Bluetooth Communication
Third-party Bluetooth serial adapter is required. The interface and/or cables that are used to connect the adapter to the data logger will vary, depending upon whether the device acts like a DTE (computer) device or DCE (PDA) device. In some instances, this is evident by the pin-out of the adapter, but not always. A general rule is if the adapter has a 9-pin female connector, then the adapter is connected to the data logger using the PDA-to-CS I/O connector for the CS I/O port or the PDA-to-RS232 cable for the RS-232 port. If the adapter has a 9-pin male connector, then the adapter is connected to the data logger using an SC32B for the CS I/O port or it can be connected directly to the RS-232 port.
Software
- A compatible version of Microsoft ActiveSync installed on the PC
- One copy of PConnectCE software per handheld
Documents
Product Brochures
Downloads
PCONNECTCE Patch v.2.33 (1.65 MB) 22-05-2008
Upgrade PConnectCE 2.0, 2.1 or 2.2 to 2.33.
PConnectCE 2.0, 2.1 or 2.2 must be installed on your machine.
Frequently Asked Questions
Number of FAQs related to PCONNECTCE: 2
-
PConnectCE version 2.x provides support for:
- Our PakBus data loggers
- Infrared (IR) communication
- Bluetooth communication
- COM ports greater than 2
-
Data files are stored on the PDA in a binary format with a .bdf extension. When they are transferred during the hot sync process, PConnectCE converts them to comma-separated ASCII. The collected data files must be saved in the My Documents folder on the PDA; if not, the conversion process does not take place. The files are transferred to the PC in their original format with a .bdf extension.
Try copying the BDF file back to the PDA in the My Documents folder. Then perform the hot sync again. If the file has not been corrupted in the copying process, PConnectCE should find it in the appropriate directory during the next hot sync and perform the conversion.
The files are also transferred in their original format if a process other than PConnectCE transfers the file before PConnectCE is able to transfer it. To resolve this issue, disable any other processes in ActiveSync/Windows Mobile Device Center that may be transferring the file. After resolving the issue, try copying the BDF file back to the PDA in the My Documents folder, and perform the hot sync again.