ElectronGuru

  Timer instructions time things; Counter instructions count things. Based on the wording of your question, I'm not sure if you're timing or counting. Either way... A Timer On Delay (TON) instruction will time when the input logic to it is true. TON is not retentive, so it will reset itself when it's input logic is false. A Count Up (CTU) instruction will count up one whole number (0 to 1, 1 to 2, 2 to 3, etc) for each false to true transition of the logic to it. It is a retentive instruction, which means it will hold the accumulated value until it's associated Reset (RES) instruction is set. PS. If this is a homework question you might consider watching some YouTube videos on @TimWilborne's channel.

@Shankar Rao I hate bringing that up but every once in a while you across someone who reverses those definitions and when that happens, the whole conversation can go sideways, lol. Like telling the student pilot to raise the gear before landing the plane. Hopefully you'll be able to get you project transferred. Let us know!

The manual says that if you're using CCW for a PanelView C you can only transfer the program using a USB flash or SD card. https://literature.rockwellautomation.com/idc/groups/literature/documents/um/2711c-um001_-en-p.pdf Also, you wrote that you created a new project but that you are trying to upload. In Rockwell / Allen Bradley, "Upload" is moving the project from the device (controller, PanelView, PowerFlex drive, etc) to the laptop. "Download" is moving the project from the laptop to the device. Hope I'm not coming off as condescending but want to make sure we're talking about the same thing, using the same terms. 

I believe the PanelView 800 (programmed from CCW) is supposed to be a direct replacement for the PanelView Component generation. Just to be sure, I looked up the C400 PanelView manual: https://literature.rockwellautomation.com/idc/groups/literature/documents/um/2711c-um001_-en-p.pdf Appendix D says that you should be able to use CCW with this terminal, assuming that (as @Joe E.said) whoever developed the code didn't lock you out of it. However, the manual also says that if you're using CCW for a PanelView C you can only transfer the program using a USB flash or SD card. PanelView C is an older system and the manual is dated 2014, so if you find that CCW V21 (newest version) has a trick not available when this manual was published, I'd like to hear about it, please.

While I have very limited experience with them myself, I've noticed that a whole new layer of potential issues arise with the use of VMs. I try to avoid them when using Rockwell or other controls software though sometimes there's no choice, like when using legacy programming tools that aren't compliant with current versions of Windows. That shouldn't be the issue here but if you can run this outside of the VM, you might have better luck. Also, it might do to have someone who has more direct experience with VMs to jump and let us know if they've seen similar issues and possibly how to fix them. You probably already know that the Go To Display buttons don't work when Test Display is used. If properly configured and you have selected a display to go to in a given button's properties (see attached .pdf), the buttons should work and navigate you to the desired display in Test Application. On your paths, make sure that you click the Verify button after copying the Design path over to the Runtime. Then click OK to close it out. I've seen the path settings not stick when Verify wasn't clicked, or when someone X-ed out of the tab instead of clicking OK. GoTo.pdf

You're using and getting disconnected from a Logix Emulator? And you get kicked when running the FactoryTalk project? What versions of Studio 5000 and FactoryTalk Studio are you using, and does this also happen when testing individual displays? When you get booted offline from the controller, are you able to go back online while running/testing the FactoryTalk project? As for the buttons in FactoryTalk, are you using ME or SE? I'm assuming ME since you mentioned Test Application instead of launching a client. If ME, when you set up your communications, did you remember to set up the separate Runtime path to the controller? If you set up a Design path, your buttons and other interactive objects will work when Test Display is used, but they will not work when you Test Application without a valid Runtime path.   

The 5069s are persnickety and don't work like any other IO cards in the Logix family. In addition to what @Joe E.mentioned about nuisance output diagnostics (fixed by unchecking "Enable No Load Diagnostics" in the card properties), in my experience you also have to manually turn off any channels you're not using on analog input cards or you're likely to get fault lights from lack of input data. I've found the 5069 IO manual to be decidedly lacking on these kinds of details and have to had to learn to properly configure these cards by digging around in the cards' properties & tags until I wrestle and cuss it into working the way I want. If you're not enjoying the digital 5069 configurations, just wait til you get to an analog.

