ARMweb settings

[YahooArchive]

On my Armweb with newest fimware it has a quirk

I am able to change all the settings and it applys them after the reset.

I am able to change the default page and it is applyed after a reset.

However after 24hrs it defaults back to the armweb.htm site. Not sure if it is
after a reset or what causes it.

Does the unit need a battery to not be flaky in the settings dept?

[YahooArchive]

If you delete the file that was set as default it reverts to armweb.htm, could
that be what's happening?

Hey Bruce, is there any way to reset it over the network?


-MM

[YahooArchive]

Those settings are stored in Flash, I don't see how they could change after 24
hours. You would see "Restoring Settings" on the USB when you turn it on after
24 hours.

As you're the only report of this, and there are a few hundred out there, try
the 7.36 firmware to see if it does the same. Also check the connection to the
switch in the front, if you hold that low during reset, the settings will be
erased. Did you wire that to something else?

PS there is no way to reset the settings remotely, by design. That would be a
huge security issue.

[YahooArchive]

OK, That is what is most likely happening. I did not see this in the docs.

I have been deleting and uploading a revised version and this could cause the
issue you described.

[YahooArchive]

Only the web page was changing

And from a prev post it was caused by me upating the web file ie, delete and
re-upload. According to Mark this will cause the armweb file to be re-set as the
default.

Thanks

[YahooArchive]

I would expect weird things to happen if you delete the main page, and then try
to surf to it. The ARMwebs probably going to throw up its hands as you
effectively mis-configured it. At that point going back to a default is about
all you can expect.

[YahooArchive]

I'm pretty sure it reverts immeadiately when the file is deleted, without any
intervening requests for it. (My ARMWeb is in production, so I can't mess with
it to verify.)

As for what might be expected, I think simply returning HTTP status 404 would be
more intuitive and less of a PITA -- or to put in terms that aren't subjective,
it would be standards-compliant.

Parenthetically, if an HTTP server implementation changes its own config because
it seems invalid, it puts the tech responsible for configuring it at a
disadvantage: 75% of the job of fixing a non-working configuration is
understanding out why the last thing you tried didn't fly. By reverting the
tech is cheated out of a.) an opportunity to examine the errant config, and; b.)
a forth-coming error message.


My two cents,
MM