I believe the 403 has a lon node limit of 27, unless you get the extended node version, which makes the lon node limit 120??
I believe the 403 has a lon node limit of 27, unless you get the extended node version, which makes the lon node limit 120??
126, the local device is default 127
I guess I should open my eyes, the FX-40 documentation says it support up to 100 devices, I guess that makes it a 403ext.
i always leave my eyes open when doing controls
You upgraded with who m's software ???
I just used the Fx-40 like any Jace403. When you upgrade a FX-40, the licences stays the same so the FX-40 is still from JCI and the licence reflects that.
To upgrade any Jace to 3.2 you just need a pc with a Workbench in 3.2 and that the jace you are upgrading has a valid 3.2 licence in it.
If you bought your Workbench via JCI, you probalbly don't have version 3.2 so you wont be able to upgrade.
Honeywell's 3.2 works ?? Without licensing issues then ???
Once you go 3.2 you cant go back
In that case I wouldnt gamble on it.
So, anyone know why JCI Jaces are coming out with 3.2 licenses then??
I just ripped out an FX40 and replaced with it with a Honeywell 3.2 Jace, just to make sure nothing bad happened.
btw,,, that resolved my troublesome FX LON job
Rumors are early next year for 3.2 and other JACE options.
Were you having problem with the FX-40's memory? We have a job where the FX-40's resets for now reasons. We trended the memory of the FX-40's with a AX Aupervisor to see that it was slowly going down to a point were the station could'nt save itself and then rebooted! JCI could'nt find anything wrong. We the received 2 new FX-40 with 3.2 licence in them and for some reason the memory leak seems to have vanish. We have put those 2 FX-40 on close supervision and are waithing for the final result in a couple of weeks to make sure the memory problem is resolved.
Maybe thats why JCI is licensing their FX-40's with 3.2 licences so they can take advantage of some fix when needed?
More read/write errors then memory issues, tons of lost messages, etc. on the 40'S
Although on the 40's I do notice my used heap always exceeds the 75% mark, more like 98%... no matter how many devices on the bus.
Sounds like yours is going out on a watch dog timeout ??
Whats Lon utilities say ??
Are you seeing any errors under the log history or station director???
Have you tried adjusting your polling times to a longer interval, with multiple tunning policies for the NV'S that don't need to refresh as often, and faster for the ones that do??
Like maybe 5 min for default and 30 seconds or so, for things running logic in the Jace/supply air temps, etc.
History intervals???
Something obviously is accumulating over time, slowing it down till,, watch dog time out/crash....
Patsy, I think they have recommended turning the autosbogsave from 3 to 1. We have turned ours all to 0, and the mystery reboots/lockups have ceased.