Fidelix FX-RP multiDISPLAY
Programming manual
page 15 of 38
With a multi24 module and a PC
Using the multi24 programming tool, the same “.dat-xxx” files can be selected in the “Display graphics” section.
The program will then ask the Modbus address of the display and the multi24 will be used as pass-through
handler.
With a µSD memory card
It is
possible to update the internal memory from a μSD
-card. During the power up sequence, the FX-RP
multiDISPLAY will check if a “MULTI-DISP.dat-
xxxx” file is found on the μSD
-card and if found the file is copied
into the internal memory. After that,
the μSD
-card can be removed, and the display restarted (power off and
back on). From then on, the internally stored pages are used. The advantage over using the graphics from the
µSD card is the obvious lower number of reads from the µSD card, but mainly the speed.
Make sure to verify if your FX-RP multiDISPLAY is of the first generation or the second, as the available memory
is tripled in the V2 displays. In the converter, you can tick the “Large Memory (STM32F405)” tick box when you
have a V2 display so the converter will allow you to convert larger projects.
Using g
raphics from a μSD
-Card
During the development stage of graphics or when your project doesn’t fit the internal memory, you can use a
μSD
-card to store graphics. To do so, tick the “uSD-card” tick box in the converter and copy the generated
“UserFiles” folder to the μSD
-card using a memory card reader. Insert the card into the memory card slot of the
FX-RP multiDISPLAY and reboot the FX-RP multiDISPLAY.
By using a μSD
-card you can quickly test if graphics are working as expected without the need to load images
into the internal memory of the FX-
RP multiDISPLAY. A μSD
-card also needs to be used if more than 768 kB
storage space is needed.
When using a µSD memory card, please make sure you are using cards of good quality from a trustworthy
manufacturer. SDXC cards are not readable by the FX-RP multiDISPLAY.
A good reference list for memory cards’ quality can be found here:
https://elinux.org/RPi_SD_cards.
Minimizing binary file size
If your project does not fit into the 768kB (or 256 for V1 displays) reserved for internal data storage, you may
either use a μSD
-card for data storage or try to optimise your project to use less memory. Here are some tips to
keep your total project size as small as possible:
-
Do not use more than 255 colours in images. The easiest way to accomplish this, is to convert your images.
The embedded compression of the converter only works with < 255 colours. Any images using more than
255 colours will not be compressed at all.
-
Do not change the image size using object properties. Instead use the real height and width of the image.
-
Minimise the colour count in pictures. Large areas using a single colour will not take much memory. Even if
the colour count is less than 255, more memory is needed if more colours are used.
-
For dynamic objects, use Text size 12. The “bold” option can be used. Font size 12 is embedded in the
firmware, all other font sizes will take up space from the internal memory.
-
If a larger font size is needed, keep in mind that a larger font size takes more memory than a smaller. So do
not use larger fonts than needed.
-
Minimise different font sizes used. Every different font size uses some space of the memory.
-
Try to have only “active” elements; this will make the background image easier and thus smaller. You can
make an element active by giving it a PointID. Make sure not to use a significant one already in use, like
“POINTxx”, “LINK”, but rather go for something like “UNUSED_ELEMENT” or “IMAGE”.
