要約
LabVIEW™ is a graphical programming tool used in production and laboratory environments to collect data and supply control signals to monitor and control the environment it's monitoring. The DS3900 is an RS-232 to 2-wire interface which is designed to provide a hardware/firmware interface between a PC's serial port and any 2-wire device.
This application brief describes how to use LabVIEW, via a PC serial port to control a 2-wire interface. An interface to a DS1086 is given as an example. The brief also describes how to configure the LabVIEW graphical user interface (GUI) to communicate to the DS3900 serial port adapter. Examples are given on how to manipulate the register settings in a DS1086 low-EMI EconOscillator™. Flow charts showing the details on how to communicate to the DS1086 are provided.
The DS3900 serial port to 2-wire adapter is not a product intended for sale except in development kits offered by Dallas Semiconductor in support of 2-wire devices such as the DS1086. Although, written for the DS1086, this application note can be used to develop a LabVIEW-based interface to any Dallas or Maxim 2-wire devices.
Introduction
LabVIEW is a graphical programming tool that is used in the lab to interface with hardware and lab equipment. The graphical LabVIEW program replaces traditional code, which reduces development time by using the pre-made modules, called Virtual Instruments (VIs). LabVIEW has serial VIs that communicate to the serial port on a PC. These serial VIs can be used to communicate with a 2-wire device using a DS3900 that accepts data and commands from the serial port and converts the information to 2-wire protocol.
This application note provides an example showing how LabVIEW can be used to communicate with 2-wire devices. The LabVIEW example VI can be downloaded from the Dallas Semiconductor FTP site. The LabVIEW software package is required in order to run the LabVIEW example VI.
Hardware Requirements
The only hardware that is required to use the LabVIEW example VI is a DS3900. Although, if a customer application board has a means to communicate 2-wire, the DS3900 is not needed but the LabVIEW example VI may need to be modified.
The DS3900 provides a way to communicate 2-wire using a PC's serial port. The DS3900 utilizes a MAX3223 RS232 transceiver to translate the serial port signal levels from ±12V to voltage levels for a microprocessor. The microprocessor is then able to communicate to the PC by using its universal asynchronous receiver transmitter (UART). The functional diagram for the DS3900 is shown in Figure 1. For more information, refer to the DS3900 data sheet.
2-Wire Protocol
The LabVIEW example VI (communicate_2wire.vi) communicates over the serial port using DS3900 2-wire commands. When writing to a device, the following commands need to be sent: start, control, register address, data, and stop. When reading from a device, the following commands need to be sent: start, control, register address, start (repeated), control, data, and stop. All commands are in hexadecimal. See the DS1086 2-Wire Example section.
DS1086 2-Wire Example
The DS1086 is a programmable frequency synthesizer that has a 2-wire interface. An example of the bytes sent and received during 2-wire communication for the DS1086 is shown in Tables 1 and 2. In this example, the VI will write and read F0h to register 02h in the DS1086. Although the DS1086 is used in this application note, any 2-wire device can be used with the LabVIEW example VI.
Each 2-wire command consists of two bytes. The first byte in each command determines the type of operation to be performed. The second byte will vary except for the start and stop commands. The second control byte consists of the device identifier, device address, and R/W bit. When the R/W bit is set to 0, data is written to the device. To read from a device, the R/W bit in the first control command should be set to 0 and the R/W bit in the second control command should be set to 1. The second register address byte is the register that is being written or read and the data to send or receive is in the second data byte. After each command is sent to the device, an acknowledge byte or bytes is received.
Command | 1st Byte Sent | 2nd Byte Sent | 1st Byte Received | Notes |
Start | 0xA0 | 0x00 | 0xB0 ack |
2-Wire Start |
Control | 0xA1 | 0xB0 | 0xB1 ack |
Device Identifier = 1011, Device Address = 000, R/W = 0 |
Register Address |
0xA1 | 0x02 | 0xB1 ack |
Send Register Address (0x02) |
Data | 0xA1 | 0xF0 | 0xB1 ack |
Send Data to Write (0xF0) |
Stop | 0xA3 | 0x00 | 0xB3 ack |
2-Wire Stop |
Command | 1st Byte Sent | 2nd Byte Sent | 1st Byte Received | 2nd Byte Received | Notes |
Start | 0xA0 | 0x00 | 0xB0 ack |
2-Wire Start | |
Control | 0xA1 | 0xB0 | 0xB1 ack |
Device Identifier = 1011, Device Address = 000, R/W = 0 |
|
Register Address |
0xA1 | 0x02 | 0xB1 ack |
Send Register Address (0x02) | |
Repeated Start |
0xA0 | 0x00 | 0xB0 ack |
2-Wire Start | |
Control | 0xA1 | 0xB0 | 0xB1 ack |
Device Identifier = 1011, Device Address = 000, R/W = 1 |
|
Data | 0xA2 | 0x00 | 0xF1 ack |
0xB2 ack |
Send Data to Write (0xF0) |
Stop | 0xA3 | 0x00 | 0xB3 ack |
2-Wire Stop |
The following hardware components were used to communicate to a DS1086 with the LabVIEW VI: PC with a serial port, DS3900, and a DS1086. Figure 2 shows how to connect the DS1086 to the DS3900.
LabVIEW
The LabVIEW program (communicate_2wire.vi) allows the user to enter serial port settings and either read or write to the 2-wire device.
The communicate_2wire.vi performs the following actions (also see Figure 3):
- Prompts user for serial port settings
- Configures serial port
- Determines whether to read or write to a register by user input
- Writes or reads register entered by user
- Returns acknowledge bytes
- Returns value in register during a read
To use the LabVIEW program:
- Download 2wire.zip from Maxim's FTP site
- Unzip the files and double-click on communicate_2wire.vi
- Enter serial port settings and click Continue (see Figure 4)
- Enter register (see Figure 5)
- Enter data, if writing
- Click on RUN
- Click on STOP when finished running program and close application
The internal structure of the VI follows the sequence shown below (also shown in more detail in Figure 3). First, the VI reads in the serial port settings provided by the user and displays the chosen settings on the front panel. Figure 6 shows the section of the LabVIEW VI diagram that configures the serial port settings.
When the RUN button is clicked, the program sends the data entered on the front panel through the serial port to the DS3900 and finally to the 2-wire device. If the user chooses to write data, the write loop completes (see Figure 7).
In Figures 7 and 8 the start command has already been completed. Next, the control command is sent to the DS3900 and the acknowledge byte is returned. An acknowledge byte is always read after a command byte is sent. After the data command is complete the stop command is sent.
If the user chooses to read data, the read loop will complete (see Figure 8).
After the write or read is completed, the program waits for the user to write or read another register or stop the program. If the STOP button is clicked, the program will stop even if it is not finished writing to the 2- wire device.
Conclusions
This application note shows how to communicate with a 2-wire device using a LabVIEW VI. There are many advantages to using the LabVIEW 2-wire program. The LabVIEW program helps to reduce development time in two ways: no software needs to be written and no additional hardware except for the DS3900 is needed. LabVIEW can also be used to automate device testing by interfacing LabVIEW with GPIB equipment.
The DS1086 was shown as an example in this application note of how to read and write from one-byte registers, but any 2-wire device can be used with the LabVIEW VI.
The LabVIEW VI can be found in a zip file (2wire.zip). There are two VIs in the zip file: communicate_2wire.vi and Get COM Port Settings2.vi. Get COM Port Settings2.vi is a VI that communicate_2wire.vi references.
NOTE: The software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall Dallas Semiconductor be liable for any claim, damages or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the software or the use or other dealings in the software.