comms errors with PV+ and L32E - PLCS.net

DairyBoy · November 23rd, 2011, 04:20 PM

Setup: PV+1000 (V5.10), 1769L32E processor (V19.11). The two units communicate, the devlopment version sees all the RS5000 tags as they are created but the PV shows runtime errors like "Item '{[Silo_Routing]B1[21]' is unresolved in the processor on route Compactlogix in slot 0... I can read numberic variables on the screen, all the colour change and visibility attributes work, but any bit addressed tags generate errors like "Write attempt for item '[Silo_Routing]HMI_Switches[5]' failed (configuration error) on compactlogix... etc. The same happens if I run the application on the pc. What have I missed this time, dudes??? Thanks.

bce123 · November 23rd, 2011, 04:23 PM

can you post the files?

DairyBoy · November 23rd, 2011, 05:12 PM

Thanks for the offer but they're still over a meg zipped. So much for zipping.

ianingram · November 23rd, 2011, 06:06 PM

Quote:

Originally Posted by DairyBoy

but any bit addressed tags generate errors like "Write attempt for item '[Silo_Routing]HMI_Switches[5]' failed (configuration error) on compactlogix... etc.

You said bit address...

[Silo_Routing]HMI_Switches[5]

Is that the correct address?
Or is the address something like
[Silo_Routing]HMI_Switches[5.0]

DairyBoy · November 23rd, 2011, 06:10 PM

Ian, "HMI_Switches" is a DINT, so [n] is the bit number within that DINT. I've checked the format against my only other 5000/PV+ project and the format is the same.

Anyway, third late night in a row on this one and eyes/brain are stuffed. Simplest plc prog I've ever written and it's giving me more grief than some of the bigguns. crazy. Time for bed. Delivering it tomorrow...

Ken Roach · November 23rd, 2011, 07:32 PM

Square brackets denote a member of an Array Tag (BOOL, SINT, INT, DINT, REAL, STRING, etc)

A period denotes a bit sub-element of a SINT, INT, or DINT Tag, whether it is an array member or an ordinary atomic datatype.

If the Tag is a DINT, then MyTag.x is the syntax for a bit sub-element in that DINT.
If the Tag is a DINT array, then MyTag[y].x is the syntax for a bit in that array element.
If the Tag is a BOOL array, then MyTag[x] is the syntax for a bit in that array.

ianingram · November 23rd, 2011, 07:37 PM

Quote:

Originally Posted by DairyBoy

Ian, "HMI_Switches" is a DINT, so [n] is the bit number within that DINT. I've checked the format against my only other 5000/PV+ project and the format is the same.

Anyway, third late night in a row on this one and eyes/brain are stuffed. Simplest plc prog I've ever written and it's giving me more grief than some of the bigguns. crazy. Time for bed. Delivering it tomorrow...

I was hoping that someone else would reply by now...

I am looking at projects that I have done, and the addressing format is [shortcut_name]tagname.bit_number

I am guessing that you are missing a . in your address format

DairyBoy · November 24th, 2011, 03:40 AM

Ken, Ian, you're both right. I've looked at the previous PV prog as a reference without sufficient care regarding the data types in the plc prog. I need to change the data type in the hmi. My mistake. Thank you.

November 23rd, 2011, 04:20 PM	#1
DairyBoy Member Join Date: Jun 2007 Location: UK Posts: 270	comms errors with PV+ and L32E Setup: PV+1000 (V5.10), 1769L32E processor (V19.11). The two units communicate, the devlopment version sees all the RS5000 tags as they are created but the PV shows runtime errors like "Item '{[Silo_Routing]B1[21]' is unresolved in the processor on route Compactlogix in slot 0... I can read numberic variables on the screen, all the colour change and visibility attributes work, but any bit addressed tags generate errors like "Write attempt for item '[Silo_Routing]HMI_Switches[5]' failed (configuration error) on compactlogix... etc. The same happens if I run the application on the pc. What have I missed this time, dudes??? Thanks.

November 23rd, 2011, 04:23 PM	#2
bce123 Lifetime Supporting Member Join Date: Feb 2011 Location: texas Posts: 1,099	can you post the files? __________________ "You can teach a dog to sit and lie down but then he justs gets lazy"

November 23rd, 2011, 06:10 PM	#5
DairyBoy Member Join Date: Jun 2007 Location: UK Posts: 270	Ian, "HMI_Switches" is a DINT, so [n] is the bit number within that DINT. I've checked the format against my only other 5000/PV+ project and the format is the same. Anyway, third late night in a row on this one and eyes/brain are stuffed. Simplest plc prog I've ever written and it's giving me more grief than some of the bigguns. crazy. Time for bed. Delivering it tomorrow... Last edited by DairyBoy; November 23rd, 2011 at 06:20 PM.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Topics
Thread	Thread Starter	Forum	Replies	Last Post
PV 600 and L32E Daylight Savings Time Change	agrosse	LIVE PLC Questions And Answers	6	November 9th, 2011 12:26 PM
Cannot ping L32E	mutabi	LIVE PLC Questions And Answers	19	August 2nd, 2011 12:48 PM



This board is for PLC Related Q&A ONLY. Please DON'T use it for advertising, etc.
*Try our online PLC Simulator- FREE. Click here now to try it.* ---------->>>>>Get FREE PLC Programming Tips

November 23rd, 2011, 05:12 PM	#3
DairyBoy Member Join Date: Jun 2007 Location: UK Posts: 270	Thanks for the offer but they're still over a meg zipped. So much for zipping.

November 23rd, 2011, 07:32 PM	#6
Ken Roach Lifetime Supporting Member + Moderator Join Date: Apr 2002 Location: Seattle, WA Posts: 8,716	Square brackets denote a member of an Array Tag (BOOL, SINT, INT, DINT, REAL, STRING, etc) A period denotes a bit sub-element of a SINT, INT, or DINT Tag, whether it is an array member or an ordinary atomic datatype. If the Tag is a DINT, then MyTag.x is the syntax for a bit sub-element in that DINT. If the Tag is a DINT array, then MyTag[y].x is the syntax for a bit in that array element. If the Tag is a BOOL array, then MyTag[x] is the syntax for a bit in that array.

November 24th, 2011, 03:40 AM	#8
DairyBoy Member Join Date: Jun 2007 Location: UK Posts: 270	Ken, Ian, you're both right. I've looked at the previous PV prog as a reference without sufficient care regarding the data types in the plc prog. I need to change the data type in the hmi. My mistake. Thank you.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)