From: Petter Reinholdtsen Date: Sun, 8 Jan 2023 18:29:25 +0000 (+0100) Subject: Adjust language. X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/a7b8bc18dfeea313e851be3568debb64597e1d69 Adjust language. --- diff --git a/blog/data/2023-01-08-linuxcnc-mqtt.txt b/blog/data/2023-01-08-linuxcnc-mqtt.txt index 6d6c619c89..7e3babb589 100644 --- a/blog/data/2023-01-08-linuxcnc-mqtt.txt +++ b/blog/data/2023-01-08-linuxcnc-mqtt.txt @@ -9,19 +9,20 @@ information to the MQTT broker IBM Bluemix. As I also use MQTT for graphing, it occured to me that a generic MQTT LinuxCNC component would be useful and I set out to implement it. Today I got the first draft limping along and submitted as -a patch to the +a patch to the LinuxCNC project.

The simple part was setting up the MQTT publishing code in Python. I already have set up other parts submitting data to my Mosquito MQTT broker, so I could reuse that code. Writing a LinuxCNC component in Python as new to me, but using existing examples in the code -repository, this was fairly straight forward. The hardest part was -creating a automated test for the component to ensure it was working. -Testing it in a simulated LinuxCNC machine proved very useful, as I -discovered features I needed that I had not thought of yet, and -adjusted the code quite a bit to make it easier to test without a -operational MQTT broker available.

+repository and the extensive documentation, this was fairly straight +forward. The hardest part was creating a automated test for the +component to ensure it was working. Testing it in a simulated +LinuxCNC machine proved very useful, as I discovered features I needed +that I had not thought of yet, and adjusted the code quite a bit to +make it easier to test without a operational MQTT broker +available.

The draft is ready and working, but I am unsure which LinuxCNC HAL pins I should collect and publish by default (in other words, the