Promecor Lathe retrofit with TKXHMI

Some of it as it diverged a lot, for example Python thing is not well supported (the new interface is C++ with Qt made)
File saving settings is removed, everything is database managed and updated as it runs, not at linuxcnc closing so in case of power outage, values remains.
Python preview is completely broken as I made a “simulation” preview so it does not get affected by endless loops as current Python preview works
All of these makes pretty hard to pull changes without braking users machines

My idea is to open a fork or something in the near future for lcnc modified codebase

Regards
Franco!

Hi Andy,
My first shot was using tooldb but then I realized that it was not what I really wanted, it is more a patch than a solution. I integrated zeromq with protobuf for messaging so I don’t only send tool information but also work offsets , variables and even settings stored on the db, no need to use file for saving stuff. The advance of this is that it is saved as soon as data changed and not only at powering off.

Sure, I can pull request line showing

About homing, I added a “drive based homing” setting on the ini to let the system it should just use the drive homing and wait for completeness. No need to use the new homing thing

Regards
Franco

Sure, I can pull request line showing

Does this also apply to subroutines in different files?

Yes my friend, just gcode subroutines and remaps , Python remaps shows line that called them

Would be really nice if you could PR that. It seems that involves changes all over the board to add the filename wherever line_number is changed.

You are absolutely right but I have done it better as you would have to hold the file name on real-time and it’s a no no . What I have done is creating a list where every time a file is loaded just append it to a list and get the index into real-time so now you have file number and line number

Hey, lookin good. your cnc controller panel, is that a retrofit or did you buy one of those fany panel mount keyboards? was it expensive? I want one but they are so damn expensive......

Also, when you say HMI, you mean in the literal sense? is your screen just a normal HDMI/DVI/VGA monitor? not an industrial PLC HMI?

Yea, this.  Do want, can't justify.

@fsabbatini


There are clearly a bunch of folks here slobbering over your screenset and back-stage improvements.

I've got an older Emco 325-II live-tool C-axis lathe running the PC-based fake "Fanuc" control.  It mostly works, but I expect some proprietary component to die if I blink and Emco is useless with older control support.

The single-block improvement you've demonstrated alone is worth me buying components to set up a bench-testing rig just to have something ready when the Emco dies.

What do you need from this community to publish this masterpiece and give a little aid the slower-witted of us in setting something up like this?

Money? Booze? Applause?

Hey cakeslob, you are right, they are expensive, it cost around 180usd but it is made from stainless stell with high IP, usable in the dirtiest environment. I have been using logitech keyboards and they last as long as a fart in a cage in heavy dirty environment..
when i say HMI is the part of software you interact with. Eveything is running on an industrial panel pc (the motherboards connects to the screen through LVDS signals internally), nice and neat.