Personally I think that an interface and possible backing DB to tie gcode, tools, and machines together is a great idea but should definitely be separate from the tool table. It is an edge case and while many users make use of the tool table, including those that do not even have ATCs, there are far fewer that would have use for this higher level of automation. Including it in the tool table solution would cause, in my opinion, unnecessary complexity that will make maintaining the critical tool table code base that much more difficult.
I would also vote against using MySQL due to the need for a running server. SQLite does not require a service running in the background and is therefore much better suited for 'one machine' systems IMHO. The core code could likely be built so that the end user could decide which DB they want to use for backing this. I have seen this in other projects, but have not investigated what is necessary to support it. YMMV On 10/27/2016 12:10 PM, EBo wrote: > I would say that this is all doable, but I thought that tieing code to > fixtures was out of scope for the tool table (which I thought was the > scope of the discussion). That said, having the ability to scan a tool > and tracking it by barcode, RFID, imprinted magnetic strip/dots, would > be very useful in its own right. > > On Oct 27 2016 10:51 AM, John Thornton wrote: >> I'd like to see the database of G code get selected by reading a bar >> code on the part/fixture/etc. Read the bar code load the correct >> program >> and when some input says go run the program. >> >> JT >> >> On 10/27/2016 11:44 AM, Sarah Armstrong wrote: >>> i for one would like to see lcnc expanded to be able to use a >>> relational >>> database for a number of reasons >>> one for tooling and one for actual gcode, or combination of the two >>> , where >>> say a schema layout txt file would essentially be pointed to from >>> your ini >>> this could then relate a gcode database of working files , linked to >>> say a >>> photo of the finished product , and to say a particular tool pallet >>> for >>> that job >>> ok yes , i am taking this into the realms of production , rather >>> than a >>> hobbiest . >>> >>> But linking these could say hold a embedded serial of a tool pallet >>> , so if >>> the wrong pallet is loaded , the operator would know . >>> this could just about be ran by anyone , but then openly any >>> combination of >>> a workorder by a barcode reader , would or could setup the whole >>> machine >>> but having access to an open schema of a txt file or indeed even >>> part of >>> the database it's self could he held and read in . >>> >>> this would also link to the tool table and pallet required down to >>> the >>> gcode file by file name could be stored >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> On 27 October 2016 at 17:13, Dave Caroline >>> <dave.thearchiv...@gmail.com> >>> wrote: >>> >>>> This popped up in the user IRC today >>>> 3 tool stores and two spindles. https://www.youtube.com/watch? >>>> v=IxBiWPZmcZI >>>> >>>> Also I have been entering my gear cutters and hobs into a database >>>> for >>>> a while, I have not yet put all columns needed for for some of the >>>> workarounds I am thinking of >>>> >>>> http://www.archivist.info/cnc/tooldatabase/ >>>> I need total thickness and offset from one side to centreline, and >>>> width of kerf at the od (one can use the wrong cutter and get away >>>> with it for some jobs) >>>> >>>> also one may use a cutter offset to get a special form or correct >>>> for >>>> an asymetric cutter. >>>> >>>> data is in mysql >>>> Arbours need measuring too, then one can add the abour offset to >>>> cutter centreline offset. >>>> the tooling I use does not lend itself to the usual tool height >>>> probes >>>> see setup http://www.archivist.info/cnc/target.php >>>> the teeth can be a few thou wide, much smaller than most probe >>>> balls >>>> >>>> >>>> Dave Caroline >>>> >>>> ------------------------------------------------------------ >>>> ------------------ >>>> The Command Line: Reinvented for Modern Developers >>>> Did the resurgence of CLI tooling catch you by surprise? >>>> Reconnect with the command line and become more productive. >>>> Learn the new .NET and ASP.NET CLI. Get your free copy! >>>> http://sdm.link/telerik >>>> _______________________________________________ >>>> Emc-developers mailing list >>>> Emc-developers@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/emc-developers >>>> >>> >>> >> >> >> >> ------------------------------------------------------------------------------ >> The Command Line: Reinvented for Modern Developers >> Did the resurgence of CLI tooling catch you by surprise? >> Reconnect with the command line and become more productive. >> Learn the new .NET and ASP.NET CLI. Get your free copy! >> http://sdm.link/telerik >> _______________________________________________ >> Emc-developers mailing list >> Emc-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-developers > > > ------------------------------------------------------------------------------ > The Command Line: Reinvented for Modern Developers > Did the resurgence of CLI tooling catch you by surprise? > Reconnect with the command line and become more productive. > Learn the new .NET and ASP.NET CLI. Get your free copy! > http://sdm.link/telerik > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers >
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi
_______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
