Bitmap upload problems on GLK19264-7T-1U

kevan.t · Post by **kevan.t** » Mon Jul 21, 2008 4:57 am

I am trying to upload a bitmap file to my GLK19264-7T-1U (USB) following the instructions in your Technical Manual version 1.1.

The code gets as far as starting the data upload - it has received confirmation (0x01) from the unit to say the file will fit. After the first byte I wait for the echo....which never arrives.

Can you help?

The file I am uploading is 192 pixels wide by 64 pixels high. The bytes I am sending are:

0xFE (command prefix)
0x5E (upload bitmap command code)
0x0A (refID)
0x00 (size LSB)
0x30 (size MSB)
wait for confirmation - 0x01 received)
0xFF (first data byte, 8 pixels, all set to 1)
wait for echo - none ever received

Clark · Post by **Clark** » Mon Jul 21, 2008 2:37 pm

Hi Kevan,

The file upload protocol is without a doubt, the hardest function to program on any of our displays. I'll do my best to help you through it.

First up, our protocol has been found to be slightly different than the version that is published in the revision 1.1 manual. Our software developer for MOGD# actually figured out that the display will expect a two (2) byte response including a confirmation.

Please have a look at this post for a better idea of the protocol expected.

If you've got any further questions, don't hesitate to post them.

Thanks,
~Troy

kevan.t · Post by **kevan.t** » Tue Jul 22, 2008 2:01 am

Troy, thanks for the immediate response. This is the kind of technical support we like!

I downloaded the excellent Portmon and captured a bitmap upload to the display using MOGD#. All appears as expected EXCEPT for some extra stuff after MOGD# receives the CONFIRM(0x01) following transmission of the file size MSB to the display.

Specifically, MOGD# sends 0xC0 and the display echoes it. MOGD# then sends another CONFIRM(0x01) followed by (0x40) which the display then echoes(0x40). MOGD# then sends another CONFIRM(0x01) before sending the first byte of the data. Things then proceed as the manual states to their successful conclusion.

0xC0 = 192(decimal), is the width of my bitmap. 0x40 = 64(decimal) is the height of my bitmap.

Sooo... I guess I have to send the bitmap pixel width, wait for echo, send confirm, send bitmap pixel height, wait for echo then confirm, then send the data as prescribed. Can you confirm this?

Thanks for your help.

Post by **Ray** » Tue Jul 22, 2008 7:17 am

I can confirm this however the sending of the width and the height (Both a single byte) are part of the bitmap data not the upload protocol so be sure to increase the filesize you are sending with two bytes as well.

kevan.t · Post by **kevan.t** » Tue Jul 22, 2008 8:13 am

Thanks for confirming that.

I have a further question...

I have implemented the upload protocol correctly now but I was still not seeing the echo after sending the bitmap width. I discovered that if I removed my "WipeFileSystem" command send, which was done just before the upload, it all started to work.

I assume then that the wipe was still in progress when I started the upload.

The question is, if I do issue a "WipeFileSystem", how can I tell when it has finished and safe to upload new data?

Post by **Ray** » Tue Jul 22, 2008 8:50 am

There's no feed back on when the wipe will actually be done but a 500ms delay should do the trick just fine.