brettdawnj
Member
I am starting a new thread on this subject as the past one was getting long and I have learned some things from all of your help and assistance. Here is what I have now...
Problem: Can not get the historical trending feature working on a Panelview Plus 1250 ME v4 application.
Know conditions so far:
Startup set up correctly
Data Model set up correctly
Trend properties set up correctly
(these all verified by another member sending me a working application and me comparing to my settings... all adjusted and set to match his in concept and style... and I still have the problem)
Issues known so far (via the diagnostics of the PV):
All startup conditions without error until warnings of the following;
1) Model "RunRatio": Started ... no problem with this one (but wanted to show you it starts)
2) (CLXDP) CIP connection (0) open rejected (Error 2040101) on route to "HP_LAPTOP".Ethernet.Ethernet Bridge (1760-L35E).1789-Virtual Chassis."application name" with 0 packets on connection
3) Datalogger: Invalid tag type. Tag '[RT_plc]Run_Ratio_1st_Trend'.
4) Datalogger: Invalid tag type. Tag '[RT_plc]Run_Ratio_2nd_Trend'
5) (CLXDP) CIP connection (0) open rejected (Error 2040101) on route to "HP_LAPTOP".Ethernet.Ethernet Bridge (1760-L35E).1789-Virtual Chassis."application name" with 0 packets on connection
and then there is no more failures but the next "information" messsages are:
6) Ethernet Driver Control Thread for 10.96.24.244 has (re)-established communications.
7) (CLXDP) CIP connection (1) timed out on route to "HP_LAPTOP".Ethernet.Ethernet Bridge (1760-L35E).1789-Virtual Chassis.* ... can't see the rest of the message
8) (CLXDP) Reoptimizing "HP_LAPTOP".Ethernet.Ethernet Bridge (1769-L35E).1789-A17 Virtual Chassis."application name".
9) (CLXDP) CLX Processor download or change noticed while offline, handled on route "HP_LAPTOP".Ethernet.Ethernet Bridge (17* ... again, can see the rest of the message
What happens on the actual application is the trending works off this live data tag, but no history is collected. So I am now thinking that I need to somehow resolve the above issues of 2 thru 5 above and then maybe it will somehow work. Physically, when I download a new application to the PV, it takes a long time to actually establish communications with the PLC... and this makes me think that this delay might be causing the Datalogger not to work properly.
Is this possible and do you think I am heading in the correct direction? Any other suggestions?
Thanks,
Brett
Problem: Can not get the historical trending feature working on a Panelview Plus 1250 ME v4 application.
Know conditions so far:
Startup set up correctly
Data Model set up correctly
Trend properties set up correctly
(these all verified by another member sending me a working application and me comparing to my settings... all adjusted and set to match his in concept and style... and I still have the problem)
Issues known so far (via the diagnostics of the PV):
All startup conditions without error until warnings of the following;
1) Model "RunRatio": Started ... no problem with this one (but wanted to show you it starts)
2) (CLXDP) CIP connection (0) open rejected (Error 2040101) on route to "HP_LAPTOP".Ethernet.Ethernet Bridge (1760-L35E).1789-Virtual Chassis."application name" with 0 packets on connection
3) Datalogger: Invalid tag type. Tag '[RT_plc]Run_Ratio_1st_Trend'.
4) Datalogger: Invalid tag type. Tag '[RT_plc]Run_Ratio_2nd_Trend'
5) (CLXDP) CIP connection (0) open rejected (Error 2040101) on route to "HP_LAPTOP".Ethernet.Ethernet Bridge (1760-L35E).1789-Virtual Chassis."application name" with 0 packets on connection
and then there is no more failures but the next "information" messsages are:
6) Ethernet Driver Control Thread for 10.96.24.244 has (re)-established communications.
7) (CLXDP) CIP connection (1) timed out on route to "HP_LAPTOP".Ethernet.Ethernet Bridge (1760-L35E).1789-Virtual Chassis.* ... can't see the rest of the message
8) (CLXDP) Reoptimizing "HP_LAPTOP".Ethernet.Ethernet Bridge (1769-L35E).1789-A17 Virtual Chassis."application name".
9) (CLXDP) CLX Processor download or change noticed while offline, handled on route "HP_LAPTOP".Ethernet.Ethernet Bridge (17* ... again, can see the rest of the message
What happens on the actual application is the trending works off this live data tag, but no history is collected. So I am now thinking that I need to somehow resolve the above issues of 2 thru 5 above and then maybe it will somehow work. Physically, when I download a new application to the PV, it takes a long time to actually establish communications with the PLC... and this makes me think that this delay might be causing the Datalogger not to work properly.
Is this possible and do you think I am heading in the correct direction? Any other suggestions?
Thanks,
Brett