PICASO-SGC, Related Display Modules and Softwares

[4dTechSupport]

This section of FAQ for "PICASO-SGC, Related Display Modules and Software" covers all the frequently asked questions related to,

1. PICASO-SGC processor
2. uOLED-32024-P1(SGC)
3. uOLED-32024-P1T(SGC)
4. uOLED-32028-P1(SGC)
5. uOLED-32028-P1T(SGC)
6. uLCD-32032-P1T(SGC)
7. DISP tool and PICASO-SGC
8. FONT tool and PICASO-SGC
9. FAT Controller tool and PICASO-SGC
10. Miscellaneous

[4dTechSupport]

Q01. What does SGC stand for?

Ans. SGC stands for Serial Graphics Controller. The PICASO processor can be configured for SGC mode by simply loading an SGC PmmC file. Now, the processor becomes a PICASO-SGC processor.

PICASO-SGC processor or PICASO-SGC modules are ideal for slave applications where the host controller sends serial commands to control them. For a complete list of Command set Refer to the Downloads tab on the PICASO-SGC product page.

[4dTechSupport]

Q02. Is PICASO-SGC a completely different(physically) set of device than PICASO-GFX?

Ans.PICASO , physically, is a single processor that can be configured for two modes SGC and GFX. In other words if you bought a PICASO-GFX processor and want to jump on to SGC configuration you can simply program an SGC PmmC file on the same processor to change its mode which we refer to as its "Personality".

[4dTechSupport]

Q03. What is the difference between PICASO-SGC and PICASO-GFX processor?

Ans. SGC and GFX are configurations of the PICASO processor.
PICASO-SGC is designed to be a slave device where it needs serial commands from an external Host controller to operate. PICASO-SGC also have the scripting language feature which allow it to run scripts from the micro SD card.

PICASO-GFX is designed to be a standalone device. It needs 4DGL program to be loaded to the module and it works accordingly. You still get the access to the com port to communicate to the external devices serially.

[4dTechSupport]

Q04. What are the necessary Development/AID tools for PICASO-SGC?

Ans. Development tools are PmmC Loader, DISP Tool, Font Tool, RMPET Tool and Graphics Composer. AID tool, FAT Controller.

Note: PmmC Loader, DISP tool and FAT Controller needs the PICASO-SGC processor or PICASO-SGC Display Modules to be connected to the PC. See USB to Serial Converter section to find how you should connect the PICASO-SGC/Display module to the PC.

[4dTechSupport]

Q05. What is the role of 4D Workshop3 IDE as a Development/AID tools for PICASO-SGC?

Ans. 4D Workshop3 IDE is not only for 4DGL code development, it can also be used for 4DSL script development.

4DSL is a Scripting language developed to provide the SGC modules, which are labelled as Slave devices, some degree of independence. The syntax of the commands is simple and easy to use. 4DSL commands can be saved on the uSD card in the form of a File called 4DSL scripting file. The script files can be called from a host controller or they can be saved as autoexec.4DS file to run automatically on power up.

For more information refer to the latest version of PICASO-SGC-COMMAND-SIS.

[4dTechSupport]

Q06. What is the extension of a 4DSL script file?

Ans. You can develop your 4DSL script in 4D Workshop3 IDE. It is saved with an extension ".4DScript".

For more information refer to the latest version of PICASO-SGC-COMMAND-SIS.

[4dTechSupport]

Q07. Why are there two modes for a Script files?

Ans. There are two modes of operation for a script file, compile mode and Run mode.

Run mode is for running script lines directly from the 4D Workshop3 IDE whilst the Display module is connected to the PC. This mode is good for testing and debugging as you can Run each command Step by Step.

Compile mode allows you to not only compile the code but to download it to the module whilst the uSD card is plugged in to the module.

Compile mode produces ‘stand alone’ code, that can be copied to the uSD card and executed from there, whereas Run mode, because it is run from within the Workshop3 IDE adds extra commands that need the IDE to work (typically all the ‘macros’). Similarly, there are some commands that are only available in compile mode (eg, SetCounter, Decrement, etc.).

[4dTechSupport]

Q08. Why do i get a compile option in Run mode?

Ans.The code always needs to be compiled, ‘compile mode’ should not be confused with the act of compiling.

[4dTechSupport]

Q09. Why can't i see my script in the FAT Partitioned card while I have already downloaded the script on the uSD card?

Ans.You need to add #origin '' in your Script after #Compile and #include to tell the processor to save downloaded script file in the form of a file with the same name as that of the original script in the 4D Workshop.

[4dTechSupport]

Q10. I see a funny filename when i load a script to the uSD card using Compile and Download option on the 4D Workshop?

Ans. The PICASO-SGC processor follow 8.3 format when it comes to filenames. If your filename is too big windows will rename it using the standard rules for converting a long filename into an 8.3 filename. Make sure your filename is less than or equal to 8 characters.

[4dTechSupport]

Q11. I am confused with the number of extensions used with a 4DSL Script?

Ans. There are following extensions associated with a 4DSL Script. See the details of each.".4DScript" When you open a new file in the 4D Workshop you get some options to choose from, of which .4DScript is one. It is the extension of the source script that you write in the 4D Workshop3 IDE. You should not copy this file to the uSD card, it is not recognized by the PICASO-SGC processor.

".WsScrpObj" When you compile a script a script object file is produced which can be copied to the uSD card manually after changing the extension to .4DS. Now this object file can be called from an external host controller using @p Run Program command.

".4DS" Any scripting file that eventually gets loaded/copied to the uSD card should be in .4DS extension because this is the extension recognized by the PICASO-SGC processor.

Note: 4DSL is not an extension of a file, it's the title of the scripting language.

[4dTechSupport]

Q12. What does an autoexec.4DS file do?

Ans. Once you have produced a WsScrpObj file after compiling a script you can change its name and extension to "autoexec.4DS" and copy it to the uSD card. As soon as you will power up your module (with uSD card already plugged in), the autoexec.4DS would start running.

[4dTechSupport]

Q13. Can i write the script to the uSD card in raw format without using FAT Formatting?

Ans. Yes you can certainly do that. Connect the module to the PC, put the uSD Card in to the module. Set #Origin to a specific Raw address such as,

#Origin 0x400 // start on sector 2

Compile and Download the script to the uSD card. Now your default script start location is 0x400 which you need to refer to when sending @P Run Script command from your host controller to run the script.

[4dTechSupport]

Q14. Why are there two PmmCs for the uOLED-32028-P1T(SGC) module?

Ans. There is slight variation in the Touch panels on these displays. These displays, as available from the Display manufacturers, have basically two distinct Touch calibration values hence two PmmCs. There is physically no difference at all to distinguish one from the other. You might have to try the other if you see touch offset on one.

uOLED-32028-P1TSGC-RXX.pmmc
uOLED-32028-P1TxSGC-RXX.pmmc (The latest batches since the middle of 2010 have had Touch settings to match this PmmC)

Note: No matter which PmmC you load, if you can, you can always use DISP Tool to calibrate the Touch panel of any SGC configured Display Module.