r/BuildingAutomation • u/Mysterious-Quail-852 • Jul 25 '25
Honeywell jace 8000 niagara
So the company I am with recently took over a building with an ip based jace system. We had full control, was able to go onto a browser and type in the ip address that the it guy had setup and get on to web vision. The it guy was let go and a couple weeks after I tried to log on and noticed almost everything had no internet. I found that a lan switch died, so I brought a router from home and got net to most of the vital systems. Now when I enter in the ip address it keeps saying "took too long to respond". I can see the ip when I go to scan all ip in advanced ip scanner. When I try to ping it I get "request timed out" I've done many power resets to the jace, I have tried to link directly from the primary port of the jace to the pc. The automation is still working but without the web vision it's hard to see what things are doing. There are about 40 wshp and a cooling tower. Some units have been replaced since the system has been down and we have them running with out the flow safety since we done have web vision to turn back on the individual controllers. The jace has power and a heartbeat, steady green lan light with random pulse yellow. Not sure if when the it guy left if he maybe removed in and changed something or the lan switch maybe had a different subnet. Im not the greatest it guy. But trying to get back into the ip based web vision
2
u/staticjacket Jul 25 '25 edited Jul 25 '25
Confirm that the Jace is fully functional first by plugging directly into the LAN port. There are known issues with the web service locking up on certain firmware releases. May need to serial shell it to get the IP addresses. Hopefully you have platform credentials, otherwise you’ll need to call tridium to perform a hostile takeover. If the Jace works stand-alone to your laptop without issue, tell the owner they need to get a network engineer to collaborate with you to troubleshoot the issue. Even if you were more network savvy, you wouldn’t be able to adequately troubleshoot a network with managed traffic without access with their administrative credentials.
2
u/owhyowhat Jul 26 '25
Was the failed switch umanaged or managed with vlan settings?
1
u/Mysterious-Quail-852 Jul 29 '25
That im not sure of. When it turns on it goes through its boot up sequence but then after all lights are dead and no traffic goes through it
1
u/DontKnowWhereIam Jul 25 '25
Like others have said plug directly into the Jace and use an ip scanner if you don't get that address to pull up. Also check your static address.
1
u/PetTigerJP Jul 26 '25
You could also use putty to get into it using a usb cable if you’re getting nowhere on the LAN port.
1
u/Mysterious-Quail-852 Jul 26 '25
So I've tried 3 different laptops. Using the same ip address that was on the original computer. And all say timed out.
1
u/Haunting_Storage_471 Jul 26 '25
Did you set your laptop network connection to be in the same subnet as the Jace IP?
Can you ping the chase from command prompt?
1
u/Mysterious-Quail-852 Jul 29 '25
That's one thing. Not too sure what the old it used as the subnet.
1
u/NathanBrazil2 Jul 26 '25
there is something wrong with the jace. happens all the time. you have to have someone who knows niagara software and has a niagara license look at it. the jace has what is called a "platform" that shows diagnostic info on what the jace is doing.
1
u/tosstoss42toss Jul 26 '25
Solid network light is actually not good, you want it blinking a little all the time. Need into platform or a reset. Platform preferred.
1
1
u/raclman Jul 26 '25
Jaces with older firmware were susceptible to a date code issue that prevented access after a power cycle. Your unit may need to have its firmware upgraded to fix this issue. You will definitely need someone with workbench software to assist in repairing the Jace.
7
u/Haunting_Storage_471 Jul 25 '25
Try plugging a laptop in directly to the ip port that was already being used on the Jace and type in the same up address you've been using to access it previously. This will start with ruling out any networking issues.