 | |
Предыдущие результаты
 Всё будет и так работать.
CNBR аппаратно проверяет исправность каждого канала связи (А и В) перед посылкой каждого пакета. Затем пакет посылается в тот канал, который имеет наименьшее затухание сигнала. Вот и всё. В Вашем случае CNBR, таким образом, каждый раз будет понимать, что работает только один канал, и посылать пакеты именно в него.
Firmware, конечно, должен быть идентичной ревизии, само собой.
|
База знаний, возможно, уже обновилась, поэтому части топиков нет, но можно набрать поиск по фразе типа string data types и попытаться полистать.
Вот, собственно, то, что у меня есть.
Background:
When using string data in the CL55xx processor with firmware version at 7 or earlier, integer storage must be allocated. Integer storage can be allocated as an SINT, INT, or DINT array. Additionally INT array data can be referenced in PLC5 emulation mode. Version 8 of the ControlLogix firmware introduced the string datatype. When the OPC node type is used, the following errors can be generated when the wrong address syntax is used. The DDE node type does not generate any errors when improperly configured, however the string data is not written correctly either.
Requirements for the native string tag support:
RSView32 6.30 previous versions of RSView32 should work as well, but were not tested.
RSLinx 2.30
ControlLogix firmware rev 8 or higher
The following paragraphs describe how the DDE/OPC implementation works, and how string data is stored in the CL55xx processor.
String Tag Configuration:
Traditionally RSView32 is looking for a string address equivalent to A10:0 or ST10:0. When the PLC5 ST datatype was introduced, 82 characters was the maximum supported. This 82 string length limit remains in the RSView32 product today. The CL55xx string data type stores the characters in a SINT array. String data can be stored in any type of integer array, SINT, INT, DINT when working with controllers at earlier versions of the firmware. Depending on the type of integer array selected the address syntax will vary.
Even though the RSView32 tag is defined as string data, RSLinx queries the data type from the processor. To allow RSView32 and RSLinx to write string data to integer storage - add the ,SSxx (string space pad) or the ,SCxx (string C null pad) to the address line, where xx indicates the number of elements to pad. The number of elements to pad depends on how the data is stored, the following table gives some examples. If the SCxx or SSxx syntax is omitted, RSView32 will only be able to access the 1st element in the integer array, and will not represent the data as the string entered, since it is integer.
There are some issues when writing to the new string datatype from RSView32. When working with variable length strings, RSView32 does not update the length field with the new string length. The improper initialization of the string length prevents ascii functions from working properly in the controller program. This issue is currently under investigation. A potential work around is to determine the length of the string in VBA code, and then manually write to the length element of the string data type.
Тут, правда, ниже табличка! Надеюсь поймете
CL5550 Datatype Description String Address Syntax Example1 String Address Syntax Example2
String 8 bit integer array String1.Data[0],SC82 String1.Data[0],m,SC82
SINT 8 bit integer SINTArray[0],SC82 SINTArray[0],m,SC82
INT 16 bit integer INTArray[0],SC41 INTArray[0],m,SC41
DINT 32 bit integer DINTArray[0],SC20 DINTArray[0],m,SC20
PLC5 emulation 16 bit integer N7:0,SC41 N7:0,m,SC41
PLC5 emulation mode may be required to read/write string data if the CL55xx firmware is at an earlier revision 4.x.
Controller Memory:
When using the string data type, the controller stores the string as a character in a element called .Data[x], where x is the character position. With the native string data type, there doesn't appear to be anyway to reference the entire string tag as was possible with the PLC5 string. Instead the RSView tag address references the first element of the SINT array that contains the string. The ,SC82 syntax tells RSLinx to get 82 bytes of string data.
When using an integer array to store string data, the controller stores the data in the integer array as the HEX equivalent of the character. For example, if a 12 is entered into a string input field, the data is converted to the hex equivalent (in this case 3132h) and is stored the processor tag name INTArray[0]. Since INTArray[0] actually stores 2 characters, examination of the individual bytes will show the 1 (31h) is stored in the high order byte, and the 2 (32h) is stored in the low order byte.
Consider the same example writing string data to the SINTArray, if a 12 is entered into a string input field, the SINTArray[0] = 2 (32h), SINTArray[1] = 1 (32h). Applying the ,m byte swap modifier to the address line does not alter the way the string data is written to the processor, it only swaps the way the data is viewed. A future release of RSLinx will correct this byte swapping for SINT arrays.
When RSView32 is performing both the string read and write, use the syntax example1. When the CL5550 processor is storing the string data, the high and low order byte may need to be swapped, use the syntax example2 to accomplish this on the read only.
It is more efficient to write null padded strings than space padded strings, therefore use the SCxx syntax when possible.
Background:
RSView32, RSView SE and RSSql can browse tag addresses from an on-line controller using OPC. However, string tags in a ControlLogix family controller (added in firmware version 8) and bit-level addresses in a PLC-5 or SLC-500 cannot be browsed directly.
String tags are actually stored in the ControlLogix as numeric data. When the OPC browser tries to update the string tag's address field, the client correctly determines that a data type mismatch has occurred. It therefore does not allow the address field to be updated.
For digital addresses in a PLC-5 or SLC-500, RSLinx does not allow browsing to the bit level. Examples: "B3:0" can be browsed, but "B3:0/3" cannot be browsed. However, a Boolean tag in a ControlLogix processor can be browsed.
Solution:
For String addresses in a ControlLogix processor:
1. Create a DIGITAL tag (if client is RSView32 or RSView SE)
2. Browse to the string tag in the ControlLogix (example: StringTag )
3. Select the StringTag.DATA element and press OK
4. Remove the .DATA manually from the end of the item address
5. Change the tag data type to STRING.
Example of correct item address syntax: [TopicName]StringTag
Example of incorrect item address syntax: [TopicName]StringTag.DATA
Note: This syntax is tested with firmware version 10 per tech note A27556111 (see references below).
Important: In RSView32 and RSView SE - if step 5 is skipped and the tag is accepted, it will not be possible to change the tag data type. In this case it would be necessary to delete the tag and start again with step 1.
For Digital addresses in a PLC-5 or SLC-500:
1. Browse to the word level (example: B3:0 )
2. Select the word containing the desired bit and press OK
3. Add the bit delimiter manually to the end of the item address. Example of correct item address syntax: [TopicName]B3:0/2
For further reference, see the following tech notes:
A5550 - How to address the different data types in the ControlLogix 5550 processor
A7004 - Reading and writing string data from RSView32 to ControlLogix 55xx
A27556111 - How to manage variable length string writes from a HMI to ControlLogix
A4814 - How to configure RSView32 to communicate to a ControlLogix 5550 processor
Успехов.
Vitaliy D. Burtsev
|
При конфигурации ControlNet не стоит забывать назначить Keeper используя RSNetworx for ControlNet,
это одна из common ошибок пользователей.
Как осуществить замену модуля CNB(R) и проделать эту процедуру(Setup Keeper) при redundant конфигурации
можно найти в документе 1756-UM523 ControlLogix Redundancy System на странице 107.
Думаю также будет полезно посмотреть ID 28720, 36202,46577
И конечно на последок, как отметил OldDad, нужно использовать firmware из подходящего redundancy bundle. :)
Успехов.
|
Понятно. Вам нужно перепрошить модуль более новой ревизией firmware. Имейте в виду, что Вы не можете перепрошить с 6.1 сразу на 6.3, а сперва нужно прошить 6.2, а только потом 6.3.
Проверьте, не Ваш ли это случай:
[quote:d79e4acb3e]
1756-DHRIO Series D revision 6.1 Stops Responding.
Question
1756-DHRIO Ser D revision 6.1 Stops Responding
Answer
1756-DHRIO/D Revision 6.1 Stops Responding
Problem: It has been identified that 1756-DHRIO series D firmware version 6.1 modules may stop communicating with external devices via DH+ or Remote I/O under certain conditions.
Cause: After 100 connections have been made to the module an error occurred that caused future connections to produce timeout errors until the module was reset. This happened with any kind of connection, such as, block transfers, DH+, CIP generic, etc.
This anomaly may cause the following symptoms:
* The module errors with error code 203 and 100 when trying to do Block Transfers un-cached to an I/O module. The Block transfers will not resume after the communication is interrupted.
* Communication with RSLogix 5000 software can no longer be established. Message "Not a Logix Controller" (error 701-8004204C). Communication will not resume until module is reset.
* Messages (MSG) going through the module may not complete and fault.
* The Module may not work in some hardware gateway applications, particularly with PLC3 to PLC3 messaging via DHRIO gateway.
* RSLinx Software tries to access device properties, the user gets a message "Unable to establish communications with the device".
Solution:
* Temporary fix is to power cycle the r6.1 module and it's good for another 100 connections.
* Cure is to Flash upgrade 1756-DHRIO/D module firmware to version 6.2 or higher. Firmware available for download at
http://support.rockwellautomation.com/ControlFlash/
or from your local distributor. Please note that FW 6.2 is incompatible with Ser A, B and C modules.
=================
You cannot flash a 6.1 revision module directly to 6.3. You must first flash the module ot 6.2 then to 6.3. Going directly from 6.1 to 6.3 will cause the module to not power up.
In one case the module displayed “++++;A9;>++++x1yo” after attempting to go from 6.1 to 6.3 directly. Once this occurs the module will have to be returned for repair.
==================
Other Notes
Please note that it is NOT POSSIBLE to re-flash:
- Series D module back to Series C rev 5.x or earlier
- Series A, B, C to Series D rev 6.2 or higher
[/quote:d79e4acb3e]
|
Рекомендации производителя следующие:
1) Don't touch the running system без необходимости
2) Ревизии firmware следует актуализировать, т.к. новая ревизия обычно лучше прежней
3) Лучше, чтобы однотипные модули имели идентичные ревизии.
4) Если сомневаетесь, см. п.1 :)
|
Практика - критерий истины:
[quote:f1685be58a]Cause: After approximately 3 to 4 months of continuous operation, ControlLogix and FlexLogix controllers at the firmware revisions listed above experience a non-recoverable major fault. Continuous operation is defined as the controller being powered up in any mode (program, run, remote, or remote run).
[/quote:f1685be58a]
[quote:f1685be58a]
Prevention: This can be prevented by:
1. Upgrading the firmware to the latest revisions, listed above.[/quote:f1685be58a]
Давайте попробуем? :)
|
На заметку,
Недавно появилось firmware 16.54
|
[quote:e61b672d91]если не секрет, в насколько обозримом будущем , планируется следующий релиз!! есть такая инфа?[/quote:e61b672d91]
Уважаемый колега,
Какие могут быть секреты от Вас в нашей отрасли?
Теоретически ваше запрос можно реализовывать хоть сейчас же.
Прежде всего хочу уведомить о появлении нового модуля для резервирования 1756-RM (1756-IN092A-EN-P April 2008).
Этот модуль занимает всего один слот, и его конфигурация через RSLinx аналогична предшественнику 1757-SRM.
Этот модуль предназначен для работы в комплекте с 1756-CN2, 1756-CN2R and 1756- EN2T.
Еще хочу заметить, что в каждой из корзин могут находиться по 2 процессора (L61-L63), а L64 может быть только один.
Модуль имеет reduced switchover time (up to 10 ms).
С другой стороны модуль не будет работать с традиционными CNB(R) and ENBT, и также нельзя строить систему,
имея в основной корзине 1756-RM а в резервной 1757-SRM или наоборот.
С Hardware все на этом. С Software проще, тот же Logix5000 и Linx.
[quote:e61b672d91]Придётся подождать до следующего релиза firmware, когда эти модули туда пропишут. [/quote:e61b672d91]
Теперь о Firmware. Только только появился redundancy bundle 16.50 и сразу же за ним было обьявленно еще о 2х (16.53 для Standard
Redundancy System and 16.53 for Enhanced Redundancy System). Смотрим 1756-RN628G-EN-E and 1756-RN650A-EN-E.
You will see two firmware bundles on the RA support site within two weeks (I hope so :) ). For Enhanced Redundancy System please
use file with name: V16.53EnhClxRed. Вот и с теоретической частью покончено.
А по практической, я не знаю когда это добро появится в Мариуполе, вам виднее. Так что вот так. Дерзайте.
Спасибо за внимание.
|
[quote:5cb958df48="oldDad"]Придётся подождать до следующего релиза firmware, когда эти модули туда пропишут.[/quote:5cb958df48]
если не секрет, в насколько обозримом будущем , планируется следующий релиз!! есть такая инфа?
|
Придётся подождать до следующего релиза firmware, когда эти модули туда пропишут.
|
Предыдущие результаты
Ещё результаты |
|
| |
|
