HVAC-Talk: Heating, Air & Refrigeration Discussion banner
1 - 19 of 19 Posts

I-Con Systems

· Professional Member
Joined
·
30 Posts
Discussion starter · #1 ·
The National Weather Service has changed the way they report the weather. When a JACE tries to update the weather the NWS redirects the JACE to an RSS feed. This causes a fault in the JACE and puts the JACE into an infinite loop of redirects. The Watchdog service in the JACE recognizes this as a fault and shuts down the station. The station stays down and reports a fault. Long story short, this causes the station to fail and takes the building down.

Niagara Central has updated JAR files for AX versions 3.4, 3.5, and 3.6. I have successfully used the 3.4 JAR file on a 3.3 system.
 
Discussion starter · #3 ·
does anyone have a fix for the 3.0 systems?
There are three things you can do.

1. Try the 3.4 version of the updated weather.jar file from Niagara Central.
2. Upgrade the Niagara software. This would require a license upgrade.
3. Delete any links and references in the station to the weather service. Delete the weather service. Then uninstall the weather.jar file using the software manager. (I tried this but was not successful. The station still tried to find the weather module and failed to start.)

Charles
 
I tried 3.4 but it doesn't work.
upgrading is not an option as it won't start after upgrading.
this is a johnson FX40. I can only upgrade to 3.0 any further and it locks it right up.
 
The National Weather Service has changed the way they report the weather. When a JACE tries to update the weather the NWS redirects the JACE to an RSS feed. This causes a fault in the JACE and puts the JACE into an infinite loop of redirects. The Watchdog service in the JACE recognizes this as a fault and shuts down the station. The station stays down and reports a fault. Long story short, this causes the station to fail and takes the building down.

Niagara Central has updated JAR files for AX versions 3.4, 3.5, and 3.6. I have successfully used the 3.4 JAR file on a 3.3 system.
I put in the new jar file and now everytime I go back to the stations, it has reverted back to Richmond, VA! :censored:
 
Save
Upgraded the 3.5.34 last week but still had to make a manual change to make it work.
Check Niagara Central for the changes that you can make manually for it to read data from the new weather service URL. I did that before the jar files came out and it worked fine.
http://www.niagara-central.com/ord?portal:/dev/PacmanIssue/20839
 
Save
I have older 3.3.31 JCI Jace's out there and for whatever reason they do not like the el'manual :gah:

For whatever reason I am also unable to unhide the "advisories" server/path/alarm extension and thinking that might have something to do with it as well?

anyone else?
I just fixed 2 - 3.3.31 JCI Jaces using These slots. you may need to add them. They are all baja String. Just go to WeatherService - WeatherReport - Provider.

The slots are.

ForecastServer
ForecastPath
ConditionsServer
ConditionsPath

Now when you go into properties you will see them. here are the entries you need

Forecast Server graphical.weather.gov
Forecast Path /xml/sample_products/browser_interface/ndfdBrowserClientByDay.php
Conditions Server www.weather.gov
Conditions Path /xml/current_obs/
 
I just fixed 2 - 3.3.31 JCI Jaces using These slots. you may need to add them. They are all baja String. Just go to WeatherService - WeatherReport - Provider.

The slots are.

ForecastServer
ForecastPath
ConditionsServer
ConditionsPath

Now when you go into properties you will see them. here are the entries you need

Forecast Server graphical.weather.gov
Forecast Path /xml/sample_products/browser_interface/ndfdBrowserClientByDay.php
Conditions Server www.weather.gov
Conditions Path /xml/current_obs/
been there and done that...

next
 
I just fixed 2 - 3.3.31 JCI Jaces using These slots. you may need to add them. They are all baja String. Just go to WeatherService - WeatherReport - Provider.

The slots are.

ForecastServer
ForecastPath
ConditionsServer
ConditionsPath

Now when you go into properties you will see them. here are the entries you need
Forecast Server graphical.weather.gov
Forecast Path /xml/sample_products/browser_interface/ndfdBrowserClientByDay.php
Conditions Server www.weather.gov
Conditions Path /xml/current_obs/
Can someone give me some help with this. I have 3.3.31 fx60 and when I go to the weather service I can't seem to find the correct place to go to actually plug the values into the slots. I do have to the slots under the provider. Just not sure what properties are being refered too. I've looked at the property sheet of the provider and the service, but I don't see a place to change these settings.
 
OK...Once again I should have looked harder the first time. I noticed when I went back to the slot sheet of the provider for the 10th time that those needed slots where HIDDEN!!! Now they are not!:whistle:
 
Can someone give me some help with this. I have 3.3.31 fx60 and when I go to the weather service I can't seem to find the correct place to go to actually plug the values into the slots. I do have to the slots under the provider. Just not sure what properties are being refered too. I've looked at the property sheet of the provider and the service, but I don't see a place to change these settings.
You need to unhide the slots under the provider ( Config Flags ) and edit via the property sheet
 
I did notice however that for whatever reason in this particular 3.? JCI Jace that I could not edit/ un-hide the advisory slots? They were clearly pointed elsewhere... :gah:
I read it wasn't until version 3.4 that they would allow you to expose those points. Read that several months ago prior to this latest weather fiasco.

I fixed a site via the browser this afternoon by exposing the slots and editing the URLs. Work out fine for me, all other sites I could get to with workbench I just replaced the modules.

This isn't the first time the weather service caused Jaces to crash. I actually stopped using for a while because of issues in the recent past.
 
Save
1 - 19 of 19 Posts
You have insufficient privileges to reply here.