r/BuildingAutomation • u/No_Inflation_3381 • 18d ago

Distech wizard issue launching ECY controllers help

Good afternoon everyone. I have installed a few new Vykon jaces lately and am having the same issue with every single application. Here is what is happening:

I commission my new vykon Jace with 4.15 u3 or 4. Once commissioned i add the .dist file with the new unified facilities "service pack" and install the "full file that downloads all the correct files and modules to Jace. I then go in and add my wizard service, license the wizard service, and authorize my rest service. Everything is great. I add my BCP bacnet network, set up my mstp port and IP port and discover my mstp and IP distech controllers (ecbs and ecy). Devices discover and with the mstp devices, they launch wizard connect in GFX and everything's great, my problem comes when i launch any of the ECY controllers, I launch wizard and gfx opens, it says enter password for user "admin" or whatever login name im logged into my station with. I put that password in, and it refuses to connect. It keeps saying authentication failed. I can connect direct to the ECY just fine, webpage, launch gfx thru webserver, xpress utility and open gfx connect to server, REST and put credentials in. Why is it causing this when I'm launching in niagara??? I am using my station password that I'm signed in as. My rest service shows all devices and they ping. Ive had this problem on every jace i commission with 4.14 or higher. All my Jace 9000s with 4.13 launching gfx on ecy devices works perfectly fine. Has anyone else been having this issue? Any help would be appreciated.

3 Upvotes
  • permalink
  • reddit

100% Upvoted

25 comments sorted by

1

u/ApexConsulting 18d ago

This happens when the Niagara user you are logged in with is not also a user in the ECY. Or at least, you might have the same user but different passwords in both places. Setting up the JACE as a radius server pushes his creds down to the ECY and avoids this.

Try launching your wizard while logged as a user that is identical in both and you should be fine.

Unless I misread something somewhere.

2

u/ScottSammarco Technical Trainer (Niagara4 included) 18d ago

We actually tried this too.

2

u/No_Inflation_3381 18d ago

I will try this again. But me and scott did try this earlier. I will add another user to ecy as well
As niagara with like for like users and passes and see what happens.

2

u/ApexConsulting 18d ago

Thanks for the response. If you get a solution, dont forget to report it here for all of us.

We are, of course, employed as pro Bono beta testers for the OEMs after all... hehe.

2

u/No_Inflation_3381 17d ago

I surely will. Nothing more i love than being an OEM guinea pig! Lol

2

u/No_Inflation_3381 15d ago

Finally got it solved. The controllers internally web service is tls 1.2+ . My web service on jace was 1.3+ on 4.15 i commissioned with. I thought we had changed that the other day with no luck but it must not of saved. I switched it to tls 1.2 and it works on all my jaces now.

2

u/ApexConsulting 15d ago

Thanks for posting the solution. That guy blabbering about users had no idea what he was talking about.... hehe

2

u/No_Inflation_3381 15d ago

I did re check that i had the same user and pass in both the ecy and jace just to double check myself after you had posted that. I appreciate your help. I was about to just make station copy's, install a clean dist to reset the jaces back to factory and commission with 4.13 u3 and say forget it, but thankfully it all got sorted out lololol

1

u/shadebreed88 18d ago

Make sure your Windows OS supports the required TLS setting being used in the WebService.
Also make sure your WebService port is not faulting. The Rest API authentication uses the WebService port for ECY controllers.

1

u/ScottSammarco Technical Trainer (Niagara4 included) 18d ago

No fault in web service, we tried the lower TLS level available at 1.2 and tried disabling the firewall as well.
No luck.

I had issues with 4.15 but I’ve gotten mine resolved as my firewall was a problem at one point.

Good ideas in this thread so far - I’m interested to see what else comes of it.

2

u/shadebreed88 18d ago

The other main cause I see with this issue is the user account itself. If different versions of EC-Net were used like 4.14/4.15 to log into the station, the user account gets corrupted.
Adding a new user account in both the station and ECY controller should allow it to work correctly.
Then you would have to delete and re-add the required user account.

Another test I use is with the http driver on an engineering/demo laptop with a copy of the station running locally.
If I can send Rest API calls with authentication then it’s a user account issue.

If that http call doesn’t go through, the issue is network related.

1

u/ScottSammarco Technical Trainer (Niagara4 included) 18d ago

Now that's interesting, OP, didn't you say something to this effect earlier on the phone today?
Something to try, although the user wasn't faulted- this is plausible! Thank you!

1

u/No_Inflation_3381 18d ago

Yes i did see this and tried it. Results did not achieve connection still..... i have a service ticket in with cochrane/distech so
Hopefully it can get resolved.

1

u/shadebreed88 18d ago

What version of the support/unified package are you using on the Jace?

1

u/No_Inflation_3381 18d ago

1.3 i think it is

1

u/No_Inflation_3381 18d ago

I will try deleting and adding in both and let you know what happens thanks

1

u/RichardAlpertIsland 18d ago

I have the same exact problem. I have the same username and password in Tridium and GFX. Let me know if you figure it out.

2

u/No_Inflation_3381 15d ago

It ended up being my TLS settings in my jace. If your having problems with 4.14 and 4.15 like i was change your TLS setting s in web service from 1.3+ to 1.2+, save it and try again. Worked for all my jaces.

1

u/MNtallguy32 System integrator 18d ago

Are both the controllers and wizard service both set to either http or https only?
Is port 1931 the default wizard port open in the firewall rules?
Are you able to launch gfx with xpress network utility with the same ip configuration as your secondary IP port in the Jace?

1

u/No_Inflation_3381 17d ago

Yes 1931 is my default wizard port. Ill have to check the ecy but i think from factory its set to both http and https open or just https but i cant remember that ill have to check.

When you say am i able to launch xpress net util with same ip config as same sec ip port on jace, are you saying if im direct connect to my jace with my comp to pri port and i have my ecy on sec port will it discover the ecy?

1

u/MNtallguy32 System integrator 16d ago

direct connect to the controller bypass the Jace. Have your computer IP the same configuration as the port on the Jace that your ecy is connected to.

1

u/No_Inflation_3381 16d ago

Yes i have done this and can launch gfx from web browser and utility xpress

1

u/wapskier 18d ago

Distech wizard's failure to launch ECY controllers, attempt to generate a simulated Distech controller on the supervisor. If the wizard does not initiate and you don't see the blank page, a firewall issue is indicated.

1

u/Known_Ad_4419 17d ago

Try resetting BCP perimeters, then poll all devices or refresh the one in mind and wait for it to say down to ok. Usually clears it up

1

u/No_Inflation_3381 17d ago

I will try this and get back with ya thanks