@VFD Guy it was intended as a two-part answer; Part one-  why you probably can't tune the drive; "Most likely the drive is owned by a Logix controller and you'll need to go online with the drive via Studio5000". Part two- since CCW threw this code "  "Failed to write a new value message - This parameter is only editable on the Identity Page.", here's where you can find the definition page; " From the controller's IO tree, open the properties dialog box of the drive, click on the Device Definition button and this will open the Identity Page". I probably should have split it up when I first posted to avoid any possible confusion.

You have to set up users and user groups, then assign permissions to the groups. This can be done under System > User Groups in ME and SE, or the FactoryTalk Admin Console in SE.  You can also specify display securities in Runtime Security of the individual ME and SE projects.  Once this is done, anyone who logs in will inherit the permissions of the group(s) of which they are a member, and will only be allowed to make changes and access displays allowed for that group. 

Most likely the drive is owned by a Logix controller and you'll need to go online with the drive via Studio5000. From the controller's IO tree, open the properties dialog box of the drive, click on the Device Definition button and this will open the Identity Page.     Indentity Page.pdf

@Cannonier10 I must've been composing my response when you posted yours and I didn't catch that before submitting. Sorry for duplicating your efforts.

In the properties dialog box of every task there is a Configuration tab. In a periodic task, this is where you set up the Period (how often the task executes), the task priority (1 through 15, 1 is the highest priority) and watch dog timer (max time the task is allowed to execute without causing a controller fault). If a Task A has a priority of 5 is to execute every 20mSecs and Task B has priority of 3 and is to execute every 22mSecs, at 20mSec Task A will interrupt the continuous task and begin to execute. At 22mSec Task B will interrupt Task A, execute, then hand control back to Task A. Task A will pick up where it left off, finish executing, then hand control back to the continuous task. Rinse and repeat. If you give two tasks the same priority level and they attempt to execute at the same time, they will hand control back and forth to each other at 1mSec intervals. This is called "time slicing" and will really slow down the execution of your code. The watch dog timer default setting on all tasks is 500mSec, but can be set to between 0.1 and 2B mSec. If the total accumulated execution time of any task exceeds its watch dog timer setting the controller will go into a major recoverable fault, and you process will come to a halt. 

I've seen this only twice in my career. Check the integrity of the key switch. It'll be showing that it's in run or remote but the inside guts of the switch are worn out and you get no operation when you think you should be in run.

I'm only up to version 12 of CCW, which does not (as far as I know) have a migration tool. Whenever I upgrade a drive I download and install the AOP, set up the new drive using the startup wizard in CCW, then get online with the processor and auto-discover the new drive that's sitting there ready for use. I'd love to learn that CCW has a migration tool that does this for you. 'Guess I'll have to start reading the release notes on V13, 20, and 21. (Yes, they skipped 14 through 19. Go figure).

Anyone have experience with the 1756-5580 controllers? I'm specifically curious about the role-based access control that Rockwell is boasting about. The following bullet point is from the associated link: Includes controller-based change detection and logging, digitally-signed controller firmware, and role-based access control for extra security https://www.rockwellautomation.com/en-us/products/hardware/allen-bradley/programmable-controllers/large-controllers/controllogix/1756controllogix5580.html The L7 controllers also have controller-based change detection and logging. It's just been expanded in the L8 from logging 100 to 500 events in the controller's memory. But they're making it sound like it's a brand new thing. The above bullet point also makes it sound as though the role-based access control feature is embedded in the controller, and therefore would not be dependent upon the FactroyTalk Admin Directory. Is this true and if so, how do you use this feature? Would you apply the FactoryTalk security when creating the project and it just remembers the permissions? Or is this advertising blurb a bit misleading, like making the change detection and logging sound like a whole new thing? Anyone?

@BobLfoot that's spot-on; you must download the individual version(s). Currently you can get RSLogix Emulate 5000 in versions 20.4, 21.3, and 24.1. Studio 5000 Logix Emulate is available in versions 24.1, 28, 30, 31, 32, 33, 34, and 35.  You should be able to look those up, compare, and download from here:  https://compatibility.rockwellautomation.com/Pages/MultiProductSelector.aspx?crumb=111

