Yes, it supports Dallas One-Wire.

No, it does not. The Diablo16 processor only supports 16-bit images.

You can save your variables to Flash Banks that are not in use. You can also it to the microSD card.

Yes, however, there are so many variants of the display driver ICs that it is difficult to cover all of them into separate driver files. Diablo16 modules need a specific driver file with the display initialization settings fully built-in. At the moment, the only supported drivers are the ones used by 4DLCD products.

If you’re interested in using a 4D graphics processor with a custom display, please submit a ticket to contact the technical support team.

You can try utilizing 4FN and 4XE files. These will allow you to compile 4DGL code and save it to Diablo16’s Flash Banks or microSD.

These files can be called/run when needed by your main program.

No, you cannot use folders in the microSD card with the Diablo16-based display modules. Files are only accessible from the root folder.

Yes, it is desirable to download/run the program from RAM to eliminate unnecessary FLASH write cycles.

Yes. Diablo16 graphics processor does not support SPI.

Yes. Diablo16 display modules support I2C. However, it only supports I2C Master mode. The display can’t behave as an I2C slave.

No. Diablo16 display modules do not directly support RS232.

However, you can use MOTG-RS232 to connect a Diablo16 display via RS232. This will require one of the COM ports.
When using a gen4-uLCD Diablo16 display, it is advisable to use a gen4-MOTG accessory board. This allows easy connectivity with the MOTG-RS232 through Diablo16’s configurable COM port.

When using a non-gen4 uLCD Diablo16 display, a MOTG-Breadtooth can be used instead.