News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Obi202 system status page error

Started by user17600, January 26, 2013, 12:33:48 PM

Previous topic - Next topic

user17600

Since upgrading my -202 to firmware version 3722, when I click the System Status link, I get the message:

QuoteXML Parsing Error: not well-formed
Location: http://1.1.1.101/DI_S_.xml
Line Number 283, Column 58:
<value hash="417db31c" type="input" default=" " current="" >
---------------------------------------------------------^

instead of the typical page with system uptime, firmware version, etc.  Tried downgrading to 3647 but this version seems very unstable (tho the system status page works properly).

Opened a ticket with Obihai, but anyone else have this same issue?

giqcass

I have seen that error a couple of times usually right after a reset but it went away when I refreshed a few seconds later.
Long live our new ObiLords!

user17600

Yeah, in the past that worked.  But this time it seems persistent, and only with that firmware version, page shows up fine with the older firmware version.

Which version are you running?


giqcass

Long live our new ObiLords!

user17600

Just to close the loop on this thread, Obi confirmed the issue and loaded a new firmware version onto my -202 (with my permission... they actually asked).  

They did not provide any details about what the issue might have been, but here is my status screen text.

ModelName           OBi202   
MACAddress   9CABCD200DDD   
SerialNumber   88D01NABBZ00   
OBiNumber           500 000 000   
HardwareVersion   1.2   help
SoftwareVersion   3.0.1 (Build: 3742:3743D)
SystemTime   19:14:23 01/31/2013, Thursday
UpTime           2 Days 5:58:58 FreeMem:23140KB (2)

What's interesting and I don't remember seeing it before is the 'freemem' statement.  Probably doesn't mean anything, but I'm watching to see what happens to the amount with use.

Anyone know how to save a copy of the firmware directly from the device?

---

CoalMinerRetired

Try viewing the same page in a different browser.

user17600

Um, well, since it's resolved... and it was a firmware problem...  How do I lock this thread?