Jump to content

Recommended Posts

People, over here at headquarters, we are curious.
As you know, we are now embedding our PLCs with technologies that enable them to support IIoT,  technologies such as  MQTT that are need for Industry 4.0 applications.

We want to know:

  • Do your current projects require IIoT support?
  • Are your clients expecting your  solutions to support Industry 4.0?
  • What features would you like to see in Unitronics controllers to help you with these projects?
  • Do you feel ready for this stage of technology--do you feel that you have the knowledge, the resources that you need?

Remember--your feedback helps us to set direction for R&D.

We would love to receive application stories involving MQTT :)

Share this post


Link to post
Share on other sites

Hi Paul,

The platform of those lines does not allow it. While we continue to support--as well as release new features--for these lines, these advanced features are supported by UniStream and the products that will follow it.

Share this post


Link to post
Share on other sites

Has Unitronics Partnered up with any   IOT  MQTT  cloud providers?  or recommend any MQTT  Broker programs for Internal Sites?

Dan Thomas

Share this post


Link to post
Share on other sites

Hello Dan,

Our MQTT client is basically generic.

We cannot recommend about specific broker. 

We tried here brokers such as RabbitMQ.

Share this post


Link to post
Share on other sites

I've been investigating a little bit more about MQTT with Azure and I'd like to share my findings with you.

The problem with the connection is the limit in the password field (128). Azure requires a SAS token for authentication that requires much more than 128 characters. The other option for authenticating to Azure IoT Hub (MQTT) is using a x.509 client certificate. That authentication option is neither supported by UniStream 5 MQTT implementation.

My question is: would be possible to extend the password field limit? I'm assuming that implementing client certificate authentication is much more complex.

Share this post


Link to post
Share on other sites

Hello,

Thanks for posting!

Starting from last version 1.24.56, the maximal length of the MQTT password had been extended to 255 characters.

Is that enough for your Azure broker? 

Quote

I'm assuming that implementing client certificate authentication is much more complex

You're right, but it is right now in process and this new feature will be available in next UniLogic version (very soon)

Hope it will help!

Rivka

Share this post


Link to post
Share on other sites
5 hours ago, Rivka said:

Hello,

Thanks for posting!

Starting from last version 1.24.56, the maximal length of the MQTT password had been extended to 255 characters.

Is that enough for your Azure broker? 

You're right, but it is right now in process and this new feature will be available in next UniLogic version (very soon)

Hope it will help!

Rivka

Hi Rivka,

Those are excelent news. The point with the password is that Microsoft uses a SAS token for authenticating the client. This token exceeds the 128 characters. In my case my token is 139 characters long, so I think that this new limit of 255 character for the MQTT password is more than enough.

Regarding the authentication using client certificates is also a real good news. It will add a good value for our projects.

Thanks for the update Rivka!!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×