enfermot

MrPLC Member
  • Content count

    4
  • Joined

  • Last visited

Everything posted by enfermot

  1. Okay I found the solution. I was passing parameters which included the whole path to the tag, such as "#1=[PLC]Zones[3].Side[0]" in the parameter file, and {#1.PID.SP} in the connections tab of the trend. I was able to make historical values show on the trend by changing the parameter file so that #1=3, #2=0 and with {[PLC]Zones[#1].Side[#2].PID.SP} in the connections tab of the trend.
  2. I believe I have found a bug in FactoryTalk View ME version 8.10. I have a trend object that uses parameter file placeholders on the connections tab. These are direct-addressed to the shortcut ie {[PLC]...}. The historical data from the datalog does not show. (The pens write lines, but when I navigate away from the screen and come back, the lines are gone and begin drawing again from the right side.) The current data does show. This tells me that the placeholders are correct syntax. When the screen loads, the placeholders are being replaced by a string which yields a correct tag path, or else the pens would not be writing correct data. When I replace the placeholders manually and directly address the tag, the historical data does show correctly. This tells me that the datalog is set up correctly and is logging data. I have verified that a previous project of mine, using I believe version 6.0, successfully used this method of using one screen and one trend to plot various tags using parameter placeholders, and the historical data did show correctly.
  3. I have a FactoryTalk 8 application that exhibits some weird symptoms when I run it. I have buttons whose "visible" state and "enabled" state are based on HMI tags. The states of these buttons don't update. I have screens that fail to close when the "abort" command is issued. I have vba that connects to a tag group, which fails to retrieve the value and produces an error. Some tag values from the PLC (always direct-addressed, I think) show up correctly, even when other symptoms above are happening. These issues randomly go away sometimes after a restart and the entire application runs fine. Does anybody have a clue what could be doing this? (Using Windows 7 Professional 6.1.7601 Service Pack 1 Build 7601, SE version 8.10.00 (CPR 9 SR 7.4), Internet Explorer 11.0.9600.17633)
  4. Putting 0 in Pre for TON and CTU in RSLogix500

    Either I'm misunderstanding you, or that is incorrect, as well. You can do the same test as above, but put a condition in front of the TON that is always false, and examine the .DN bit (and not the inverse this time) on the next rung in front of the same ADD. (MOV or type a value into the .ACC which is greater than the .PRE) The .ACC clears to zero on every scan, and the number value never increments.