Error message

IdealDan

Member
Join Date
May 2017
Location
MA
Posts
480
Hi Guys
Can I just experience favour from someone please?
I really need an idea on how to correct below PB32/FT ME Migration error:
1. Tag es temp: Bit Array tags are not supported. Tag will be converted as a memory tag.
Migration guide recommend Changing the tag address to a full word address but I really understand.

2, Screen 2 - GENERAL VIEW: Message display object will be converted to Multistate Indicator object at (224, 88).

I THANK YOU IN ADVANCE.
 
Can you post screenshots of you error message? It sounds like something is wrong with your Device Tag mapping.
 
Can you post screenshots of you error message? It sounds like something is wrong with your Device Tag mapping.
Hi Firend! Here is the screen shot,I'll apreciate your input

Tag pt502: The maximum value for this tag was invalid and has been set to the maximum valid value based on the tag's data type.
Tag pt503: The maximum value for this tag was invalid and has been set to the maximum valid value based on the tag's data type.
Tag es_temp_al: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag comp1_pk961d: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag tt501: The maximum value for this tag was invalid and has been set to the maximum valid value based on the tag's data type.
Tag at504: The maximum value for this tag was invalid and has been set to the maximum valid value based on the tag's data type.
Tag tt502: The maximum value for this tag was invalid and has been set to the maximum valid value based on the tag's data type.
Tag tg_mois_hm: Bit Array tags are not supported. Tag will be converted as a memory tag.

Tag f0501d: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag pk961d_ram: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag chauf_961a: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag chauf_961b: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag ka961: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag cr_temp_al: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag chauf_961c: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag pk961a_rat: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag es_mois_al: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag chauf_961d: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag pk961a_bat: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag pk961b_rat: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag pk961b_bat: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag tg_temp_al: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag comp1_pk961a: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag pk961c_rat: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag pt501: The maximum value for this tag was invalid and has been set to the maximum valid value based on the tag's data type.
Tag comp1_pk961b: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag ka962a: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag pk961c_bat: Bit Array tags are not supported. Tag will be converted as a memory tag.
Tag pk961d_rat: Bit Array tags are not supported. Tag will be converted as a memory tag.
Bit and LSBit triggered alarms that used a Trigger Tag with a Bit data type will only be able to trigger a single alarm after import.
Alarm message Ack option not supported.
Blinking color images are not supported.
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (214, 70).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (234, 105).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (54, 70).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (44, 412).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (360, 412).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (454, 70).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (200, 214).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (200, 239).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (200, 263).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (24, 233).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (24, 293).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (340, 232).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (340, 292).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (197, 346).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (514, 345).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (44, 448).
Screen 4 - 82PK961C_D: Message display object will be converted to Multistate Indicator object at (360, 448).
Screen 2 - GENERAL VIEW: Message display object will be converted to Multistate Indicator object at (224, 88).
Screen 2 - GENERAL VIEW: Message display object will be converted to Multistate Indicator object at (12, 28).
Screen 2 - GENERAL VIEW: Message display object will be converted to Multistate Indicator object at (424, 80).
Screen 2 - GENERAL VIEW: Message display object will be converted to Multistate Indicator object at (535, 80).
Screen 2 - GENERAL VIEW: Message display object will be converted to Multistate Indicator object at (5, 80).
Screen 2 - GENERAL VIEW: Message display object will be converted to Multistate Indicator object at (115, 80).
Screen 2 - GENERAL VIEW: Message display object will be converted to Multistate Indicator object at (33, 174).
Screen 2 - GENERAL VIEW: Message display object will be converted to Multistate Indicator object at (200, 188).
Screen 2 - GENERAL VIEW: Message display object will be converted to Multistate Indicator object at (496, 236).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (215, 70).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (235, 105).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (55, 70).
Screen 3 - 82PK961A_B: Print flag for multistate indicator or message display at (257, 323) not supported.
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (44, 412).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (360, 412).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (200, 214).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (200, 239).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (200, 264).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (455, 70).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (516, 212).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (516, 237).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (516, 262).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (24, 233).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (24, 293).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (340, 232).
Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (340, 292).
 
It sounds like you will have to go through your tags and check the Device Tag mapping and the Min and Max values.
 
It sounds like you will have to go through your tags and check the Device Tag mapping and the Min and Max values.
Ok, Thanks.
For this ''Tag pk961b_rat: Bit Array tags are not supported. Tag will be converted as a memory tag.''
I Have changed the DATA TYPE to INTEGER on Factory Talk Tag Dialog box, IS THIS APPROACH CORRECT?

What do you think of this one? ''Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (340, 292).''
 
Ok, Thanks.
For this ''Tag pk961b_rat: Bit Array tags are not supported. Tag will be converted as a memory tag.''
I Have changed the DATA TYPE to INTEGER on Factory Talk Tag Dialog box, IS THIS APPROACH CORRECT?
This is what I would try too, but you will have to test it to make sure it is correct.

What do you think of this one? ''Screen 3 - 82PK961A_B: Message display object will be converted to Multistate Indicator object at (340, 292).''
Not sure about this
 

Similar Topics

Hi guys, I have the same program in my CPU and in my SD card but when I boot from the SD card I get error message 2400 which relates to some...
Replies
4
Views
579
Good day I would be so glad if anyone can assist me. I have a message instruction and i am sending data between 2 PLC's. The Message...
Replies
5
Views
2,586
I have uploaded a file from a panelview and i get a message when trying to restore it: "This runtime application file was saved in a protected...
Replies
4
Views
1,291
I have been working on creating a subroutine for my company to send an email from my controller to our email server and had been successful in...
Replies
12
Views
2,253
I have a 1756-L62 that is sending a message to give a 1769-L24ER a permissive bit to run. This system has been working fine for about 2 years...
Replies
4
Views
3,020
Back
Top Bottom