Welcome to the overview of software releases for the EOSCONNECT products.
For more information on the new features please check the respective release below. For the Release Notes with many more details please visit myEOS.
New datapoints for more insights in the machine status where added:
You can now streamline your data model even further by using the new information which has been made available for each data point on the Web Api:
We made all available data points available in an Excel sheet along with the following information:
We have added MQTT as the third type of interface besides OPC UA and Web API. An external MQTT broker needs to be set-up by customers wanting to utilize MQTT.
EOSTATE MeltPool and EOSTATE Exposure OT images, indications and part statistics can now be obtained via the EOSCONNECT Core Web API. With this data available you can start building own analytics or automate the generation of part documentation. The new endpoints are available in the “jobs” and “layers” group. If you are a member of the EOS Developer Network you can use a virtual EOS system via the EDN Portal to try out this new functionality.
Measure the availability of your EOS systems by using the new status endpoints and optimize their utilization by using the new control functions. Automation functions allow you to further streamline your AM production in combination with your 3rd party periphery.
We have added capabilities to remotely control the machine in alignment with health and safety requirements. It is now possible to send the following commands via the OPC UA interface:
Optimize the laser-on-time of your EOS systems by integrating seamlessly with 3rd Party periphery. There are new control endpoints supporting this:
The status of a machine can now be tracked in a fine granular way. On the EOSYSTEM user interface an operator can select the status. The status is accessed via Web API or OPC UA and it can be used to track the utilization of a system over time.
The tool to troubleshoot problems with EOSCONNECT Core was introduced with Edition 11.20. We enhanced it to check for a valid license and certificate.
We further improved security of our APIs. The message security mode Basic256 of OPC is due to security issues no longer supported. Instead we provide the following: None, Basic256Sha256, Aes128Sha256RsaOaep, AES256Sha256RsaPss.
Several new datapoints are available on the Web API allowing even more insights on process critical parameters. They include:
We are taking first steps in adding control functionality to EOSCONNECT Core. The running job can now be paused and resumed via OPC UA interface. This is function is currently only available for EOS Apps like EOSCONNECT MachinePark. It will be made available for public use in a future version of EOSCONNECT Core.
The EOS M 300-4 and EOS P 500 are now also supported by EOSCONNECT Core.
Images from EOSTATE PowderBed Imaging can now be retrieved via the Web API. Image acquisition can be automated. This enables you to improve traceability of the process or allows you to build your own image based data analytics
Improved security – Users can configure a password for data access via the EOSCONNECT interfaces. These apply to access via OPC UA as well as the Web API. This ensures that only approved individuals or software services get access to machine data.
EOSCONNECT Core works exclusively with EOSYSTEM Edition 10.18. EOSCONNECT Core runs on the machine IPC as a separate service. The software is installed along with EOSYSTEM. No additional installation required.
The EOS M 290, EOS M 400 and EOS M 400-4 are supported by EOSCONNECT Core.
The documentation of the UPC UA interface as well as the Web API can be viewed via a web browser connection to the machine PC. Always have the correct version of the documentation fitting the version of the API.
Live data, like sensor and status data can be retrieved via OPC UA interface. Machine events can be retrieved via the OPC UA interface. Integrate with e.g. with MES systems to monitor the live statius of machines. Settling on the industry standard reduces the time for integration projects.
Historical data can be read from the machine via the Web API. Quality data of the machine can be read out via the Web API. The Web API relies on the widely accepted REST principle. It is easy to use by developers.
The Web API is protected via SSL to ensure secure access to the machine data. The software is shipped with a self-signed certificate which can be replaced by a customer certificate.
With EOSCONNECT MachinePark you can monitor your entire EOS shop floor from anywhere in just one app. No more Excel lists and walking long distances, system information is now easily accessible to your team to receive automatic notifications about machine status and print jobs.
We have improved our rights management. It is now possible to show or hide specific machines to specific users of certain roles.
You can assign tags to machines like “M 4-4” or “Metal” and use them in a filter to only show specific machines.
There is an API to inject timeseries data to the EOS Hub database from external data sources or own analytics. The UI of EOSCONNECT MachinePark can then be used to visualize this data in the sensors/graphs section of a machine. Thresholds can be configured and notifications can be set up for the external data, just as for internal data.