I agree about the complexity part. The one issue that does make sense to keeping it in a data store is that if someone moves the g-code to clean up the dirs, then everything breaks. Other than that I think a full on relational database would be more problems than it is worth. I will not mind being proven wrong on this, but this will be a "show me" issue. I'm just waiting at this point to see people prototype something so we can look at it.
On Oct 27 2016 11:06 AM, James Waples wrote: > What's wrong with a filesystem for gcode? There's already a pretty > good > implementation distributed with the OS that LinuxCNC runs on ;). > Additionally, having an SQLite DB of gcode programs is overly complex > and > makes getting gcode onto my control over a network share impossible. > There > will likely be a lot of similar setups out there so gcode in a > database is > not the way to go. > > As for tool libraries, it seems to be the increasingly common > opinion, so I > should probably shut up about JSON. > > On Thu, 27 Oct 2016 at 17:54 John Thornton <j...@gnipsel.com> 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 ------------------------------------------------------------------------------ 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
