MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About geetee1969

  • Rank
    Hi, I am New!

Profile Information

  • Country United States

Recent Profile Visitors

759 profile views
  1. PVRIO

    Thanks for the quick reply, the HMI  uses a tag database, but there are no corresponding tags in the Controller tags. Example, HMI tag [PVRIO]OCTIME is a signed integer addressed B17 0. Looking through the messages and Controller tags I found that N150[0] seems to be the tag that houses the data that is written to [PVRIO]OCTIME via a Block transfer message. Other than the data being correct, (a value for a timer preset) the other indication to me that I have the corresponding tag is that it’s described as OCTIME. It would seem that I only have to do this another 700 times or so and I will have it converted. I guess I didn’t want to do this another 699 times only to find I could have or should have used another method.  
  2. PVRIO

    Hello,  I am trying to migrate a PanelView plus program that uses RIO communications to run on PanelView plus 7 terminal. Using Factory Talk View Studio ME, I restored the runtime file and changed the terminal type and size as needed. My intentions are to make some sort of table to list all of the PVRIO tags, and find the corresponding tags in  the program running inside of a 1756-L71 V30. I would then use the find and replace Tool until I changed all of the tags in the PanelView program to point directly to the corresponding tags in the control logix program. My plan is then to delete the RIO communication shortcut in the PanelView, and get rid of the lines of logic that handled the block transfer reads and writes. My question is this, is this as easy as the plan that I laid out or am I missing something?  The Control logix program was converted from a PLC 5 program a few years ago, and I suddenly have time on my hands to try to get this obsolete terminal changed out. Any advice would be appreciated. I hope each one of you are well and stay that way, or have a speedy recovery if not.  Thanks,  geetee      
  3. DeviceNet

    Ken thanks for replying. The network is set for 500 kb/s. The sensor is a R series sensor factory set for 500 kb/s. It came set as node 63 from the factory, so I changed the node to 05.  I guess the revision level of the sensor may have been different than the one previously installed. I thought I could take care of that issue by correcting the identity mismatch after uploading but I never got a message this was the case. The original alarm was an E78 node 05. The alarm handling operates like you suggested, after a few minutes a reset command is issued by the controller and then it issues a run command to the scanner. This was another piece of the puzzle or rabbit hole that has me confused. After switching back to the old sensor, all errors went away but the scanner was stuck in idle mode.  Looking through the controller tags, there were no device net errors and there was a 1 in run status tag but the module still said idle. I could not get the module to switch to the run mode until I downloaded a copy of the program back into the controllogix controller. Then the scanner went into run mode and we have been running this way for a few shifts now. This system has been in place for 17 years now and we have had these alarms happen a couple times a year. This is our first attempt at changing one of the devices, and I thought I had my ducks in a row, apparently I did not.   
  4. DeviceNet

    I have enjoyed reading the posts on this site for some time now, and I am hoping that someone on here would be able to help me out with a problem. We have a small DeviceNet network consisting of a 1756-DNB (node00), two Wago scanners (nodes 03, and 04) and two identical MTS position transducers (nodes 02, and 05). The DNB card is in a rack along with a ControlLogix L71 controller. We have been experiencing random device net error alarms lately where a node would stop communicating and we would power down the system and reboot. The errors would then go away. The other day I decided to use the Networx for DeviceNet to find out what was going on when one of these errors popped up. I found that the device on node 05 was not present on the network. Since we had a spare identical sensor I decided I would address the sensor as node 05 and configure it using a spare DNB card and chassis we have. All went well until I installed the spare sensor into the system. At that point we had alarms pertaining to most of the device net devices. Scanning the network with the Networks software showed no device problems, all were present and communicating, but I could not get the alarms to reset. We tried rebooting the network, the sensor, and even the entire system with no luck. It wasn’t until I reinstalled the old sensor that we were able to get the alarms to clear. Since I have rambled on long enough I won’t bore you with the rest of the trip down this rabbit hole I went down, but what did I do wrong when trying to change this sensor? Is there a specific sequence of events that need to take place when replacing one, even if the sensors are identical?  I am stumped, and we still have the potential of one of these sensors failing without having a clear idea about how to go about changing it. Any help would be greatly appreciated.