List of Available JSON Attributes in a RSC File.

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

This combination of 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, e.g. to reuse it for your own application, or to extend the file.

ID

Entry

Description

A

App

Main area providing information on how to control the application layout

A.1

App.name

Name of the application (from config.json)

A.2

App.version

Version of the application (from config.json)

A.3

App.saveTS

14-digit timestamp of the storage time of the .RSC file (yyyyMMddHHmmss)

A.4

App.language

Language setting of PiCtory that was set when saving the .RSC file

A.5

App.layout

Subarea providing layout information

A.5.1

App.layout.north

Menu area of the application layout

A.5.1.1

App.layout.north.size

Height of the menu area

A.5.1.2

App.layout.north.initClosed

Menu area is displayed as closed (true / false)

A.5.1.3

App.layout.north.initHidden

Menu area is hidden (true / false)

:

All further App.layout.[…] entries have the same structure; this also applies to the sub-layout areas available under “children” (e.g. App.layout.south.children.layout1.east).

B

Summary

Main area: totals values for facilitated parsing of devices data

B.1

Summary.inpTotal

Total size of the input values of all devices

B.2

Summary.outTotal

Total size of the output values of all devices

C

Devices

Main area: array of 1-n device data; index [i]

C.1

Devices.[i].catalogNr

Reference to PiCtory catalog file (redundant to “id”; currently not used)

C.2

Devices.[i].GUID

GUID for unique identification of the device

C.3

Devices.[i].id

Complete device ID incl. “device_” prefix, catalog no. and version information, e.g. device_RevPiCore_20160818_1_0_001

C.4

Devices.[i].type

Positioning type of the device (according to key “devicetype” from RAP file)

C.5

Devices.[i].productType

Code number of the product type in the KUNBUS product range

C.6

Devices.[i].position

Position 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.7

Devices.[i].name

Name of the device – from device data table

C.8

Devices.[i].bmk

Decice identification code of the device – from device data table

C.9

Devices.[i].inpVariant

Input variant of the device – from device data table

C.10

Devices.[i].outVariant

Output variant of the device – from device data table

C.11

Devices.[i].comment

Comment on the device – from device data table

C.12

Devices.[i].offset

Absolute offset of the device in the memory image

C.13

Devices.[i].inp

Subrange of the input data of the device; for each input value there is an array with the following structure:

1

“0”, [

2

“Input_001”,

3

“0”,

4

“16”,

5

“70”,

6

false,

7

“0036”,

8

“”,

9

“”

]

Explanation:

1

Serial number to facilitate array processing

2

Name / description of the value; may be qualified by serial number, if values with the same name already exist.

3

Default value

4

Bit length of the value

5

Offset compared to device offset

6

Is the value exported?

7

Sort sequence for restoring the original display sequence in the value editor table

8

Comment

9

Contains the bit position (starting with 0) for BOOL values

C.14

Devices.[i].out

Subarea of the output data of the device

Description see C.13

C.15

Devices.[i].mem

Subarea of the memory data of the device

Description see C.13

C.16

Devices.[i].extend

Subarea of the extended data of the device; this area is filled if the device allows an extended data acquisition by the menu item “extended data” in the device menu. The data stored here and their structuring depend on the respective device.

C.17

Devices.[i].extend

Subarea of the extended data of the device; this area is filled if the device allows an extended data acquisition by the menu item “extended data” in the device menu. The data stored here and their structuring depend on the respective device.

C.17.1

Devices.[i].extend.deviceMisc

Extended device-specific data, which is available once per device only (1:1)

C.17.2

Devices.[i].extend.data

Extended device-specific data series (1:n), i.e. data available “n” times per device and usually tabulated

C.18

Devices.[i].active

true or false; defines whether the device should be enabled or disabled in the current configuration