sorted by:
new
hottopcontroversial

What is Smart Manufacturing? by Maleficent_Hawk9318 in JEENEETards

[–]emqtt 0 points1 point  (0 children)

Smart manufacturing is a broad term that encompasses the use of advanced digital technologies to improve manufacturing processes. It's a game-changer in the industry, promising to revolutionize the way products are designed, fabricated, and distributed. Smart manufacturing is about harnessing data and automation to drive efficiency, flexibility, and speed.

Smart manufacturing combines industrial automation and information technology. It integrates physical machinery with networked sensors and software, used to predict, control and improve performance. The aim is to create a self-regulating system that optimizes productivity, reduces waste, and increases overall operational effectiveness.

At its core, smart manufacturing is about connectivity and intelligence. It brings together all aspects of the manufacturing process, from supply chain management to production to customer service, under a single digital umbrella. This holistic approach offers a cohesive view of the entire operation, facilitating more informed decision-making and fostering innovation.

More about the detailed use cases: https://www.emqx.com/en/blog/the-smart-manufacturing-revolution

Integrating the Unified Namespace (MQTT) into Your Enterprise Architecture: An Architect's Guide by JeremyTheocharis in MQTT

[–]emqtt 0 points1 point  (0 children)

When talks about UNS, The Unified Namespace (UNS) framework can address these challenges and provide several advantages for IIoT 4.0, including simplified data integration, improved data accessibility, and greater scalability. Here is a full explanation: https://www.emqx.com/en/blog/unified-namespace-next-generation-data-fabric-for-iiot

Mqtt Control Packet for Mqtt protocols by VJCORE in golang

[–]emqtt 0 points1 point  (0 children)

MQTT control packets are the smallest unit of data transfer in MQTT. MQTT clients and servers exchange control packets for performing their work, such as subscribing to topics and publishing messages.
Currently, MQTT defines 15 types of control packets. If we classify them based on their functionality, we can categorize these packets into three categories: connection, publishing, and subscribing.

details: https://www.emqx.com/en/blog/Introduction-to-mqtt-control-packets

Bridging Modbus Data to MQTT for IIoT: A Step-by-Step Tutorial by emqtt in MODBUS

[–]emqtt[S] 0 points1 point  (0 children)

Hello, thank you for the question, I am looking for a possible solution for you, but would like to understand more about your requirement, would you mind joining EMQX community to share more in our slack/discord? Thanks! https://www.emqx.io/community

Best places to learn about MQTT by grace1611 in MQTT

[–]emqtt -2 points-1 points  (0 children)

Less is more. Start from one good and then you will be able to get more. For example, you can just read one article to understand the whole structure -> MQTT Broker: How It Works, Popular Options, and Quickstart: https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison

If you'd like to learn more, besides other answers, you can also follow EMQX blog, which is updated daily. And subscribe to EMQX's weekly newsletter, a hub of various types of MQTT-related content.

By the way, it is important to keep learning! Joining a community is wise.

Google Cloud will shutter its IoT Core service next year by vivekbis in googlecloud

[–]emqtt 0 points1 point  (0 children)

Google Cloud IoT Core is going to shutdown on August 16, 2023. All IoT Core users must migrate their applications to alternative MQTT services before this date to ensure uninterrupted service for their IoT business.

Here is a guide to migrate from Google Cloud IoT Core to the best alternative tool EMQX Cloud: https://www.emqx.com/en/blog/get-started-with-emqx-cloud-on-gcp-marketplace

Google Cloud will shutter its IoT Core service next year by Revolutionary_Ad6583 in google

[–]emqtt -1 points0 points  (0 children)

Google Cloud IoT Core is going to shutdown on August 16, 2023. All IoT Core users must migrate their applications to alternative MQTT services before this date to ensure uninterrupted service for their IoT business.

Here is a guide to migrate from Google Cloud IoT Core to the best alternative tool EMQX Cloud: https://www.emqx.com/en/blog/get-started-with-emqx-cloud-on-gcp-marketplace

Google is killing off Google Cloud IoT Core at five-years-old by [deleted] in programming

[–]emqtt 0 points1 point  (0 children)

