Matrix Orbital Corp

I have a LCD0821, serial connected, to a Supermicro X8DTH MB. When I turn the system on the LCD displays the MO logo. Thats good.
As the boot process continues, random gibberish appears on the LCD. Is there any way to prevent the gibberish from appearing?

Hi Ray,

The LCD0821 will typically display all information sent to it. Ideally, you'd try to eliminate any gibberish data sent during the bootup process, but you could also set and save the datalock to block all text and setting changes, then set the datalock to the lowest setting once the unit has booted.

Thanks,
Troy

Can y'all tell me if there is a firmware difference between 09M05-0218 and 09M05-0282 ?

Hi,

The LCD0821s with sn# 09M05-0218 and 09M05-0282 have the same firmware version, v6.0.
If you please send the command 254 / 54, the displays should report back 0x60.

Are you seeing different behaviour between the two? Can you please give more details of what is happening?

The machines are supposed to be identical. The customer says that some of them act correctly and some of them
act like the second line in the graphic below. The gibberish always the same.

Any ideas on what I should check?

Hi Ray,

Given the images provided, I would recommend checking the baud rate of those units to ensure that it hasn't been changed inadvertently.

If you continue to have trouble, please provide a list of the commands sent or even the start-up code if available, and we'll try to replicate here.

Thanks,
Troy

Here's some ramblings:

uProject- Display Tuner R.v0.7 - untitled.usf
Baud rate on Com Setup tab = 19200
Baud rate on Main tab = 19200
Clear Display button does nothing.
Load Startup Screen clears the display.
Set Cursor Position (row 1, column 1) causes random gibberish.
Show Large Digit-clock causes constantly changing random gibberish.
Send Text button with the text"testthis" -> text starts in row 1 column 8 and wraps to row 2.

Any ideas?

Hi Ray,

Please search your documentation for the Manual Override section, is there any improvement with the override jumper in place and the settings forced to default?

Thanks,
Troy

The LCD seems to work as expected with the jumper on.

Clear works. The text that I send to it is in the expected place. Bar graph demos work.
What next?

Hi Ray,

Good to hear the override is working, now to save the settings to their defaults.

In override mode, open up uProject, make sure you can communicate with the display, then move over to the uploader tab, and open the unzipped version of the .usf file attached. Hit run, wait for the script to complete, and you should be back to default. Remove the override jumper, cycle power, and try to communicate once more to confirm.

Thanks,
Troy

This is not exactly defaults. The MO logo no longer shows at power on. Not really that important at this point.
The system now boots to the operating system with a clear screen, no gibberish. When I go into UProject to send
text to the screen it still doesn't show up in the right place. If I send the phrase testthis the test starts in row 1
colum 2. I am expecting it to start in colum 1.

BTW, the clear screen button doesn't work and set cursor position sends an un-recognizable character to the screen.
the bar graph demos send garbage to the screen.

Hi Ray,

My apologies, the file I sent was meant to quickly reset the important settings such as baud rate, backlight, and contrast. The file I have attached now will take a little longer and rewrite all memory. Please ensure you can communicate successfully and repeatedly to the unit before starting the memory initialization.

To use this file, again place the unit in override mode, ensure you can communicate successfully using uProject, then hit the Initialize Memory button near the top right of the main window and point to the file.

This process will take longer than the usf file. Once complete, cycle power and check communication once more.

Thanks,
Troy

Thanks Troy. This appears to have worked. I'll pass it along to my customer and let you know how it goes.

Good to hear Ray, if you have any trouble implementing the memory initialization please let me know.

Also, if this type of problem is common, you might investigate the Set and Save Data Lock command in your manual to try to prevent inadvertent setting changes.

Thanks,
Troy

My customer has 13 that work properly and 15 that have problems. We'll see what happens when the memory update is applied.

The one I've been using for trouble shooting was a brand new one.