Hi all,

I'm trying to make a screen saver as dynamic text. I would like to have that text changing from time to time and moving like image does. The questions are:

* can I decide what area(x,y range limits) image/text is moving?
* can I change speed of moving object or it is fixed value?

Hello,

This issue occurs when accidently loading a Cleo35 sketch onto a Cleo50. Please see below for instructions on how to resolve this issue and a BIN file for re-flashing the Cleo50.

Instructions:
ftp://u45902898-gavinmoore:ftd1$erv@ftp.ftdichip.com/CES/CleO/Cleo50%20restore.pdf

BIN File:
ftp://u45902898-gavinmoore:ftd1$erv@ftp.ftdichip.com/CES/CleO/CleO_Factory_Firmware%2050fix.bin

Best Regards,
BRT Community

Hi,
I am studying using the CLEO50 module.
While testing a program that outputs BMP files to the screen,
The screen changes as shown below.
Note that the size of the bmp file is over 1M bytes.
Thereafter, no operation is performed.
However, the firmware upgrade is normal.
Is there a way to fix it?

Hello,

You can have a look at section 7 of the following application note which covers loading PNGs and inflating images:
https://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/ICs/EVE/BRT_AN_014_FT81X_Simple_PIC_Library_Examples.pdf

Best Regards,
FTDI Community

I noticed that edge strips don't anti-alias, so need to be outlined anyway.

Using Scissors is the easiest way for simple shapes, but doesn't allow for moving the shape using vertex offsets. For that, stencilling is required.

For shapes with relatively thin diagonals, drawing multiple parallel lines seems to be the easiest way.

I haven't been able to get compressed images to work yet. PNGs load, but return zero length.
I'm now trying to upload compressed raw L4 converted output from the Asset Converter. For some reason it doesn't compress files when 'compressed' is selected. I've written a python script to compress the raw files and output to c array, but so far I've only gotten errors from CMD_INFLATE.

CMD_GETPROPS is returning {0,0,0} for me.

CMD_LOADIMAGE completes successfully.

I've checked that I'm reading out correctly from the CMD buffer by including the command when reading out, and checking its value is correct.

The only error condition in the documentation is CMD_READ == 0xfff.
It says nothing about zero return params, so far as I can see.

Any clues what might be wrong?

"cmd_loadimage" decodes PNG into various image formats based on the PNG image properties.  It might be in
Paletted4444, or L8 or RGB565.   So user may need use cmd_getprops to retrieve the decoded size to calculate the next available address.

To use cmd_getprops, please see the example in "cmd_regread". It is common practice to read the output parameter from EVE coprocessor buffer.

Hi,

I was hoping to be able to draw filled polygons using an FT813 so that I can replace some large icon bitmaps with a small list of vertices, saving me a whole load of flash memory space.

I looked at application note AN334 https://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/ICs/EVE/AN_334-FT801_Polygon_Application.pdf and I saw filled polygons.
On closer inspection, it seems that the polygon is split up into smaller sections so that they have vertical and horizontal edges for the scissor command to trim to.
This makes diagonals impractical however, as they would have to be cut up into squares whose sides match the width of the diagonal section. A long thin diagonal would require many cuts.
Concave polygons also need to be chopped up into straight edged convex pieces, and would need some thinking about..


Firstly, is filled concave polygons something that is likely to be supported in the future? Are the existing range of chips field upgradable, or would this feature require rolling out a new product?


Secondly, what would be the best way of getting around this?

1) I could draw over the unwanted part of the polygon with another polygon set to the background colour, but this wouldn't preserve non uniform backgrounds.

2) Perhaps I could draw to the stencil channel instead, but the stencil is 1bit and wouldn't have nice smooth edges when I fill, so far as I can tell from the docs, haven't tried it yet. I suppose I could then draw the outline with with a LINE_STIP to get the anti-aliased edges.

3) Or I could break up the icons into smaller components and composite them, making use of completely blank rectangular bitmaps that can be generated with the MEMFILL command and using the bitmap transform to rotate them to get the diagonals. Rotating bitmaps is a bit iffy, though. I did try animating a rotating circle and it did not look good. Its size and position kept shifting about.

4) Or I could give up and just use bitmaps, take the hit on space, hope deflate does a good job.

I think option (1) would suit my immediate needs, but I'd like to know if other folk have encountered this limitation, how they've gotten around it, and why that method, so I can make an informed decision before making a commitment.

Cheers,
 AT38

Could you not trace the previous owner and see if they still have the card?

Hi,

 Thanks for your reply. I figured out the problem as I collated data.
 I was sending the parameters for the text command as 32bit instead of 16bit.
 The hash on screen was the text command reading out from an invalid bitmap cell and then falling over.
 Probably corrupted the display list after that, hence no dots, but still accepting touch input.

 I'm developing my own library, fyi.

Cheers,
AT38