OkiePC
Lifetime Supporting Member
Yes I have seen .RVS mentioned when searching online but did not find a lot of detail.
It will be a flash drive or usb removable drive. The IT guy has several sizes of usb external drives and flash drives and one 480GB flash drive to transport it.
Can you expand more on CTRL+P?
If the PC has the right license and isn't locked down, pressing CTRL + P will bring up a box which lets you edit the application.
In the programs most of the HMI pushbuttons are just XIC in the logic so whats the best way to handle them like a one shot after them perhaps?
When you say a "set" type button would that be a multi state button in AB HMI language? or the maintained pushbutton option?
Neither. There is a "set" command or something like that which is a command to write a value to a tag. The buttons write a "1" to a tag (or what ever value you choose).
The PLC deals with writing a "0" back to the tag after the action is complete.
A multistate button will toggle between values and a maintained button will toggle between 0 and 1, so you can end up with a button that you have to press more than once if RSView "thinks" it needs to write a 0 next and the PLC already did that.
I have two methods for dealing with stuck buttons. If there are a boatload of them, I will just OTU the address after triggering required PLC logic. If there are few enough to tie each one to a timer, I will examine the button and operate a TON timer. I use the TT bit (Timer Timing) of the timer in the logic in place of the button, and use the DN bit of the timer to OTU (or CLR) the address. That let's the programmer see things happening by allowing the state of the button to remain active for a couple of seconds. The TT bit will only be active for the duration of the timer preset.
Take my comments with a grain of salt. I have worked on one RSView32 system about a year ago, but mainly that was just to replace PLC-5 tags with Logix tags. Prior to that was around 2006, so my description may not match exact terminology.