FX-40 Lon Node Limit

[Chris_Worthington]

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

[freddy-b]

Rumors are early next year for 3.2 and other JACE options.

[patsy]

btw,,, that resolved my troublesome FX LON job

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.

So, anyone know why JCI Jaces are coming out with 3.2 licenses then??

Maybe thats why JCI is licensing their FX-40's with 3.2 licences so they can take advantage of some fix when needed?

[Chris_Worthington]

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 ??

[patsy]

Whats Lon utilities say ??

There are no Lon devices on those FX-40, only N2 devices!!

[Chris_Worthington]

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....

[freddy-b]

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.

[patsy]

Are you seeing any errors under the log history or station director???

it's not log or history related, after it rebbots the memory climbs back to normal level!

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?

No LON devices on that job only N2 and we dont even have the actual N2 devices wired to all the FX-40 and still the memory goes down even on those without the N2 devices pluged in (we are creating the points offline and preparing the FX-40 station before we actually switch from NCU to FX-40)

History intervals???
Something obviously is accumulating over time, slowing it down till,, watch dog time out/crash....

... yeah but what?? I'm hopping that the upgrade to 3.2 will solve that issue: we are still in test so I will keep you posted on the result

[Chris_Worthington]

Just a FX40, no devices,,hmmmmm...

Try logging in through explorer to your IP 000.000.000.000:3011/QNX and see if those logs provide any insight.

Bizarre for sure, keep us apprised should you find resolution.

Chris

[amigo]

patsy, did 3.2 resolve your issues with FX40?

[freddy-b]

I bet if he tried it that the station wouldn't open or license. Sounds like a big mess waiting to happen to me.

[Chris_Worthington]

Any word on when JCI may be coming out with 3.2 or later??