@mhi are you needing to go online with a PLC-5, or just open the file and read the code? If you truly need to get online with a working PLC-5 processor, you'll want to check through RSLinx to see what the controller is flashed to, as only versions 8, 9, and 10 (out of 10) are still available. In the Search box, type "RSLogix 5" and get the exact version to match your processor(s) here: https://compatibility.rockwellautomation.com/Pages/MultiProductSelector.aspx?crumb=111 If you only need to open the file to read the code, post the .rsp file here and someone who has RS5 will be able to open it, print as a .pdf and re-post for you. 

Most of the components of a .med are individually exportable and saved with their own file extensions. A couple of examples would be; displays are .gfx, global object displays are .ggfx, recipes are .rcp, etc. I think maybe one of the SQL's jobs is just keeping the whole thing grouped together in one database, hence the Tech Note stating you'd have to import the components and create a whole new application. When editing HMI code in a .med the save button is always greyed out until you make a change on whatever component (such as a display) you have open and has focus. As you know, an L5K is an exported project and we accomplish that export by doing a "Save As", which doesn't exist in FTME or FTSE. We can only save individual components as we edit them, and import/export them using the import/export tool.  Just for grins, I just tried to open a .med in Notepad and it looked like a lot of gibberish, with more than half the character being symbols I've never seen anywhere.  All that to say, unless someone pulls a rabbit out of a hat, I don't know any way to make a deliberate and meaningful change to a .med with a text editor. But I sure would be willing to learn about it if it exists.

We've known forever that once a .med is opened in a newer version of Studio than the one it was created in, it's now locked to that version or higher. But yes, in versions 9 through 12 we were able to restore a .mer or .apa to a .med and edit it, regardless of which version of FTView Studio created the original file. To make sure I'm not remembering this wrong, this morning I created a .mer on a laptop with FTView Studio V12 and downloaded it to a PanelView Plus 7 Pro with FW 8.2. I then uploaded that .mer to a different laptop with FTView Studio V10 and successfully restored it to a .med. I only got the usual warning that I'm converting an V8.2 .mer to a V10 .med, and that I won't be able to go backwards with that specific .med.  I haven't downloaded FTView Studio V13 yet but I'm willing to take you at your word, @BobLfoot, that once V13 gets hold of a project file, that file is locked to V13. I'm wondering what surprises await us in V14, scheduled for release sometime early next year.  

@BobLfoot got it, thanks. @pturmel my experience is that you can't have more than one version of FactoryTalk installed at a time. I screwed myself a couple of years a while back by updating to V12 when the rest of the outfit was using V10. That created some work-related issues that are neither here nor there for this thread but suffice to say, there is no "go back" button. I had to completely un-install FTView Studio and do a clean install to get back to V10. If you or anyone knows a way to have more than one version of FTME or SE on a single machine (without using a VM) I'd love to know about it. 

Maybe I'm not reading this right but I'm confused. The project was built in V12, modified by an integrator in V12, and then you wanted to add another display in V12. When did V13 come into play?

Something else just occurred to me; In your laptop's search box type the words "FactoryTalk  Directory Configuration Wizard" and open it. You might try checking both the local and network boxes and going through the setup process again (it's short and painless) before running the resdir utility.  Hope this helps.

Unfortunately, Rockwell removed the Read IO feature when they went from 500 to 5000. There are several module status values that can be obtained with a GSV instruction, but the retrieving model/catalog number is not on the list.  The best way to see what's in any given slot is RSLinx when offline. When online, of course, you just look a the properties dialog box. 

Though this article doesn't reference your specific issue, I've found that the resdir tool linked at the end solves a lot of FT directory issues.  https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/577717

@Ron_Smith I'm currently having an issue where from within the Studio 5000 Task Monitor the RSLinx Ehternet driver sees the nodes but won't let me connect to them. The Knowledgebase solution was to upgrade to 4.3, so I'll be trying that in the coming week. RSLinx seems to have some quirks here lately.