Hello,
the hex unfortunately won’t help - if Estlcam cannot control the serial port to program the device it also won’t be able to use the port to control the machine later.
While the hex is no secret there is no static file as it is generated on the fly depending on configuration. The firmware itself is only a fraction of the data that needs to be programmed to the controller.
The question is if it is a permissions issue that Estcam simply isn’t allowed to connect to the port. This one should be relatively easy to solve (but I have no clue of Linux hardware permissions)
Or if the implementation of the bridge between “Windows COM” and “Linux TTY” is simpy broken or non existent. Estlcam uses the .NET “System.IO.Ports.GetPortNames()” function to get the list of available devices - whatever this reports can be selected - it is not limited to “COM…”
Christian