List of available JSON attributes in an RSC File (Compact)

In PiCtory you can virtually assemble your devices as they will later be mounted on the DIN rail.

This combination of the devices is saved as an RSC file and thus represents your project structure.

If you have already created a device configuration with PiCtory, you can save this file. You can then use the saved file to reuse it e.g. for your own application or to extend the file.

AAppMain area with information on how to control the application layout.
A.1App.nameName of the application (from config.json)
A.2App.versionVersion of the applikation (from config.json)
A.3App.saveTS14-digit timestamp of the storage time of the .RSC file (yyyyMMddHHmmss)
A.4App.languageLanguage setting of ‘PiCtory’ which was set when saving the .RSC file
A.5App.layoutSubarea with Layout Information
A.5.1App.layout.northMenu area of the application layout
A.5.1.1App.layout.north.sizeHeight of the menu area
A.5.1.2App.layout.north.initClosedMenu area is displayed closed (true / false)
A.5.1.3App.layout.north.initHiddenMenu area is hidden (true / false)
:All further App.layout.[…] entries have the same structure; this also applies to the sub-layout areas under ‘children’ (e.g. App.layout.south.children.layout1.east)
BSummaryMain area: totals values for facilitated parsing of devices data
B.1Summary.inpTotalTotal size of the input values of all devices
B.2Summary.outTotalTotal size of the output values of all devices
CDevicesMain area: array of 1-n device data; index [i]
C.1Devices.[i].catalogNrReference to PiCtory catalog file (redundant to ‘id’; currently not used)
C.2Devices.[i].GUIDGUID for unique identification of the device
C.3Devices.[i].idComplete device ID incl. ‘device_’ prefix, catalog number and version information, e.g. device_RevPiCore_20160818_1_0_001
C.4Devices.[i].typeDevice positioning type (according to key ‘devicetype’ from RAP file)
C.5Devices.[i].productTypeCode number of the product type in the KUNBUS product range
C.6Devices.[i].positionPosition number – taken from device data table of ‘PiCtory’:
0 … BASIS device
31, 30 etc. descending … left-sided positioned device
32,33 etc. ascending … device positioned on the right hand side
‚virt.‘ … virtual devices
C.7Devices.[i].nameName of the device – from device data table
C.8Devices.[i].bmkDevice identification code of the device – from device data table
C.9Devices.[i].inpVariantInput variant of the device – from device data table
C.10Devices.[i].outVariantOutput variant of the device – from device data table
C.11Devices.[i].commentComment on device – from device data table
C.12Devices.[i].offsetAbsolute offset of the device in the memory image
C.13Devices.[i].inpSubrange of the input data of the device; for each input value there is an array with the following structure:
1“0”: [
1Serial number to facilitate array processing
2Name / designation of the value; possibly qualified with current no. if values with the same name already exist
3Default value
4Bit length of the value
5Offset relative to device offset
6Is the value exported?
7Subset of the outpentcontains for BOOL values the bit position (starting sort order to restore the original display order in the value editor table with 0ut data of the device
9Subarea of the output contains for BOOL values the bit position (starting with 0)ut data of the device
C.14Devices.[i].outSubrange of the output data of the device
Description see C.13
C.15Devices.[i].memSubarea of the memory data of the device
Description see C.13
C.16Devices.[i].extendSubarea of the extended data of the device; this area is only filled if the device allows extended data acquisition via the menu item ‘extended data’ in the device menu. The data stored here and its structure are device-specific
C.17.1Devices.[i].extend.deviceMiscExtended device-specific data that are only available once per device (1:1)
C.17.2Devices.[i].extend.dataDefines whether the device should be activated or deactivated in the current configuration. Extended device-specific data series (1:n), i.e. data that are available ‘n’ times per device and are usually recorded in tabular form
Devices.[i].activetrue or false; defines if the device should be activated or deactivated in the current configuration