EA eDIP240/320 Serial Graphic

eDIP240: when using touch panel letters \"R\", \"L\" and \"C\" are not displayed

I have problem with your intelligent LCD EA eDIP240-7. When I try to write using the virtual keyboard, several letters  do not print: “R  ” – “L  ” – “C  ”. This always happens in the simulator and also in real embedded applications when I try to write   these 3 capital letters. With other letters everything looks OK.

For example (R key ):
# AT X,Y, X dX, Y dY “R” 0,”R

The letters R, L and C stand for right, left and center align. The 1st letter of text is always the alignment and when omitted, then the text will be centered.

So please use CR and CL and CC , for example:
# AT X,Y,X dX,Y dY R 0,CR

How to transfer the macro files into the eDIP240?

We are currently designing  the EA eDIP240-7 display in one of our products.
So far we have programmed the EEPROM on the display using the KitEditor connected to the display via the RS-232. For production reasons we would like to write our own program that programs the EEPROM. Where can I find the specification for the commands that are required to program the EEPROM?

You can send the created macro file *.eep with any other system to the EA eDIP240-7.
All programming commands are in this file, so you only need to send the content of the *.eep file (via RS-232, SPI or I2C with the small protocol in packets) to the EA eDIP240-7.

For Windows/DOS we  have a little tool called copycom.exe

Usage (COM1) with the small protocol:

copycom projectname.eep -c1 -b115200 –p

How I am able to display a picture

I use an EA eDIP320J-8LWTP. Now I would like to implement a bitmap for a start-up screen in the display. I  installed the EA KIT editor and USB driver.

The EA KIT editor (ELECRONIC ASSEMBLY LCD Tools) is the right tool for that. When the USB driver is correctly installed  , connect the display to the USB.

Open the EA KIT editor and the file

As a first step save it, for example, as  “show_picture.kmc”

This is the code for the power-on macro:

Picture 10 <..\..\..\bitmaps\monochrome\ea2.bmp> ; double click to open

Macro: MnPowerOn

;---- Place ELECTRONIC ASSEMBLY Logo ----
#TC 0 ; Cursor invisible
#UI 101,20,10 ; place Picture no. 10
#GD 30,75,290,75 ; draw a line

I am looking for a help file while working with the KitEditor/ KitCompiler

I’ve downloaded and unpacked the LCD TOOLS. I’m working with the KitEditor to program my EA eDIP. Is there any help available  besides the datasheet?

Yes, of course. While working with the KitEditor, just press F1.
You will get detailed information about the compiler options and the commands.

If you need help on how to work with the available commands practically, you will find many examples in the following folder of the LCD TOOLS:

drive:\ELECTRONIC_ASSEMBLY_LCD-Tools-Portable\Data\eDIP ‒ intelligent graphics displays\your eDIP\How to use...

Just select a term you are interested in and open the *.kmi file with the help of the KitEditor.

Please feel free to get in touch with us if you need any further help examples.

How to work with the Small Protocol

We are going to use EA’s eDIP240-7 in our products. We have connected the module using the SPI interface clocked at 75 kHz.
The messages are exchanged by means of the small protocol. We have the following questions:

1. After sending the command (with the DC1 header) we send an additional 0xff byte to get the ACK/NACK. In spite of conforming to the 6µs time of clock inactivity EA eDIP sometimes sends a byte of unknown value (it’s not an ACK and not a NACK).
In UART mode the eDIP sends the ACK/NACK when it’s ready to send it, but in SPI mode eDIP is a slave, and the master dictates the moment for sending the acknowledgement. What value is output when this is done too early?
This is not specified.

2. We suspect there’s some time needed to allow eDIP calculate the checksum of a received message and prepare the ACK/NACK byte. How long must it be?

Furthermore, this time seems to be dependent on the current eDIP CPU load, i.e. processing of previously received messages.
The calculation takes max.  6µs after receiving the last byte (bcc).
It does not depend on the current CPU load because the receive interrupt has the highest priority.

3. Can the -SS be asserted throughout the message transfer or must it return high between subsequent bytes (as is shown in the datasheet)?
No, it’s not necessary but we recommend it.

4. Please clarify the meaning of timeout when receiving a command. Is it the time for receiving a complete message, and if it’s not received within this limit it’s dropped?

5. How can we upgrade the firmware in the eDIP?
It is not possible to upgrade the firmware.