Is this open source? Where to find on GitHub?

Yes, clearly: if I turn the machine off for 15 minutes and then turn it back on, the MH300’s product ID changes.
I have tested this—even without launching LCNC or running the EtherCAT XML command—and found that after the machine has been powered down for 10–15 minutes, it returns a different product ID. Although this ID is consistent each time it occurs, it differs from the one specified in the manufacturer’s XML file (which I used in our own XML file).
In practice, if the customer turns the machine on first thing in the morning—following an overnight shutdown—the machine fails to start; the MH300 remains in the "pre-op" state with a product ID of 10400000. However, if the customer then turns it off and back on again after 2 minutes—allowing enough time for the inverter’s capacitors to discharge—the machine starts up correctly, with the MH300 showing the product ID 104001F0 (the one found in the manufacturer’s [Delta] XML file).

Why can't I post screenshots here? 
So annoying.

This GUI is inspired by industry standard controllers and also probe_basic. Its goal is to provide a modern, graphically and feature rich GUI which is familiar to 
industry users and can be used in industry education, optimized for physical control with a CNC control panel and industry like custom CNC keyboard.

You can find it on GitHub:  Demo AppImage / Source code on GitHub

It is written from the ground up in Rust/egui and therefore starts up very quickly and has good performance even with syntax highlighting,
and context aware 3D display (highlight current line of code in the toolpath, loop iteration counter display, ...).

We just had our first release. It is now running on my machine and I start to find it useable now. Will be daily driving it while fixing issues.

Some features:

• G-Code syntax highlighting (works also with larger files)
• current G-Code line highlighted in the 3D view
• tooltable optionally integrates with loobric server ( github.com/loobric/ )
• automatically shuts down Internet / WIFI when a program is loaded or MDI to safeguard latency, brings it up again on program unload / MDI done
• Integrated G-Code help
• probe basic inspired probing
• Loop variable / Repeat identification and live monitoring (so you know where in the loop the program currently is)
• Support for lathe / canned cycles (currently only tested in the simulator)
• Integrated LinuxCNC log viewer and HAL browser
• mouse and touchscreen navigation also works where it makes sense, if available (3D view can do touch pan and pinch zoom), although not everything, lists can be touch scrolled. 
  

Main overview screen:


Program screen (note that the current selected G-Code line is highlighted):
 

Control panel simulation (this could be used on a touchscreen, although a physical panel is available and recommended):
 

MDI:
 

Probing:
 

Integrated interactive searchable offline G-Code help:
 

Integrated HAL browser:
 

Running on my machine:
 



  



 

I will use the -nobase option for the latency-test and capture a new latency-histogram - with all the network upates - I missed that option earlier
Re runnng- on Trixie first.

Sounds like you have a 7I85S rather than a 7I85.
What does the lot label on the back of the card say?

This is a test.

Hi everyone, I'm having a problem with my Mesa setup and hope someone can help me figure out what's going on. My setup consists of: - Mesa 7i96S- Mesa 7i85- Mesa 7i84 connected to the 7i85 via Smart Serial (sserial) The 7i84 works perfectly, but only on Smart Serial channel 4 of the 7i85. I've tried connecting the 7i84 to other channels and adjusted the HAL configuration accordingly, but it only works on channel 4. I recently wanted to connect another Smart Serial device using an additional cable, but I couldn't get it to work either. So I decided to take some measurements directly at the 7i85. Measurements with power OFF: - Channel 4: Resistance between RX and /RX is approximately 120 Ω.- All other channels: Resistance between RX and /RX is infinite (open circuit). Measurements with power ON: Channel 4: - RX to GND: 2.7 V- /RX to GND: 2.7 V All other channels: - RX to GND: 0 V- /RX to GND: 5 V These measurements seem quite different between the working channel 4 and all the other channels. My questions: 1. Is this behavior normal, or does it indicate a hardware problem with the 7i85?2. Has anyone experienced a similar issue with the Smart Serial channels on a Mesa 7i85?3. Could the missing 120 Ω resistance indicate a problem with the RS-422 termination or transceiver circuitry?4. Is there anything I can check or repair myself, or does the board need to be replaced? Any advice or suggestions would be greatly appreciated! Thanks in advance!

Good morning, everyone. I am encountering a rather strange issue involving an MH300 drive and a CMM-EC03 EtherCAT communication card.
To provide some context: we have configured the XML file so that the Delta MH300 operates in "free run" mode—essentially, we have removed the "dcsync" entry.
This same configuration—with only the PID changed—works perfectly on a Delta C2000 Plus drive.
The problem arises when I power on the machine after it has been turned off for 15 minutes or more: LCNC (LinuxCNC) detects the EtherCAT slave, but it remains in the "Pre-OP" (Pre-Operational) state.
If I then power cycle the drive—or the entire machine—and turn it back on immediately, the MH300 transitions to the "OP" (Operational) state.
However, if I turn the machine off again and wait 15 minutes, the issue recurs, and the MH300 remains in "Pre-OP."
The XML file for the MH300 specifies a `product_code` of `104001F0`, which matches the value in our XML file.
When the MH300 gets stuck in "Pre-OP," the EtherCAT diagnostic output shows a `product_code` of `10400000`; naturally, it remains in "Pre-OP" because this differs from the `104001F0` value defined in the XML file.
If I power cycle the drive or the machine immediately, the MH300 transitions to "OP," and the EtherCAT diagnostic output correctly reports the `product_code` as `104001F0`.
I do not believe the issue lies with the XML file or LCNC. I am unsure, however, whether the problem stems from the EtherCAT card (which is already running the latest firmware version) or the MH300 drive itself.
Is there a way to configure the XML file to bypass or ignore the PID check?

A brief description of the script would be helpful.
What does it do?
How does the process work?

Without a detailed description, I wouldn’t test the script—my servos are too valuable to me to risk it.

What is the latest development on the project?