B&R 7DO135.70模擬量輸出模塊，7DO135.70使用配置教程
為了實現(xiàn)之間的高波特率串行通信172Bug和終端要工作，終端必須做一些握手的形式。如果正在使用的終端沒有通過CTS線路進行硬件握手，則必須這樣做XON/XOFF握手。如果你收到亂碼信息缺少字符，則應(yīng)檢查終端以確保已啟用XON/XOFF握手。4.如果您想連接設(shè)備（如主機系統(tǒng)和/或串行打印機）連接到其他EIA-232-D端口連接器，連接適當?shù)碾娎|并按照詳細說明配置端口上述步驟3中。
B&R 7DO135.70模擬量輸出模塊通電后，您可以重新配置這些端口通過編程MVME172LX Z85230串行通信控制器（SCC），或使用172Bug PF命令5.EPROM/Flash標頭J20必須設(shè)置為配置3，并且J20針腳5-6、8-10和9-11之間的跳線。這為512K x 8個EPROM。6、接通系統(tǒng)電源。172Bug執(zhí)行一些自檢，并如果固件在板上，則顯示調(diào)試器提示172 Bug模式但是，如果ENV命令將172Bug置于系統(tǒng)模式，系統(tǒng)執(zhí)行自檢并嘗試自動啟動。請參閱環(huán)境和菜單命令（表4-3）。如果置信度測試失敗，則在出現(xiàn)第一個故障時中止測試遇到。如果可能，將顯示適當?shù)南ⅲ⑶铱丶缓蠓祷夭藛巍?、初始安裝后使用MVME172LX前，設(shè)置使用以下命令行結(jié)構(gòu)的日期和時間：例如，以下命令行啟動實時時鐘并將日期和時間設(shè)置為1999年9月7日上午10:37：172 Bug>SET 0907991037Autoboot是包含在172Bug中的軟件例程閃存/可編程只讀存儲器提供獨立的啟動機制操作系統(tǒng)。自動啟動例程自動掃描控制器和設(shè)備，直到有效的可引導(dǎo)設(shè)備找到包含啟動介質(zhì)或列表已用盡。如果有效的可引導(dǎo)找到設(shè)備后，從該設(shè)備啟動?？刂破鲯呙栊蛄袕淖畹涂刂破鬟壿媶卧枺↙UN）開始檢測到檢測到的最高LUN?？刂破?、設(shè)備及其LUN見附錄D。通電時，Autoboot啟用（前提是驅(qū)動器和遇到的控制器編號有效）
In order for high-baud-rate serial communication between
172Bug and the terminal to work, the terminal must do some
form of handshaking. If the terminal being used does not do
hardware handshaking via the CTS line, then it must do
XON/XOFF handshaking. If you get garbled messages and
missing characters, then you should check the terminal to
make sure XON/XOFF handshaking is enabled.
4. If you want to connect devices (such as a host computer system
and/or a serial printer) to the other EIA-232-D port connectors,
connect the appropriate cables and configure the port(s) as detailed
in step 3 above. After power-up, you can reconfigure these port(s)
by programming the MVME172LX Z85230 Serial
Communications Controllers (SCCs), or by using the 172Bug PF
command.
5. The EPROM/Flash header J20 must be set to configuration 3, with
jumpers between J20 pins 5-6, 8-10, and 9-11. This sets it up for
512K x 8 EPROMs.
6. Power up the system. 172Bug executes some self-checks and
displays the debugger prompt 172-Bug> if the firmware is in Board
mode.
However, if the ENV command has put 172Bug in System mode,
the system performs a self-test and tries to autoboot. Refer to the
ENV and MENU commands (Table 4-3).
If the confidence test fails, the test is aborted when the first fault is
encountered. If possible, an appropriate message is displayed, and
control then returns to the menu.
7. Before using the MVME172LX after the initial installation, set the
date and time using the following command line structure:
For example, the following command line starts the real-time clock
and sets the date and time to 10:37 a.m., September 7, 1999:
172-Bug> SET 0907991037Autoboot is a software routine that is contained in the 172Bug
Flash/PROM to provide an independent mechanism for booting an
operating system. This autoboot routine automatically scans for controllers
and devices in a specified sequence until a valid bootable device
containing a boot media is found or the list is exhausted. If a valid bootable
device is found, a boot from that device is started. The controller scanning
sequence goes from the lowest controller Logical Unit Number (LUN)
detected to the highest LUN detected. Controllers, devices, and their LUNs
