FAQ

1.Built-in Drivers (CIMWAY)
Data collection for mainstream automation is managed directly by CIMWAY, PcVue native communication kernel. In the documentation, these are referred to as Built-in drivers.

• What they cover: Standard Ethernet or Serial manufacturer protocols used by major PLC brands (e.g., Schneider Open Modbus TCP/IP, Siemens Industrial Ethernet, Rockwell DF1, Omron FINS).
• The “One Driver” Rule: Every standard PcVue license automatically includes one Built-in CIMWAY driver at no additional cost.
• Mixing Multiple Protocols (CW_DRIV): If your system architecture requires communicating with several different standard protocols simultaneously (for example, connecting to a Modbus meter and a Siemens PLC at the same time), you must add the CW_DRIV option to your software license to unlock additional concurrent CIMWAY drivers.

2. Built-in Optional Drivers
For specialized industrial verticals, PcVue features high-end protocols referred to in the documentation as Built-in – Optional.

• What they cover: Advanced vertical-specific industry standards such as BACnet (for Building Management Systems), and IEC protocols (such as IEC 61850, IEC 60870-5-104) or DNP3 (for Power and Smart Grid automation).
• Licensing: Because these handle complex information modeling and advanced services (like millisecond timestamping or file transfers), they are not included in the standard core driver selection. To use them, an additional communication option (CW_BACNET, CW_104..) must be added to your software license to unlock that specific protocol link.

You can view the full, categorized list showing exactly which protocols are classified as Built-in vs. Built-in – Optional directly on the official PcVue Communication Drivers Resource.

Unlike other object protocols, there is no standardization of the data. That is to say that each sensor manufacturer encodes the data as he wishes. We talk about ‘payload’.
To do so, our LoRaWAN, MQTT or UDC drivers are very open and allow you to quickly retrieve any type of elements. For example, we can retrieve an integer, a text or an element from JSON. The JSON format is very widespread in the IoT domain. With PcVue you can model your object and with the Application Architect you can quickly and graphically instantiate your IoT. Do not hesitate to contact us, we can advise you in the modeling, the choice of sensors and the IoT solution that will meet your needs.

PcVue allows you to report information from a private IoT network and an operated IoT network. You have a range of drivers such as LoRaWAN driver, MQTT or Universal Data Connector

Sure you can. The PcVue station will serve the mobility part and be connected as a client to the existing SCADA. You may use standard connection like OPC for instance to collect the data from your SCADA. However you may need to recreate mimics to be displayed in SnapVue.

Yes, in the project folder of the PC with the instant messaging backend role (where the MSG server is running). Some messages are also cached on the client devices (in the TMP directory of PcVue, and in the local database for mobile app)

It depends a lot on the manufacturer.
Some of them may work during 3+ years , some are wired and do not require a battery at all. Accuracy is about 2 or 3 meters but it can go up to 5 meters.

There is no specific vendor for BLE Beacon. As long as the beacon is compatible with iBeacon standard.

Step1 : Get the License Utility software. You can find it on PcVue\Bin directory, RmLicMgr.exe file, or download it from the Technical support website.
Step2 : Generate the Host machine signature .DAT (ie the machine  or virtual machine you will install PcVue). To generate the signature file on the target machine you must install the PcVue License Utility (standard PcVue installation or stand-alone installation). Then, you must create a shortcut to the License Utility (licutil.exe) and add the argument -software on the command line. This argument is used to bring up a menu dedicated to software license management in the License Utility.
You have to select the entry “Computer signature …” and fill the information fields displayed in the generation form of the signature. When you validate the dialog box, Signature<machine name>.dat is created containing the signature of the machine as well as the filled information.
Step3 : Send the signature file Signature<machine name>.dat generated to your usual sales contact for activation request
Step4 : Our logistic department will send you a License protection file (lic.dat or lic<serialnumber>.dat)
Step5 : Copy it on the Host machine into the ETC directory of PcVue
Step6 : Run PcVue

PcVue Solutions License Procedure (pdf)

You can download release notes information for each PcVue version in our KB portal/ version information category.
If you can’t access to the KB, please contact your sale representative. Please note that you need to register first to get a full access on every articles.

The latest version is PcVue 17.
See what’s new in PcVue 17.