Fidelix FX-RP multiDISPLAY
Programming manual
page 16 of 38
Multiple projects on one
μSD
-Card
Multiple graphic projects can be stored on a single
μSD
-Card. This feature is useful if you have many
language versions of the same project or for
demonstration purposes. Links to a different
project folder can be defined with
“PATH:UserFiles_xxx” syntax in the link field as
shown on the right.
The folder name should be “UserFiles_xxx” where
xxx can be anything you want. The last character
of the folder name is loaded into register 3013, so
the Modbus master can detect which project is
loaded. The FX-RP multiDISPLAY demo projects
folder contains an example project folder named
“multi language example” which will help you on
your way.
Additionally, instead of using
“PATH:UserFiles_xxx”,
“LOCKPATH:UserFiles_xxx” can be used. The difference is that with “LOCKPATH”, the folders on the µSD card
get renamed. The original “UserFiles” folder will be named “UserFiles_orig”, and the folder in the link will be
renamed “UserFiles”. Note that because of this, you can only use “LOCKPATH” once with each µSD card.
The main use of the “LOCKPATH” feature is to be able to send out displays with µSD cards and only choose on
site what program wil be loaded. If the selectable projects are compiled to fit in the internal memory of the FX-
RP multiDISPLAY, selecting them will load the desired project into the memory, and the µSD card can then be
removed, making this a very useful feature for situations where you don’t know in advance with what equipment
the FX-RP multiDISPLAY is going to be used.
Uploading a project via Modbus
Graphical pages stored on the FX-RP multiDISPLAY’s internal memory or on the µSD can be updated through
Modbus registers 65278 – 65343 by any Modbus master:
65278 - 65341
64 data registers
65342
statusCPU status from substation
65343
statusDISP status to substation
1)
To start a transfer, the master sets
statusCPU
register to
0xAAAA
(upload request)
2)
statusDISP
receives
0x0000
from the display and the display will read "Loading data..." (ready for
download)
3)
Modbus master sends the first 128 bytes of the bin file and sets
statusCPU
to
0x0001
(uploading
part 1)
4)
statusDISP
receives
0x0001
from the display (download part 1 completed)
5)
Modbus master sends the next 128 bytes of the bin file and sets
statusCPU
to
0x0002
(uploading
part 2)
6)
statusDISP
receives
0x0002
from the display (download part 2 completed)
…)
... (repeat until the file is sent)
n-1) Modbus master sets
statusCPU
to
0xBBBB
to signal that file is sent (upload completed)
n)
statusDISP
receives
0x2222
from the display (download completed)
statusCPU
(written by master)
0xAAAA
Initiate a file transfer (requested upload)
0x00**
Counter for which part we are sending (uploading part x)
0xBBBB
Last part of the file was sent (upload completed)
statusDISP
(written by Display)
0x0000
ready to receive the file (ready for download)
0x00**
counter for which part was received completely (downloading part x)
0x2222
finished receiving the file (download completed)
