-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
creating tool_db_utils #2654
creating tool_db_utils #2654
Conversation
I have a branch which integrates sqlite as a tooltable directly. It finally and once and for all solves all tooltable related issues properly. I will clean it up and create a PR. |
That would be awesome. Does it integrate the same way using the emc/tooldata code ? |
Do either of these use the tool database schema that I worked out with Tormach? |
My code does not use that, but it can. I used a simple test db to make sure the connections were working and loading tools. I see spindle hrs in the db, and one of my main motivations is to track individual tool usage time for tool life etc. It looks like that can be tracked per tool in this db ? |
… also adding in databse from Andy Pugh for testing
@andypugh I've re-written the code to incorporate the database you mentioned here: It works the same it did before, but now it loads tools from that database into LinuxCNC. Now other features can be added to start tracking things like tool life and spindle usage. Here's the relevant changes |
my code depends on this PR: #2497 |
I'll take a look. The code in this pull just interacts with the current system to load/unload tools and doesn't change anything internally. |
stuttgart meeting agrees this will be obsolete when @rene-dev is done with the sqlite tooltable. |
I've added a c program to the sim/axis/db_demo to pull in tools form the sqlite3 databse. it's mostly based on the python code in the db_demo. It's basic But a good start to get Linuxnc working with sqlite3 and might open the door to track things like tool life and other things.