I loaded fresh versions of 4.8 on a desktop and laptop with a brand new
license. Some items to be aware of:
1) Make sure your "Niagara" service is indeed running after you've installed it.
Even if it says it's automatic, it may not have started the first time it's installed and
needs to be manually started. My laptop ran fine right off the bat, but my desktop
didn't start its Niagara service. This will save you lots of time or aggrevation to at
least check it.
2) If you don't like the black and white display of N4 and liked the colorful AX display
better, go to Tools, Options, General, and change the active theme to Lucid instead
of Zebra. Restart N4.
3) If you're having trouble logging into your brand new station, and wondering why FOXS with
TLS protocol is the only way to login, which uses a certificate....check the Services section,
then FoxService, and make sure "Fox Enabled" is set to True which then activates port 1911.
At some point in the past, the Fox port got disabled by default and instead only allows FOXS port
4911 for a brand new station.
4) The MPX Install documentation mentions installing only two of the 6 modules. If you only copy
the two because you're trying to do the install very carefully by the book, you'll be in a world of
hurt later on and also wondering when you'll ever need to load the remaining 4 jar files. Make
sure to copy all 6 in the beginning. Not doing so will give the following results:
a) When you try to click on the MPX Script Compiler setup section, the item will be highlightable,
but you can't enter the section. The mouse indication will go back to the previous highlighted
b) If you skip ahead and try to load the Jace, you'll get tons of dependency errors asking for the
other jar files.
5) To make sure the jar files are being seen in the entire system. Check a few locations
a) Go to Tools, then Module Info. You will see the 6 jar files with an exclamation point
on the shield. It will say, "This module is unsigned. Modules must be signed with a valid
trusted certificate in a future version. If you highlight the jar files, you'll be able to see
the entire list of dependencies for those files. Very Nice!!
b) Go to MyModules and make sure 3 modules show up here. Each module has an RT and WB
component to it, therefore the reason there will be only 3 instead of 6.
c) Go to SysHome and then SW to make sure the modules have been integrated into your
Workstation. You'll see 6 files in the folder "22.214.171.124.15
Back in AX, item "C" had a module initialization routine that would make it appear as an import. I was having
trouble getting the jar files to show up in the SW folder for this version of N4 until I created a new station local
to the computer and copied it over to the localhost using "Station Copier". Once that happened, the jar new files
showed up in the SW section as version 126.96.36.199.15. I know there was an easier way to initialize or import
a set of jar files to show up in this section without a bunch of messing around, but it alludes me at the moment.
Been awhile. If anyone knows an easier way to get the jar files to show up in the SW section, please reply.
6) When setting up the script compiler section, there will be some default entries already in the Ord paths.
Don't leave them that way. Manually re-create the paths. The initial path will essentially show the "C" drive
pathing to get to the location, but you really want the "UserHome" path to get to the MPX_Script section.
It's really the same location, but viewed differently in N4.
Ok, that's what I've found out at the moment. Time to go home for the day! If any R+D people find any
errors with what I put, please correct or shed some light where needed.
Thanks for the initial review of the install. Some of the things in the Quick Start Guide were written before things like AWS and OWS were available, (no Jace). This has been a very dynamic process with Tridium so the documentation may not have kept up. I fact, the first line of the Install section mentions "no Jace support". You are correct, installing all provided modules on the ES will streamline things for future Jace use.
Keep the comments coming. Even if we are aware of these issues/defects, it doesn't hurt to state them again.
@Jim_Okapal thank you for all your feedback and pointers.
Item 4: I will go in and update the quick start guide to reflect the recent change to add the 2 new modules (4 new JAR files.) As far as making sure the JACE has all the the required files, I create the new station, open the bog file and add the MPX BACnet Interface, saving the BOG and then transferring it to the JACE. This way all the required modules are automatically sent to JACE.
Item 5: I have had the best results with copping the 6 jar files directly into C:\niagara\niagara-188.8.131.52\modules and then restarting the Niagara service by running "Install Platform Deamon". Make sure you close Workbench, Install Platform Deamon and then restart Workbench.
Item 6: This is a defect that we will report back to Tridium. The default locations are supposed to be:
If anyone is having issues with this part please manually populate these fields under Tools -> Options -> MPX Script Compiler Options.
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!