Sergei Troizky

Double-click the "IO table and unit setup" in the project tree and transfer the IO table from the PLC. There is such icon there.

See this thread. Probably, it will help you at least with the USB communication. http://forums.mrplc.com/index.php?/topic/34230-cp1h-xa-failed-to-connect-to-the-plc-with-usb/#comment-160191

The error HE is tag datalink communication timeout, and IP 07 (not 1P)  is the last octet of the erroneous node IP address. Did you download only the program, or data memory as well? The latter might change the communication settings, as well as "Set defaults" in the Ethernet port configuration.

The complete instruction would be: <> K4M801 H0

Because the PRV2 works only with HSC0. The PRV may be used to measure the speed programmatically, with certain limitations in resolution and update period.

All posters: Mentioning the OS would make big sense in such cases!

Tried it. No result.

Same problem, but no such menu option in the v9.45. No matter the Information Window being On or Off.

After changing the computer name, I cannot configure the RSLinx Enterprise communication in Factory Talk View ME Studio projects. It says no such computer in the Factory Talk directory. How can I fix this?

In other words, a Number type data is a named constant.

From my experience, the mentioned error will appear if there is another session of the CX-Programmer running, with transfer-related dialog box active. Even if the transfer (upload or download) is already finished, and the dialog box is only waiting for OK. Or, when the CX server stops working. In such case, the CX-Programmer restart helps.

I want to install and run the Rockwell software on new Win10 PC in the Oracle Virtualbox VM. However, my Factory Talk activations are tied to the hard disk serial number. Tried to change the VM hard disk serial, with couple utilities, but no success. Any suggestions?

CompactLogix with integrated motion. Hyperphase absolute encoders. There are the Motor Offset and Controller Offset options in the Axis properties/Motor feedback. The manual says "in the most cases it would be the controller offset", however does not explain when and why. Could anybody explain the difference and the preferences.

So many unnecessary technical details, and still absolutely unclear when and why use the controller offset or the motor offset.

500ms?! What may be such an application? I've tried this on a live CP1H, and it indeed falls into communication error. But, after changing the USB Respone Timeout from the default 2s to 20s, I was able to communicate and revert everything back. However, the responses were SLOW. Expect almost a minute delay between every mouse click and its result.

What did you change the constant cycle time to? And can you afford wiping off the entire controller content?

I have seen couple CP units with the USB port damaged by 24V due to wrong wiring. The incident may be instantaneous; the wrong wiring may not be there anymore. I used a communication adapter board in such case as an alternative port, e.g. CP1W-ETN61. 

This confirms the PC port is OK, but not the PLC's.

How do you know that? Meaning the PLC port.

Why bother switching? I would calculate and display both.

That's right. The SC-09 retailed for $200 at the time.

What is this (C) on the attached picture, in the Alias line?

I've used couple times the CP1W-MODTCP adapter board with CP1H. It can be a master or a slave, and supports read and write commands, but not the combined read/write command.

Then, the most straightforward way is to utilize the major property of the Gray code: any transition may be in a single bit only. Compare every new value with the previous one for changed bits. If more than one bit changed simultaneously, the  sequence is abnormal, and may indicate wiring problem. However, the method assumes reading of every change. If the lower bits are too fast, use interrupt, or simply exclude them, and verify at least the  rest. The lower bits can be verified by some other method.

Probably, it's a matter of opening existing project files, not the supported PLC models.