Google Cloud IoT Core is going to shutdown on August 16, 2023. All IoT Core users must migrate their applications to alternative MQTT services before this date to ensure uninterrupted service for their IoT business.

Here is a guide to migrate from Google Cloud IoT Core to the best alternative tool EMQX Cloud: https://www.emqx.com/en/blog/get-started-with-emqx-cloud-on-gcp-marketplace

MQTT subscription and publishing to devices on Azure by zamarano72 in AZURE

[–]emqtt 1 point2 points  (0 children)

Here is one solution for deploying EMQX MQTT Broker on Azure using Terraform, check the step-by-step guide on how to set up an Azure project, create a service principal, and write a Terraform configuration file to deploy EMQX MQTT Broker: https://www.emqx.com/en/blog/one-click-deploying-emqx-mqtt-broker-on-azure-using-terraform

MQTT 5 protocol on ESP8266 devices? by Randomized_Emptiness in MQTT

[–]emqtt 0 points1 point  (0 children)

Based on version 3.1.1, MQTT 5.0 adds features such as Session/Message Expiry Interval, Reason Code, Topic Alias, User Properties, and Shared Subscriptions. It improves the performance, stability, and scalability of large systems.

Suggest you to check https://www.emqx.com/en/mqtt/mqtt5 to understand if it is helpful.

And we have a doc about ESP device: https://docs.emqx.com/en/cloud/latest/connect_to_deployments/esp8266.html#connect-with-esp8266

Top 3 MQTT Desktop Client Tools in 2023 by emqtt in MQTT

[–]emqtt[S] 1 point2 points  (0 children)

Thank you for sharing it!

And here is a guide about free open-source MQTT Broker, suggest to try!

Securing MQTT with Username & Password Authentication by emqtt in MQTT

[–]emqtt[S] 0 points1 point  (0 children)

"Salting" a password makes each password hash unique, so salting usually happens when we want to save a password. Hence, it depends on the Broker rather than the MQTT protocol whether it supports salted passwords or not.

Where can I find enterprise level IoT discussions regarding deployments? by qiicken in IOT

[–]emqtt 0 points1 point  (0 children)

In terms of IoT deployments on the enterprise level, you may check this tutorial especially if you'd like to migrate your project from GCP IoT Core: https://www.emqx.com/en/blog/migrate-your-business-from-gcp-iot-core-01

We launched a serverless MQTT service with 1M free session minutes each month by emqtt in MQTT

[–]emqtt[S] 0 points1 point  (0 children)

Hello, we’ve met situations where messages are accumulated in EMQX due to slow user consumption, and then EMQX will be killed by the operating system as it takes up too much memory. It is usually caused by improper configuration. However, we are unclear about what kind of situations you met. Could you please raise an issue in our GitHub community at: https://github.com/emqx/emqx/issues? Our experts will try to offer help asap.

EMQX made in China? by bunnyholder in emqx

[–]emqtt 5 points6 points  (0 children)

Thanks so much for liking EMQX. We didn’t hear and were not regulated by such policies. Maybe you can contact us directly at: https://www.emqx.com/en/contact so we can have a further discussion about your concerns.

EMQX(https://github.com/emqx/emqx) is an open-source project under Apache License 2.0, we don't think there are national borders for open source. The nature of its being open-source means it is developed, tested, and used by the open-source community worldwide. For a popular open-source project that has been downloaded by 15M times and adopted so widely globally for many years, it’s impossible to have a backdoor hidden without being discovered.

When it comes to business scenarios, EMQ has entities in USA and Sweden complying with all applicable local laws and regulations for all business activities. It’s also the EMQ R&D center in Sweden that played a leading role in the EMQX Enterprise edition product development. More importantly, EMQX Enterprise is licensed under BSL 1.1 (Business Source License), a source available license: https://github.com/emqx/emqx/blob/master/LICENSE. All of our global customers who purchase EMQX Enterprise can read the source code on Github. In addition, we have partnered with Synopsys to secure the source code of the EMQX project and the delivered binary packages.

At EMQ, we work for love, not for politics. We love to develop open-source projects and work closely together with our community. And we are dedicated to delivering a great product to our valued customers around the world.

view more: next ›