The application PiCtory manages the configuration file of a Revolution Pi system (/etc/revpi/config.rsc), i.e. for a RevPi base module with expansion modules. The system configuration can be managed via a browser according to its physical arrangement on the DIN rail.
The configuration file is used to define which expansion modules are located at which position in relation to the RevPi base module and how all the inputs and outputs used are named and configured. The configuration file can also make this system setting available for other programs.
In addition to physical expansion modules, virtual devices can be integrated to support common network protocols or act as pure I/O interfaces.
Starting PiCtory #
PiCtory is started via the pre-installed Cockpit application.
▷ Start Cockpit.
▷ Select menu RevPi configuration.
▷ In the section RevPi Apps click on Open for PiCtory.
❯❯ PiCtory opens in a new browser tab.
Until RevPi Bullseye (04/2024), PiCtory is started via the RevPi Status application, also known as Webstatus. See: Query Device Information.
Arrange Devices (Device Catalog) #
In the Device Catalog, all available RevPi devices and the virtual devices are listed.
On the Configuration Board, the individual RevPi devices of the Revolution Pi system can be arranged as they are physically arranged on the DIN rail, see Rules for the Arrangement of Devices.
▷ Select the RevPi base module from the Device Catalog and drag and drop it onto the empty slot with position number 0.
❯ PiCtory loads the selected base module onto the configuration board and creates new empty slots.
▷ Drag the other devices to the left or right onto the configuration board.
▷ The slots can be moved by clicking on the position number.
▷ Use Right-click > Delete to remove a device.
Basic Configuration of the Devices (Device Data) #
In the Device Data area, the basic settings for the device currently selected on the Configuration Board can be configured.
| Field | Description |
|---|---|
Device Name |
Change the device name if many devices are used and the system data is later processed in another program. |
BMK |
If necessary, specify the equipment identification number (German: Betriebsmittelkennzeichen). |
Inputs/Outputs |
Define data schema for the inputs and outputs. Choose the higher value for the boolean variable or the lower value for the 16-bit variable. |
Comment |
If necessary, use the comment column for additional information. |
If no values are entered, PiCtory uses the values stored in the RAP file.
Configuring Inputs and Outputs (Value Editor) #
In the Value Editor, the inputs and outputs of the device currently selected on the Configuration Board are configured.
| Type | Description |
|---|---|
Type INP |
Values for the inputs |
Type OUT |
Values for the outputs |
Type MEM |
Values for the memory variables, e.g. operating modes of the inputs and outputs |
Name |
Name stored in the process image |
Value |
Value or mode |
Unit |
Unit of the value |
Comment |
Internal comment field |
Export |
Activate values for export via a communication interface (e.g., with MQTT) |
The configurable values differ depending on the RevPi device:
Configuring RevPi Base Modules #
Configuring RevPi Virtual Devices #
Saving the Configuration #
▷ Save the configuration as the start configuration with File > Save as Start-Config. The start configuration is called up directly after each boot process.
▷ Alternatively, use File > Save As to save the configuration as an additional configuration file on the RevPi base module.
▷ Restart the piControl driver with Tools > Reset Driver.
❯❯ The Revolution Pi system is fully configured.
The configuration settings of the Revolution Pi system can be checked with piTest.
Opening Saved Configuration #
▷ Select a configuration file with File > Open.
▷ Alternatively, use File > Load Start-Config. to open the configuration file stored as the start configuration.
Resetting Configuration #
▷ Reset the configuration with File > Clear.
Exporting Configuration #
The configuration file can be exported from PiCtory, e.g. to use it for other programs, for data backup or for simulation purposes.
▷ Export configuration with File > Export.
▷ Define file name and file format. Possible formats are:
-
logiCAD3 ST GLOBALS
-
Offset list .txt
-
IBHSoftec symbol list
-
CODESYS offset list
-
LogicLab
▷ Export file with Download.
▷ Alternatively, display file with Show Only.
Reset Servicestats #
Restarts all services such as RevPiPyLoad.
Reset Layout #
Resets the layout of the PiCtory user interface to the factory settings.
Reset Driver #
Restarts the RevPi driver piControl. The configuration saved in PiCtory is thus available for communication with the RevPi device.
Set Language #
Set the language of the user interface in PiCtory.
User Settings #
Session Timeout #
After the specified number of minutes of inactivity, the user will be automatically logged out. To prevent data loss when session ends, also activate Auto Save when Session Timeout is on. Changes take effect only after restarting PiCtory.
Auto Save #
After the specified number of minutes the current project file is automatically saved. Auto Save should always be shorter than the Session Timeout.
Auto Export #
Set which automatic exports will be performed each time the user saves the project data.
-
PiCtory project file: Revolution Pi module configuration in PiCtory format (config.rsc).
-
ST GLOBALS for logiCAD3: IEC 61131-3 Structured Text GLOBALS section.
-
Offset list: Text list with the names and byte/bit offsets of the values with export checkmark in the Value Editor.
-
Symbol list for IBHSoftec: IBHSoftec Text list with the names and byte/bit offsets of the values with export checkmark.
-
Offset list for CODESYS: Text list with the names and byte/bit offsets of the values with export checkmark.
Cache #
Switch browser caching on or off.
-
Leave the cache mode to On to get the best perfomance of PiCtory for ordinary use.
-
Switch the cache mode to Off if you frequently edit .RAP files in the background while PiCtory is running. Caching set to On will cause PiCtory to load .RAP files from cache instead of loading your latest edited version. This may cause unwanted and unexpected effects while testing .RAP modifications.