Whao, I didn't know there are tools like gschem or eagle libs for lcnc.
I moved from eagle to KiCad a long time ago, gschem I used just to try it for evaluation, also a long time ago, so I don't really know about the actual features of this two programs. I hope I understand well Nicklas' challenge with thread symbols. KiCad has a feature that may give an idea. KiCad has sort of global net-name symbol and links all of them together if they have the same name. So let's say I've a schematic divided in several sub-sheets and an I2C bus in it. I use two global net symbols, name them I2C_SDA and I2C_SCL, then I can connect those Global Symbols in every sub-sheet to the related pins, the netlist generator links together what has the same global name. So a thread symbol just needs one pin, like Nicklas says. Linking that pin to a global net symbol makes that pin available in any sub-sheet in the schematic. Ju ________________________________ From: [email protected] <[email protected]> Sent: Monday, July 4, 2016 12:34 AM To: [email protected] Subject: Emc-developers Digest, Vol 123, Issue 3 Send Emc-developers mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/emc-developers or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Emc-developers digest..." Today's Topics: 1. Re: Got a bug I think, and its smashed $25 worth of tools today (Sebastian Kuzminsky) 2. Re: Got a bug I think, and its smashed $25 worth of tools today (Gene Heskett) 3. gschem --> *.hal (Nicklas Karlsson) 4. Gschem library (Nicklas Karlsson) 5. Re: gschem --> *.hal (TJoseph Powderly) 6. Re: gschem --> *.hal (Nicklas Karlsson) ---------------------------------------------------------------------- Message: 1 Date: Fri, 1 Jul 2016 18:05:08 -0600 From: Sebastian Kuzminsky <[email protected]> Subject: Re: [Emc-developers] Got a bug I think, and its smashed $25 worth of tools today To: EMC developers <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=windows-1252; format=flowed On 07/01/2016 02:40 PM, Gene Heskett wrote: > Got it, its working, many thanks Sebastian. I owe you some hand coolers > if we ever get in the same county. :) I'm glad it's working for you. Sorry the bug wrecked your stuff though, hopefully that won't happen again :-/ > Thanks again. FWIW, the previous version did ask me for permission to > upgrade my configs, I said yes of course, but I haven't looked to see > what it did as the motion after stop was, ANAICT, the only problem. So > that script appears to have done whatever it needs to flawlessly. So > thanks to whoever wrote that script are due too. That was Andy Pugh, and yes huge props due. -- Sebastian Kuzminsky ------------------------------ Message: 2 Date: Fri, 1 Jul 2016 22:25:24 -0400 From: Gene Heskett <[email protected]> Subject: Re: [Emc-developers] Got a bug I think, and its smashed $25 worth of tools today To: [email protected] Message-ID: <[email protected]> Content-Type: Text/Plain; charset="iso-8859-1" On Friday 01 July 2016 20:05:08 Sebastian Kuzminsky wrote: > On 07/01/2016 02:40 PM, Gene Heskett wrote: > > Got it, its working, many thanks Sebastian. I owe you some hand > > coolers if we ever get in the same county. :) > > I'm glad it's working for you. Sorry the bug wrecked your stuff > though, hopefully that won't happen again :-/ Thats is precisely why I run the "bleeding edge". I am not making a living at this where time and efficient tool usage is a given so that the shop can compete with the next guy two blocks down the street. I CAN afford to blow up a tool occasionally as long as it doesn't kill the bank. 2 in a row from the same miss-cue, and I _will_ tell you about it. :) OTOH, those 2, 1/8" SC mills, are my down payment/contribution for all the verbosity you folks put up with from me. ;-) >> So thanks to whoever wrote that script are due too. > > That was Andy Pugh, and yes huge props due. Thanks again Andy, and a big tip of a brown almost 5 gallon Woolrich hat that Woolrich no longer sells in your direction again. And a hand cooler or three if we're ever in the same county. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------ Message: 3 Date: Sun, 3 Jul 2016 18:12:05 +0200 From: Nicklas Karlsson <[email protected]> Subject: [Emc-developers] gschem --> *.hal To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=US-ASCII As I am also a gschem user and have started to move away from the lower level drivers I have started to think about a gschem to *.hal file converter. Basically it would be a netlist backend generating the hal file. If I remember correct the idea is not new? Nicklas Karlsson ------------------------------ Message: 4 Date: Sun, 3 Jul 2016 22:59:30 +0200 From: Nicklas Karlsson <[email protected]> Subject: [Emc-developers] Gschem library To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=US-ASCII I found the linuxcnc gschem library and are thinking about adding a back end for gschem. There already is a backend in python although other backends for gschem is written i scheme. The first thing I noticed is library pin symbol pintype is not good enough, there is only in and out. There is a need for what is usual a type in a programming language like float, integer or similar. In ordinary schematics there are concepts like driven low but not high for open collector and similar. I think it pintypes like "in.float", "out.float", "in.bit", ... would be suitable. Second thing I noticed is threads are represented by an n pin symbol, I think a one pin symbol would be enough, there would be one "net" for each thread possible with many called functions. Nicklas Karlsson ------------------------------ Message: 5 Date: Mon, 4 Jul 2016 11:18:08 +0700 From: TJoseph Powderly <[email protected]> Subject: Re: [Emc-developers] gschem --> *.hal To: EMC developers <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=windows-1252; format=flowed Hi Nicklas, http://wiki.linuxcnc.org/cgi-bin/wiki.pl?HalSchematicsUsingGschem I wrote that stuff i found the scaling and idea of threads to be a limitation scaling as in scope,meaning, when you can see the pin, you cant see the overall so i used sheets ( like meta widgets ) to contain ideas inside the schema but eventually reduced my expectations to simply display the idea of the .hal not to make it forward/backward interpretable by linuxcnc also look at the http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Eagle2HAL and more exciting, google Rockhopper Linuxcnc i still play with the idea and watch for netlist visualization I recently played a bit with VUE from Carnegie Mellon HTH TomP tjtr33 On 07/03/16 23:12, Nicklas Karlsson wrote: > As I am also a gschem user and have started to move away from the lower level > drivers I have started to think about a gschem to *.hal file converter. > Basically it would be a netlist backend generating the hal file. > > If I remember correct the idea is not new? > > Nicklas Karlsson > > ------------------------------------------------------------------------------ > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > present their vision of the future. This family event has something for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------ Message: 6 Date: Mon, 4 Jul 2016 06:34:17 +0200 From: Nicklas Karlsson <[email protected]> Subject: Re: [Emc-developers] gschem --> *.hal To: EMC developers <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=US-ASCII Netlist generator for *.hal "netlists" would be rather simple in gschem so I stick with gschem. I think of the thread symbol as a clock signal clocking the functions and one thread could drive several functions. This thread signal is however not a data path so it might be better to have a thread attribute for functions. To get a visuable good looking schematic I think the hieriachical function will be useful. Some values are set as constants and it would in particular be useful to hide these on a lower level. On Mon, 4 Jul 2016 11:18:08 +0700 TJoseph Powderly <[email protected]> wrote: > Hi Nicklas, > http://wiki.linuxcnc.org/cgi-bin/wiki.pl?HalSchematicsUsingGschem > I wrote that stuff > i found the scaling and idea of threads to be a limitation > scaling as in scope,meaning, when you can see the pin, you cant see the > overall > so i used sheets ( like meta widgets ) to contain ideas inside the schema > but eventually reduced my expectations to simply display the idea of the > .hal > not to make it forward/backward interpretable by linuxcnc > also look at the > http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Eagle2HAL > and more exciting, google Rockhopper Linuxcnc > i still play with the idea and watch for netlist visualization > I recently played a bit with VUE from Carnegie Mellon > HTH > TomP > tjtr33 > > On 07/03/16 23:12, Nicklas Karlsson wrote: > > As I am also a gschem user and have started to move away from the lower > > level drivers I have started to think about a gschem to *.hal file > > converter. Basically it would be a netlist backend generating the hal file. > > > > If I remember correct the idea is not new? > > > > Nicklas Karlsson > > > > ------------------------------------------------------------------------------ > > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > > present their vision of the future. This family event has something for > > everyone, including kids. Get more information and register today. > > http://sdm.link/attshape > > _______________________________________________ > > Emc-developers mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/emc-developers > > > ------------------------------------------------------------------------------ > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > present their vision of the future. This family event has something for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------ ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape ------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers End of Emc-developers Digest, Vol 123, Issue 3 ********************************************** ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
