We have been working with the iLon100 now for almost 2 years, and there are still things that perplex me with this web server. The ilon100 that is giving me problems is a first generation model, running firmware version 1.02.06 and bootrom 1.00.52. This particular iLon has been up and running now for almost 2 years, but recently I have been getting a lot of errors on my network through the iLon, causing a very slow response time when I look at my live points. The web pages themselves seem to load very quickly after the iLon has been rebooted but as soon as I click on a page to view the live data, it gets very slow almost standing still. It gets progressively worse until I can't even pull up my web pages. Coming from an IT background I blamed the router or internet connection first. After checking both, I realized it was either my Lon network, or the iLon itself. The part that bothers me the most is that I can no longer get into the iLon with the echelon plugins. I do have several different computers at my disposal, all with LonWatcher on them and all with the iLon plugins, so my point is it's not the computer. Well this is getting longer than I had hoped, so my question is; is there anything that I can do to try to bring this iLon back? Is there a way that I can wipe it clean and start fresh? Maybe a firmware update?
Thanks for any and all help.
apply the latest updates/upgrades, there has been many fixes.
then if you still have problems, look at your poll rates.
Yeah there was a bunch of firmware updates, key word here is was. Going back now and checking Echelons site, all I see are updates that apply to the e2, and a data logging update to the original iLon, that's it. On a side note, all my poll rates are set to 120 sec; I changed that from the original 5 sec poll rate that was default. Unfortunately without getting into the plugins, it makes changing anything very difficult.
I believe the latest update is retroactive, just be sure to update bootrom first then apply the image upgrade.
goto echelon download area and read the readme files, to see procedure to upgrade to e2 from ver1
I am not sure if i understand why you can not use the plugin, what is the error?
[Edited by amigo on 10-05-2005 at 12:11 PM]
You could wait a little bit here and upgrade your existing units to the e3 version.
Otherwise you may want to implement JACK to radically improve the speed. We have a JACK site running 746 NVE's with an average poll rate of 12 seconds.
The upgrades should solve your problem however.
Sysint, where can I get more info on JACK? The ilon is getting around 200 Data Point Message Failures a day. We probably have 450 NVEs running.
It sounds like you've got a huge amount of polling going on with 450 nve's. Excess network traffic can really affect response times. I'd put a protocol analyzer on the channel and check the bandwidth consumption. Also, you might check the polling rates for the nve's and make em longer. Poor response time is usually an indication of an overloaded channel.
Sys- so when can we get our hands on e3? How much?
A hundred million nodes - it's a LON story.
We have 58 devices on one channel. Do you think adding a router and splitting the devices would help?
Well it depends. If all the devices are talking to each other then it probably wouldn't help much to add another channel. Routers basically filter message traffic based on the destination address.
You really need to see what traffic is happening on the channel and that requires a protocol analyzer. You can download the new LonScanner for free from Echelon and it will run in the demo mode for 10 minutes.
There's a few ways you can reduce traffic - set heartbeats longer (remember to set the receive intervals at 3x the send interval), set throttles and send on deltas to match the dynamics of the point, and maybe use unacknowledged message service on non critical bindings.
Definitely get a protocol analyzer on the channel and let us know what you find. BTW, you can download some files into the iLON100 and run the protocol analyzer remotely over IP.
A hundred million nodes - it's a LON story.
Excellent, I'll try it and let you know.
Just a note with changing message service types. If you leave it at default it is acknowledged - LonBoy taught me that - I had a system with less than 40 nodes all using the default message type and I was losing information constantly. I added terminators early on in the job to help as I had about 10 nodes or so to add yet. I went back through and changed all my message service types to repeated unacknowledged and my network went from poor performance to great. I did not put an analyzer on the network at all but no longer were devices going offline and I added my other devices and still am amazed at what that simple change did for my network. I've just been going through and changing all my message types to repeated unacknowledged but most of my networks are under 60 nodes and all I am controlling is HVAC for the most part.
"How it can be considered "Open" is beyond me. Calling it "voyeur-ed" would be more accurate." pka LeroyMac, SkyIsBlue, fka Freddy-B, Mongo, IndyBlue
BIG Government = More Dependents
"Any 'standard' would be great if it didn't get bastardised by corporate self interest." MatrixTransform
My 5 yr old son "Dad, Siri is not very smart when there's no internet."
"Sys- so when can we get our hands on e3? How much?"
Order one today. Should be the same.... unless you order w/routing capability added.