Problem initializing AL-162

Support for MOC/MOS/MOI/MOU/X-Board/MOP

Moderator: Mods

Posts: 5
Joined: Mon Jun 25, 2007 3:11 pm

Post by Philip » Fri Jun 29, 2007 9:53 am

Interresting findings with a logic analyzer (although I shouldn't have to be reverse engineer YOUR product initialization should be properly documented in the first place).

The MOS product initializes the parallel LCD according to the 4-bit HD44780 standard and NOT the S6A0069 as is in the Matrix Orbital spec. I've confirmed that the HD44780 initialization as is being performed by the MOS ATMega micro works, but the S6A0069 doesn't.

Also, you will note that Samsungs own S6A0069's datasheet shows a different initialization sequence than Matrix Orbitals.

The MOP datasheet is incorrect for whichever driver is being used. The website lists the S6A0069 as being the driver used, but since the MOP datasheet shows a totally different initialization and your own MOS product uses the HD44780, so it's unclear what is actually being used.

To those who run into the same walls, go by the HD44780 initialization if you don't want to pull your hair out unnecessarily.


Matrix Orbital
Matrix Orbital
Posts: 692
Joined: Thu Aug 19, 2004 3:37 pm
Location: MO Office

Post by Raquel » Wed Jul 04, 2007 10:46 am


This is why the HD44780U data sheet is at the top of the link for the MOP manuals. Our manufacturer specifies S6A0069 or equivalent driver as it says on the manual. The initialization was geared for the S6A0069, but then what was used was something more equivalent to the HD44780U.

We will get this sorted out with the manual for the MOP's.
Raquel Malinis
Design and Development
Matrix Orbital

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests