trouble shooting board V02:

1. potensio terhubung
2. terjadi short di jumper dalam mikro antara 3.3 dengan GND
The ESC generally accepts a nominal 50 Hz PWM servo input signal whose pulse wid
th varies from 1 ms to 2 ms. When supplied with a 1 ms width pulse at 50 Hz, the
ESC responds by turning off the DC motor attached to its output. A 1.5 ms pulse
-width input signal results in a 50% duty cycle output signal that drives the mo
tor at approximately half-speed. When presented with 2.0 ms input signal, the mo
tor runs at full speed due to the 100% duty cycle (on constantly) output.
https://thriva.activenetwork.com/Reg4/(S(dntwqy45dmvbytqc2a5rfh45))/Form.aspx?re
gkey=RpYOYPxE37%2bS0effZk5L2g%3d%3d
https://thriva.activenetwork.com/Reg4/(S(dntwqy45dmvbytqc2a5rfh45))/Form.aspx?re
gkey=RpYOYPxE37%2bS0effZk5L2g%3d%3d
General I2C development information.
This application note applies to displays:
Alphanumeric Displays:
LK/VK162-12 PCB Rev 3.0
LCD0821 PCB Rev 2.0
LCD/VFD2041 PCB Rev 2.0
LK/VK202-25 PCB Rev 3.0
LK/VK204-25 PCB Rev 2.0
LK402-25, LK404-25
MOI Series
Graphic Displays:
GLC24064, GLK24064-25 PCB Rev 2.0
GLK12232-25-SM PCB Rev 2.0
GLK12232-25-FGW PCB Rev 3.0
GLK240128-25 PCB Rev 1.0
GLK24064-16-1U PCB Rev 1.0
GLK19264-7T-1U PCB Rev 1.0

Q: How do I talk to the display?

A: We use a standard Phillips 7bit address as defined by Phillips. How ever, we
at Matrix Orbital specify the I2C address in 8bits. The 8th bit, least significa
nt bit (LSB or Low Order Bit) of the 8bit address is read/write bit. If we take
a standard Phillips 7bit address of 45hex this would be in binary 1000101. This
is 7bits. If one adds the read write bit to this 7bit address and you assume tha
t you are writing one gets 10001010. Matrix Orbital would describe the Philips I
2C address of 45hex as 8Ahex. The read address would be 8Bhex.

Q: Does the display reply to a General Call Address? (Address 00h)

A: No, the display does not reply to general calls address.
Q: How fast can I clock the display?
A: The display modules can be clocked up to 100 kbps.
Q: How do I read the keypad data?
A: The keypad is read by I²C master read. A simple master read transaction that is
not preceded by a query command will always return the first unread key press.
A read is initiated by writing to the module with its base address plus 1, then
clocking the module's return byte after the module releases the SDA line. To pol
l the display for a keypad press, you send your I²C display address plus one.
eg. For a display with I²C address of 0x8A, the write address would be 0x8A, and t
he read address would be 0x8B.
The module contains a ten key press buffer so that it can be polled for key pres
ses at an infrequent rate (every 250 to 1000 mS is typical). All returned key pr
esses indicate the presence or absence of additional logged key presses by the m
ost significant bit (MSB - bit 7). If the user has pressed two keys since the la
st poll of the keypad interface, the first read will return the key code with bi
t 7 set and the second read will return the key code with bit 7 clear. The appli
cation must take into account this bit to keep up with user key presses. If ther
e are no keypresses detected, the module will return zero (0x00).
It is necessary to send the following commands to be able to read keypad presses
from the display. Both commands need to be sent only once.
254 / 79 - Set Keypad Auto Transmit Off command this will make sure that keypad
presses stay in the buffer until a master read is sent
254 / 160 / 0 - Set Auto232 Tx Data to OFF this will make the display to put the
reply bytes in the I²C output buffer, instead of the RS232 output buffer.

Q: Can I get other data back form the display like Module Type or Module Version
Number?
A: Yes, you can get data like module type and module version numbers. Because t
here is only a 16 byte output buffer on the dispaly, commands that return more t
han 16 bytes from the display is not guaranteed to work. This makes the command
'Read Customer Data' (which returns 16 bytes) to be the command with the most re
turned data that is guaranteed to work.
It is recommended that there be at least 3ms delay between each read commands an
d read transactions. It is also necessary to set the command 'Set Auto 232 Tx Da
ta' to OFF (command 254 / 160 / 0) to get the display to put reply bytes in the
I2C output buffer, instead of the RS232 output buffer.
Q: Can I upload fonts or bitmaps over I2C?
A: Theoretically, fonts and bitmaps can be uploaded over I2C but this is somethi
ng that is not tested. The easiest way to perform font or bitmap upload is via t
he software mogd# (in RS32 mode).
Q: Do you use ACK? What do I do with it?
A: Yes, we do use ACK/NAK for acknowledgment of write/read transactions. Part of
the I2C transaction is the acknowledgment bit. The display will send an ACK (on
the 9th clock) when addressed. It will also send an ACK after a write by the ma
ster provided that hte write is successful. /if the write is not successful. the
display will be sending a NAK. A master write is deemed successful when the mod
ule's buffer is still capable of accepting data (ie. when it is not full). When
the module 's buffer is full or when it is busy processing data, the display wil
l send a NAK in response to a write by the master. The master will then have to
stop the transaction and re-send the NAK'd data. It is suggested that a delay is
observed to give the display time to process data. This delay is based on the d
ata previously sent to the display. For a graphic display. a minimum of 50ms del
ay is sufficient, usually the application will dictate if this delay is enoght,
or may have to be extended.