Manufacturing Connect FAQs

how can i try manufacturing connect? you can get started with manufacturing connect install / upgrade manufacturing connect docid\ yhwg58leb5hm4g507yeg0 read about manufacturing connect here access the manufacturing connect edge web ui docid 9y0 n74s8m5x4gynbfb9u manufacturing connect user ui docid\ smw1mexhytuxtggngo2tc can i use manufacturing connect without manufacturing connect edge? no, manufacturing connect is based on the model purchased from litmus manufacturing connect is the management suite for manufacturing connect edge why don't i see device attributes, such as manufacturer and model number, in the device info tab? these attributes are sent by the devices if it does not display check the device status from the edge devices pane to see if data is connected see activate an edge device docid\ jala8oa1dtk8bdvoenawa check the device information in the edge device see info docid 4rmhgrs0z5dnt69n jxit what could be some reasons that my device is not connecting? try double checking your connection parameters if the parameters are correct, check your firewall settings why can i see device data in the raw tab, but not in the explore tab? data sent to manufacturing connect must be in a special format, as shown in the json schema in the general settings page if manufacturing connect cannot parse incoming messages, the messages only appear in the raw tab how can i remotely manage a device? manufacturing connect offers the remote ui feature see open edge devices docid 4nmta3jptfgemui 1wuvp manufacturing connect supports mqtt protocol to remotely manage a device mqtt manufacturing connect supports 3 types of mqtt topics request to send manage requests to a device response to receive responses from a device data to receive data from a device request/response formats are not defined for example if you can program your device to reboot when it receives {"command" "reboot"} from the request topic, you can reboot your device remotely if you open the mqtt tab on the device details form, you can see request/response tabs to manage mqtt devices online to accomplish management tasks, you must program your device the batch device management feature offers operations similar to those described above, but you can define batch commands (mqtt) and schedule these commands to execute against a group of devices how can i visualize my data? use manufacturing connect edge all data that appears in the explore tab is available in manufacturing connect edge as well are messages sent from manufacturing connect edge to manufacturing connect secure? we do security testing with every release we prevent security issues through rest and mqtt protocols they only use secure transports, such as tls and dtls we do not support unencrypted transport between the two products all security credentials established during cloud activation are securely stored on the manufacturing connect edge device and not exposed to the end user it is impossible to alter these credentials after activation as long as physical security of the manufacturing connect edge gateway is maintained what is the difference between manufacturing connect alerts, events, and incidents? alert the manufacturing connect alerts feature allows users to define notifications based on rules rules comprise a set of conditions that define an abnormal state of a device for example no data received from a device in more than two minutes, or the temperature went below 30 degrees first, define actions actions are the types of notifications, such as slack or webhook then, create a trigger a trigger combines device tags, a set of rules, and an action once triggered, manufacturing connect sends the alert notification to the defined destination alert messages can be viewed on the manufacturing connect dashboard and from email and third party web applications, such as slack the incidents tab on the projects page lists the alerts that were generated event events list the manufacturing connect configuration activities that occurred for a project within a company for example added a new project, or deployed a new device incident if a device reaches an abnormal state according to the rules, manufacturing connect will create a new incident and send notifications the incidents tab lists the alerts that were generated when a device returns to a normal state, the open incident will be closed, and manufacturing connect will send another notification with a message about the incident being resolved how many manufacturing connect edge devices can manufacturing connect manage? the number of edge devices is not limited, provided you have allocated the appropriate resources the billing is based on tags in use what is the esxi version minimum requirement for manufacturing connect deployment? we strongly recommend esxi version 6 7 or higher what are the technical details i can verify before raising a support ticket? find out the following the version of the manufacturing connect edge and the manufacturing connect the version of a component if it is not working the type of license installed if the network is properly configured if the ntp/dns settings are correct if you are using the correct plc driver and ip address how long is alert history retained within manufacturing connect? alert history is not deleted it is kept as long as there is space in the database what happens if the database for alert history becomes full? after the alert history database becomes full, the system stops accepting data in upcoming releases, we will develop a more sophisticated data life cycle management do any security settings, such as active directory settings or certificate policies, get deployed when implementing a template on a manufacturing connect edge device from manufacturing connect? not at this time in upcoming releases, manufacturing connect will be able to deploy ldap/ad settings for various manufacturing connect edge devices can i deploy selected flows from a template to a selected manufacturing connect edge device from manufacturing connect? currently, a template consists of device configurations (settings and tags), analytics, flows, and connectors you can select a mix of both types and create as many templates as you want these templates can be uploaded from the manufacturing connect admin console or from the manufacturing connect you can create different groups of manufacturing connect edge devices and select which template you want to deploy to a selected group of devices in upcoming releases, we will include cc as well as a few other configurations what bi tools can be connected to manufacturing connect? manufacturing connect supports the mysql protocol for clickhouse if the bi tool supports mysql, it can connect to clickhouse some smart bi tools may use mysql system tables that are not present in clickhouse, so they should be tested manufacturing connect allows you to connect to the clickhouse underlying database see https //clickhouse tech/docs/en/interfaces/third party/integrations/ https //clickhouse tech/docs/en/interfaces/third party/integrations/ to find the native connectors that clickhouse uses why am i unable to activate an edge device? how do i fix this? when an activation fails, there will be an activation stage message that reports the exact cause(s) here are some potential fixes ensure port 443 is opened ensure 51820/udp is open for the manufacturing connect edge instance ensure the remote access protocol is not blocked at all ensure the time synchronization setting between the manufacturing connect and manufacturing connect edge is working properly for docker run manufacturing connect edge instances, check for netadm capability if i delete or deactivate a manufacturing connect edge instance in manufacturing connect, will its service account (sa) key also be deleted? yes, deleting or deactivating a manufacturing connect edge instance does remove the services account that was created during manufacturing connect edge activation how can i find which sa key belongs to a specific manufacturing connect edge instance? you can check under general settings > pubsub settings in manufacturing connect this shows a list of manufacturing connect edge instances using pubsub the service account name looks like edge \<mc device id>@project the first five characters of the device id appear in the ui, but the link contains the full id after deleting a manufacturing connect edge instance, does manufacturing connect automatically remove unused service accounts? no, manufacturing connect does not delete service accounts automatically however, some users have noticed fewer unused accounts after cleanup it’s a good idea to remove unused accounts, especially in test/demo environments, since google cloud limits the number of service accounts to 100 per project what if i need more service accounts for pubsub integration? you can request a limit increase from google cloud support another option is the workload identity federation (wif) , which removes the limit on the number of pub/sub connectors and allows secure access without needing many service accounts this is because with wif, pub/sub connector service accounts and their keys are not created at all, simplifying the management of authentication and access