-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Share single CNC connection across multiple output types. #73
Comments
@MRIIOT, am I right to assume that this issue is about using a single FOCAS connection to a machine for every type of data gathered from that machine? I would be awesome and a huge performance gain if we currently use a connection per feature (or something along the lines). |
It is actually the other way around. We observed performance degradation when using multiple Focas connections. One to mqtt, one to Influx. So the suggestion is to output to mqtt and Influx from a single Focas connection. Even though the driver is async, I would imagine that the Focas connection blocks another somewhere. But this should be Wiresharked. |
@tukusejssirs, I don't think multiple connections to the same CNC will improve performance... From Focas docs:
|
It is also worth noting that using Fast Ethernet instead of Embedded Ethernet improves performance. |
Is that a config on the machine or something you need to implement in |
It is a physically separate network interface on the machine (if available). |
Allow output to SHDR and MQTT, for example, from a single CNC connection to avoid multiple Focas connections to CNC.
The text was updated successfully, but these errors were encountered: