A recurring error dated 2033

[pioneerMan]

This error continues to always present itself at the top of the list of events. I assume because these are sorted by date, and this particular error has a date in the future. Is the tech team aware of this "bug" in the firmware? And yes, the date and time are correct on my Mate 3s.

[David LeBow]

You didn't list an Optics site in your profile, so I couldn't have a look.

Can you tell me what firmware version your Mate3 is running?

From the Mate3 home screen:

Steps from home screen:
1. Press Lock
2. Enter user code
3. Press Enter
4. Choose Settings
5. Choose System
6. Choose Firmware Versions

[pioneerMan]

I have a folder on my computer containing the most recent firmware that was installed on the Mate. The folder has a name of:

mate3s_1_4_6

Now that I have the attention of the tech team, is this also the right place to ask why some dates in the Mate use 24 hour military time and other places use a 12 hour time stamp? Why isn't there a consistent standard throughout?

[David LeBow]

Could you please follow the steps shown above on your Mate3 and post the version results?

[pioneerMan]

Mate3s = 001.004.007

[David LeBow]

Thanks,

There were changes made in 1.4.7 which can leave some old event log entries "uninterpretable" - I think that your 2033 event is similar. If you look at page 50 of the Mate3S Programming Guide (https://www.outbackpower.com/downloads/ ... de_web.pdf), you can see how to delete events from the Mate3S event log. Give that a try to see if you can lose these undesired entries.

About the 24/12-hour issue: this is a known issue. The developer feels that it only (ok, "only") visible on the live time display on the generator page and shouldn't otherwise affect any operations. There's a development ticket to look at this in a future release.

Hope that helps!

David

[pioneerMan]

About the 24/12-hour issue: this is a known issue. The developer feels that it's only visible on the live time display on the generator page and shouldn't otherwise affect any operations. There's a development ticket to look at this in a future release.

That's not quite true, as you can also see it in the Event History Detail page:

[pioneerMan]

There were changes made in 1.4.7 which can leave some old event log entries "uninterpretable" - I think that your 2033 event is similar. If you look at page 50 of the Mate3S Programming Guide, you can see how to delete events from the Mate3S event log. Give that a try to see if you can lose these undesired entries.

I gave it a try and it did not go well. There are only preset options to choose from, like delete:

last 1 day
last 2 day
last 1 week
last 1 month
last 2 year

etc.

There is no option to delete an errant event log dated 2033 without apparently deleting everything. Or am I missing something?

Thank you.

[pioneerMan]

David, is there any other option other than deleting ALL of my saved events in the log?

[David LeBow]

I'm not a Mate expert, but poking around the folks who are, it doesn't seem that there's a way to just delete that one zombified event entry besides clearing the log altogether. I hear that page 47 of the Mate3s programming guide explains how to export the log before clearing it, if that's something you'd like to do first.

[David LeBow]

An additional thing to try. I do not have a way to test this or confirm this today, but the Mate3 manual has more detail about Event Log management than the Mate3s manual. According to the Mate3 manual, if the user scrolls through the list of events until the rogue event is selected, then presses Continue, he will be prompted to delete the event. Seems an easy thing to try.