Difference between revisions of "IO12-Update"
m (→Hardware setup) |
m (→Hardware setup) |
||
Line 20: | Line 20: | ||
== Hardware setup == | == Hardware setup == | ||
# Connect the PC/Mac and the Barionet to your network switch or hub | # Connect the PC/Mac and the Barionet to your network switch or hub. | ||
# Prepare the power supply to connect it to the Barionet in a later step. | |||
# Depending on the kind of application control connection do the following: | # Depending on the kind of application control connection do the following: | ||
#: If you plan to use the TCP version of the application skip to step 3. | #:* If you plan to use the TCP version of the application skip to step 3. | ||
#: If you plan to use the serial version of the application: Connect the PC/Mac to the serial port of the Barionet with the cross cable | #:* If you plan to use the serial version of the application: Connect the PC/Mac to the serial port of the Barionet with the cross cable | ||
# Depending on | # Depending on which Barionet you choose wire the IO12 as following: | ||
#: If you use the Barionet 50: bridge the Barionet 50 (J10) and the IO12 (J9 or J10) using the supplied 4 pin extension cable. | #:* If you use the Barionet 50: bridge the Barionet 50 (J10) and the IO12 (J9 or J10) using the supplied 4 pin extension cable. | ||
#: If you use the Barionet 100: As the 4 pin extension cable is '''NOT''' supported, connect the Barionet 50 to the IO12 using 4 wires via the screw block terminals as following: | #:* If you use the Barionet 100: As the 4 pin extension cable is '''NOT''' supported, connect the Barionet 50 to the IO12 using 4 wires via the screw block terminals as following: | ||
{| | {| | ||
! width="30" rowspan=" | ! width="30" rowspan="6" | | ||
! | ! rowspan="6" | [[Image:Barionetpinout3.jpg|180px]] | ||
! width=" | ! width="80" bgcolor="#C22" align="center" style="color:#FFF;"| <sup>Barionet 100 | ||
! width=" | ! width="80" bgcolor="#C22" align="center" style="color:#FFF;"| <sup>Signal / Wire | ||
! width=" | ! width="80" bgcolor="#C22" align="center" style="color:#FFF;"| <sup>Barix IO12 | ||
! | ! rowspan="6" | [[Image:BarixIO12pinout.jpg|180px|right]] | ||
|- | |- | ||
| align="center" | <sup>J6 pin 15 | | align="center" | <sup>J6 pin 15 | ||
Line 50: | Line 51: | ||
| bgcolor="#EEE" align="center" | <sup>RS485 B | | bgcolor="#EEE" align="center" | <sup>RS485 B | ||
| bgcolor="#EEE" align="center" | <sup>J11 pin 3 | | bgcolor="#EEE" align="center" | <sup>J11 pin 3 | ||
|- | |||
| | |||
| | |||
| | |||
|} | |} | ||
<br> | <br> |
Revision as of 17:32, 17 February 2011
Products >> Automation and Control >> Barix_IO12 >> IO12-Update
This page describes how to update the firmware on an IO12.
The IO12 can be updated using a Barionet and a PC/Mac using a terminal program to control the BCL application named MBT (Modbus Tester & Loader). The terminal program can connect to the application MBT either via network (TCP) or a serial (RS-232) connection (two different BCL applications).
Prerequisites
Prepare the following material:
- PC or Mac with e and a terminal program such as hyperterm
- Optionally: a serial port (HW or USB2serial) and a serial cross cable (3 wire, DB9 female to DB9 female)
- A Barionet 50 (FW 2.00 or higher) or a Barionet 100 (FW 2.08 or higher)
- Modbus Test & Load BCL application (MBT_Vxx_S.cob for serial cable or MBT_Vxx_T.cob for TCP terminal)
- Power supply 9VDC (min.) to 30VDC (max.), to supply both Barionet and IO12, 300mA (min.)
- 4pin Extension cable to connect to Barionet 50 or 4 wires to connect to Barionet 100
⇒ Tips:
- Using a Barionet 50 is simpler as it needs no wiring: The supplied 4 pin extension cable can be used !
- Using the TCP version of the application is simpler as it needs no serial port and serial cable ! It works via the Ethernet network connection.
Hardware setup
- Connect the PC/Mac and the Barionet to your network switch or hub.
- Prepare the power supply to connect it to the Barionet in a later step.
- Depending on the kind of application control connection do the following:
- If you plan to use the TCP version of the application skip to step 3.
- If you plan to use the serial version of the application: Connect the PC/Mac to the serial port of the Barionet with the cross cable
- Depending on which Barionet you choose wire the IO12 as following:
- If you use the Barionet 50: bridge the Barionet 50 (J10) and the IO12 (J9 or J10) using the supplied 4 pin extension cable.
- If you use the Barionet 100: As the 4 pin extension cable is NOT supported, connect the Barionet 50 to the IO12 using 4 wires via the screw block terminals as following:
Error creating thumbnail: File missing
|
Barionet 100 | Signal / Wire | Barix IO12 | Error creating thumbnail: File missing | |
---|---|---|---|---|---|
J6 pin 15 | Power + | J5 pin 1 | |||
J6 pin 16 | Power - | J5 pin 3 | |||
J7 pin 4 | RS485 A | J11 pin 1 | |||
J7 pin 5 | RS485 B | J11 pin 3 | |||
Software setup
- Connect the PC/Mac and the Barionet to your network switch or hub
- Depending on the kind of application control connection do the following:
- If you plan to use the TCP version of the application:
- * Load the file MBT_Vxx_T.cob (xx is the version, at the time of writing: 11) into the Barionet's page WEB4 (Barionet 50: via extended web update, Barionet 100: via tftp), reboot when done and wait 10 seconds
- * Connect the PC/Mac to the serial port of the Barionet with the cross cable
- * Start a terminal program with the serial settings 9600,8,N,1 no HW control
- If you plan to use the serial version of the application:
- Load the file MBT_Vxx_S.cob (xx is the version, at the time of writing: 11) into the Barionet's page WEB4 (Barionet 50: via extended web update, Barionet 100: via tftp), reboot when done and wait 10 seconds
- ** Connect the PC/Mac to the serial port of the Barionet with the cross cable
- ** Start a terminal program with the serial settings 9600,8,N,1 no HW control
- Wire the X8 with the Barionet and power supply as following:
Firmware Update Quick Guide
The follwing steps give a quick run down on how to update the firmware on an IO12.
- Load a Barionet 50 or 100 with the latest Firmware
- Connect the IO 12 to the Barionet (BA50 4pin cable, BA100 2pin power & 2pin RS-485)
- Load the MBT application (either the T version for TCP terminal or the S for serial terminal on RS-232 into the Barionets WEB4 and reboot
- Connect the terminal (T: open TCP terminal to Port 12345 / S: open serial Terminal 9600,8,N,1 NoHW). The terminal shows:
Modbus and X8/R6 Test Application
Please select: 1 for factory, 2 for service mode, 3 for loader
- Hit the number 2 and hit the Enter (↵) key for sevice mode. The terminal shows:
Wadr,reg,val | Radr,reg,num or | sSadr,coil,val | bBadr | Is1,s2 | Cs1,s2 | Fs1,s2 | X ?
- To check if talking to the IO12 is possible enter R0,256,4 (capital R, zero, comma, two, five, six, comma, four) and hit the Enter (↵) key. The terminal shows:
R0,256,4
READ: 00B3 0008 000C 0052
- The first group of digits tells the HW Type (B3=IO12), the 2nd tells the current version (V8), the 3rd the Serial 1 (0xC=12 decimal) and the 4th the Serial 2 (0x52=82 decimal). Both serials can be found on the data plate of the IO12 !
- Now that we know that the connection works we can start with deleting the existing firmware by entering F12,82 (capital F, serial1, comma, serial2)
- ⇒ Make sure you use the correct serial numbers 1 and 2 (decimal values not hex) of YOUR device !!!
- and hit the Enter (↵) key. The terminal shows:
F12,82
?
Wadr,reg,val | Radr,reg,num or | sSadr,coil,val | bBadr | Is1,s2 | Cs1,s2 | Fs1,s2 | X ?
- ⇒ Do NOT be fooled by the question mark. The IO12 will carry out the Erase command and after 3 seconds the PWR LED will go dark.
- If the PWR LED stays lit then repeat step 7 carefully.
- If after repeating step 7 the PWR LED stays lit then check if your devices production week information on the data plate (bottom of the device):
- ⇒ If it was produced on or between PW50/10 and PW03/11 then you can NOT updated the device using this MBT method !
- ⇒ If this is the case the device must be returned to Barix (via reseller) for factory programming.
- Hit the X (capital X) and then hit the Enter (↵) key to exit the service mode. The terminal shows:
Modbus and X8/R6 Test Application
Please select: 1 for factory, 2 for service mode, 3 for loader
- Do NOT wait and hit the number 3 and hit the Enter (↵) key for loader mode. The terminal shows:
wrong serial setup - correcting & rebooting ..
- After the reboot the loader mode will be started automatically. The terminal shows:
Modbus and X8/R6 Test Application
Please select: 1 for factory, 2 for service mode, 3 for loader
loader started, please reset unit. Press F for erase command, S to send firmwar
- Hit the S (capital S) and then hit the Enter (↵) key to start the firmware update. The terminal shows:
sending firmware
end programming
- ⇒ This will take about 20 seconds (the RS-485 LED of the Barionet will flicker) and when done the PWR LED will be lit.
- If it stays dark power cycle the IO12 (disconnect the power wires, wait 4 seconds and reconnect power wires)
- If it still stays dark repeaet power cycling up to 3 more times
- If it stays dark go back to step 10 and repeat the erase command
- Hit the X (capital X) and then hit the Enter (↵) key to exit the loader mode. The terminal shows:
Please select: 1 for factory, 2 for service mode, 3 for loader
- Do NOT wait and hit the number 2 and hit the Enter (↵) key for service mode. The terminal shows:
wrong serial setup - correcting & rebooting ..
- After the reboot the terminal shows:
Modbus and X8/R6 Test Application
Please select: 1 for factory, 2 for service mode, 3 for loader
- Hit the number 2 and hit the Enter (↵) key for sevice mode. The terminal shows:
Wadr,reg,val | Radr,reg,num or | sSadr,coil,val | bBadr | Is1,s2 | Cs1,s2 | Fs1,s2 | X ?
- To check if the update of the IO12 went fine enter R0,256,4 (capital R, zero, comma, two, five, six, comma, four) and hit the Enter (↵) key. The terminal shows:
R0,256,4
READ: 00B3 000B 000C 0052
- The second group of digits tells the current firmware version (now 0xB = V11).
- ⇒ If it still says the old version then the update failed. Start over from the beginning.
Gratulations, you succesfully updated the device.
Back to FAQ