Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Info Updates from June 28 - September 01
#1
Updates from June 28 - September 01:

  • Updated ethernet module
    updated all modules using network to work on any network interface, including ethernet
    Ftp server and Telnet server now also works over ethernet
  • Refactored display module
    • prepared for implementation of e-paper displays support (comming soon)
    • added support for FTDI EVE (Embedded Video Engine), FT80x and FT81x
      • FTDI EVE offers amazing graphical capabilities, especially on FT81x.
      • Hardware accelerated graphics functions, transparency, internal and external fonts, hardware jpeg decoding, extremely fast bitmap handling, bitmap scalling, rotation alpha blending, even playing avi video files (mjpeg encoded) up to full screen resolution, animations, audio, widgets are only the part of the features
      • Easy to use programming using display lists
      • Affordable display prices, for example 5" 800x480 FT810CB-HY50HD on which development was done is only 33 US$
      • some demos, not in MicroPython, but can be programmed in MicroPython too: demo1demo2demo3demo4demo5
      • This is a complex module, full documentation and examples will be available soon.
  • Added requests module
    • requires much less resources than curl module
    • implemented get, post (including multipart), head, put, patch methods.
    • based on esp-idf esp_http_client componnent
    • SSL enabled, server certificate can be given
  • Updated gsm module (Wiki)
    • added option to allow connection when in roaming
    • added method ifconfig() to get the IP, netmask and gateway
    • some small improvements
  • Updated SDCard handling and uos.sdconfig()
    • SPI host can be selected for SDCard in SPI mode
    • some bug fixes
    • Wiki
  • Updated curl module
    • added getmail() method (Wiki)
    • added option to set maximum write buffer size, lower size can make it more usable on boards without psRAM
    • tab character (0x09) is now accepted in response body
  • Bug fixes
    • machine: fixed bug in 'deepsleep' method, deepslep for all timeout values now works as expected
    • machine.DAC: fixed bug in 'waveform' method, the 'duration' argument now works for waveform types
    • machine.Pin: fixed bug in handling the 'debounce' argument; improved irq handling
    • machine.DHT: fixed bug: when a DTH22 sensor is used, the results were always truncated after the decimal place
  • Updated esp-idf to version v3.1-rc1-53509c7b
  • Other minor updates, improvements and bug fixes

Full list of updates is available on GitHub

Wiki documentation for new and changed modules will be updated soon.
Reply
#2
Thanks once again your the work you have done Smile

The FTDI EVE looks super interesting. I am right in thinking there is a processor on board the screen that does a number of graphics processing to remove these overheads from the main MCU??

How many pins does the FTDI EVE  interface need??
Reply
#3
Will your library also work with the slightly smaller http://www.hotmcu.com/43-graphical-lcd-t...cPath=6_16
Reply
#4
The library is working with any EVE controlled display, only the correct display configuration has to be declared.
Some predefined configurations are available via menuconfig.
If you are interested in the smaller EVE based displays, Riverdi and Matrix Orbital have some small displays (but large ones too).

Using displays based on FT81x is recommended over FT80x as it has many improved features, higher maximum resolution and more graphic memory.

FT8xx has a powerful graphic processor. You are actually not drawing pixels, but populate a  display list of various graphics object and widgets which are rendered to the display by graphic processor in real time.
Here are some links to more information on EVE FT8xx:
FT800 From the Ground Up
FT81x data sheet
There is also an interesting book Gameduino 2: Tutorial, Reference, Cookbook. It is available on Internet in pdf form, but I think it is copyrighted, so I wont give the link.
It is the manual for Gameduino board, but has many tutorials/examples which can help to understend how EVE works. All video examples on the linked page should be easily converted to MicroPython.

EVE based displays uses the SPI interface, so 4 pins are needed (reset pin can be used too, but it is optional, there is also the interrupt pin, which is not used in the current driver).
FT80x also supports I2C interface, but it is not supported in the current driver.


Attached Files Thumbnail(s)
       
Reply
#5
Some additional info about EVE module.

Two subclases are included in EVE module which may be of interest.

console
  • text oriented display 'window' of defined number of columns and rows for displaying text (monochrome or VGA 16-bit color)
  • uses only column*row bytes in EVE graphic memory
  • can be placed on any position on screen
  • uses fixed width font 8x8 (monochrome) or 8x16 (VGA color)
  • the console 'window' can be scalled
  • can be drawn with transparency
  • VGA color mode accepts foreground/background color attributes
  • word wrap possible
  • automatic scroll when writting past the last row
  • shows on screen combined with any other EVE objects
  • comming soon: scroll buffer larger than the visible area
tft
  • a bitmap 'window' which can be used as framebuffer to draw the same way as in TFT module
  • almost all methods from TFT module can be used to draw on that 'window'
  • can be placed on any possition on screen
  • can be scaled and drawn with transparency
  • shows on screen combined with any other EVE objects
Reply
#6
Thanks for all the info. I will sit down and read though how EVE works a lot more.

I ordered this smaller 4.3" cheaper screen with the FT800 due to the size being better for my uses. FT800 http://www.hotmcu.com/43-graphical-lcd-t...cPath=6_16

Price is crazy cheap for everything it has including case for mounting.
Reply
#7
The external dimensions of the 4.3" display (the frame) are the same as of 5" one.
The price of the 5" one with FT810 is only 8 US$ higher, so it is probably better choice as it has newer, more powerfull chip.
Reply
#8
Great job!
FTDI EVE looks very interesting.
When you update the Wiki, can you please add an example for Bluetooth.
Thanks.
Reply
#9
The documentation for Bluetooth (RFCOMM) should be available in a couple of days, and for the EVE module probably at the beginning of the next week.
Reply
#10
great job! thanks a lot!
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)