Author Topic: clx driver wont write to tags on a particular pc  (Read 860 times)

paulfletch

  • Newbie
  • *
  • Posts: 5
    • View Profile
clx driver wont write to tags on a particular pc
« on: September 09, 2019, 06:02:50 PM »
Hi Archie, we are using the clx driver to read and write tags. On a particular pc on windows 7 we can read but not write to tags. No exceptions are flagged. The same program is running on other pc's with windows 7 without issues.
Could there be a pc setting that would stop this write function?   

Archie

  • Administrator
  • Hero Member
  • *****
  • Posts: 5317
    • View Profile
    • AdvancedHMI
Re: clx driver wont write to tags on a particular pc
« Reply #1 on: September 10, 2019, 12:23:35 AM »
There is nothing that I am aware of in the PC that would cause this. If you follow these steps, I will be able to tell you the problem

1) Install Wireshark on the problem PC
2) In the PLC, create a controller scope tag "DINTTag" of type DINT
3) Start with a new AdvancedHMI solution
4) Add the driver to the MainForm and set the IPAddress
5) Add a BasicLabel to the MainForm
6) Set PLCAddressValue and PLCAddressKeypad to DINTTag
7) Make sure RSLinx is completely shut down
8 Start a Wireshark capture session
9) Run the AdvancedHMI application
10) Click on the BasicLabel and enter the value 99
11) Close the AdvancedHMI application
12) Stop the Wireshark session
13) Save the Wireshark capture and post it here

paulfletch

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: clx driver wont write to tags on a particular pc
« Reply #2 on: September 10, 2019, 01:08:29 AM »
Ok will do. Thanks

paulfletch

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: clx driver wont write to tags on a particular pc
« Reply #3 on: September 10, 2019, 08:09:45 PM »
Hi Archie, turns out that the plc tag being a timer accumulator was being written as a zero by the timer reset function at the same time we were trying to write to it. It just happened to be at the same time we were testing this particular pc.
So there was absolutely nothing wrong with the pc at all. Sorry for wasting your time.