Some random thoughts/discussion.
To be useful a stand-alone HAL package also needs tools for building HAL
networks.
These include halscope, halmeter, siggen, etc. as well as any future
insanely great visual HAL-netlist creation and visualization software.
Hardware-drivers should also be included i
On Jul 1 2013 10:30 PM, Alec Ari wrote:
> I've converted several non-git projects to git projects simply
> because of how easy it is... Is CVS impossible or is it just me?
CVS is old enough and lacking in features that most people move to at
least SVN, if not Mercurial of GIT. So, CVS is better
On Jul 1 2013 7:08 PM, Matt Shaver wrote:
> On Mon, 1 Jul 2013 22:09:21 +0200
> Michael Haberler wrote:
>
>>
>> Am 01.07.2013 um 16:20 schrieb EBo :
>
>> > hat raises a question though how deeply you want
>> > Python to get into LinuxCNC.
>>
>> No, it does not; a key/value pair-based API does not
>>"the way I envisage it to be is to be rather pythonic than c-ish,
namely using name/value pairs as arguments rather than say positional
arguments" <<
Whatever you want to achieve can be done in C / C++, dicts, hash tables,
dawgs etc.
There are C/C++ apis for all the databases too
Given that
On 2 July 2013 08:24, Anders Wallin wrote:
> These include halscope, halmeter, siggen, etc. as well as any future
> insanely great visual HAL-netlist creation and visualization software.
...
> There's a
> bunch of work on DAQ cards with linux at http://www.comedi.org/
Once you have Comedi suppor
I like python and find it easier to understand and write programs in and
hope more of LinuxCNC can use it. But I don't have a clue if that makes
any difference in the overall scope of things.
JT
On 7/2/2013 5:51 AM, Schooner wrote:
> >>"the way I envisage it to be is to be rather pythonic tha
On 2 July 2013 12:36, John Thornton wrote:
> I like python and find it easier to understand and write programs in
I find Python to be rather confusing, especially when it tries to out-think me.
(last night I discovered that it has a habit of adding a "self"
parameter to a function call, for examp
Do you have a git branch set up for this? I'd like to follow along with
the SQL and Python part, I've tried to learn C and C++ but don't get
very far.
JT
On 7/2/2013 6:42 AM, andy pugh wrote:
> On 2 July 2013 12:36, John Thornton wrote:
>> I like python and find it easier to understand and wri
On 2 July 2013 12:53, John Thornton wrote:
> Do you have a git branch set up for this?
Not yet. I want the code to be rather less obviously
baby-steps-in-python first.
There should be a new branch appearing in a week or two.
--
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/M
On Tue, Jul 2, 2013 at 7:26 AM, andy pugh wrote:
> Once you have Comedi support and a graphical net builder, you are very
> close to having an open-source LabView...
Hush your mouth.
Actually, it would be a useable alternative that isn't missing the zoom feature
On Tuesday 02 July 2013 08:03:14 John Thornton did opine:
> Do you have a git branch set up for this? I'd like to follow along with
> the SQL and Python part, I've tried to learn C and C++ but don't get
> very far.
>
> JT
C++ I never got the overall picture of John, but C itself I tend to look a
On 7/1/2013 9:19 PM, Matt Shaver wrote:
> On Mon, 1 Jul 2013 13:22:17 +0100
> andy pugh wrote:
>
>
>> On 1 July 2013 13:17, Stuart Stevenson wrote:
>>
>>
>>> Will the toolID be alphanumeric or any other symbology?
>>>
>> Yes :-)
>>
>> You would want to avoid employing:
>> http:/
I would also make sure that you can still use it with Classic Ladder as
a standalone also. That could be very useful.
Dave Cole
On 7/2/2013 3:24 AM, Anders Wallin wrote:
> Some random thoughts/discussion.
>
> To be useful a stand-alone HAL package also needs tools for building HAL
> networks.
Am 02.07.2013 um 03:08 schrieb Matt Shaver :
> On Mon, 1 Jul 2013 22:09:21 +0200
> Michael Haberler wrote:
>
>>
>> Am 01.07.2013 um 16:20 schrieb EBo :
>
>>> hat raises a question though how deeply you want
>>> Python to get into LinuxCNC.
>>
>> No, it does not; a key/value pair-based API do
good point. Where should the classic ladder be grouped? In its own
bin, with HAL, with a generic parser/PLC?
On Jul 2 2013 7:43 AM, Dave wrote:
> I would also make sure that you can still use it with Classic Ladder
> as
> a standalone also. That could be very useful.
>
> Dave Cole
>
> On 7/2
On 06/27/2013 09:22 AM, John Morris wrote:
> Seb, kick off a run when you get a minute. If you're updating an
> existing clone, be sure the git/linux/debian submodule is also updated
> for Wheezy fixes (I still don't quite understand git submodules).
I fetched the debian linuxcnc autobuilder and
Classic Ladder (as we use it) is basically a HAL application. It uses
HAL threads to evaluate the ladder rungs and HAL pins to connect
to I/O. Then there is a user-space part (the GUI) that builds the ladder
itself, in an independent shared memory block.
I guess I see HAL as a set of tools. Yo
On 07/02/2013 09:23 AM, Sebastian Kuzminsky wrote:
> On 06/27/2013 09:22 AM, John Morris wrote:
>> Seb, kick off a run when you get a minute. If you're updating an
>> existing clone, be sure the git/linux/debian submodule is also updated
>> for Wheezy fixes (I still don't quite understand git subm
I would think all code which refers to hal_lib.c but none of the say
interpreter/task code, and usable standalone without further package deps would
be a start at a guiding principle as to what goes where
this would suggest in the minimum:
- almost all comps, the comp tool proper
- scope, halsh
Am 02.07.2013 um 16:35 schrieb John Kasunich :
> Classic Ladder (as we use it) is basically a HAL application. It uses
(agree to all of above)
> I'm having a harder time wrapping my mind around Michael's
> larger messaging proposal(s). Non-scalar HAL types certainly
> have benefits for some
On 7/1/13 11:15 , Ian McMahon wrote:
>
> On Jul 1, 2013, at 11:45 AM, Matt Shaver wrote:
>
>> OK, I want to start making a "HOWTO Contribute To The Project" wiki
>> page. Linked to that page will be this page that's at least the
>> beginnings of what you want:
>> http://wiki.linuxcnc.org/cgi-bin/w
Am 02.07.2013 um 13:53 schrieb John Thornton :
> Do you have a git branch set up for this? I'd like to follow along with
> the SQL and Python part, I've tried to learn C and C++ but don't get
> very far.
I'll spin out a branch containing the protobuf support machinery plus zmq usage
examples,
> -Original Message-
> From: Sebastian Kuzminsky [mailto:s...@highlab.com]
> Sent: Tuesday, July 02, 2013 11:42 AM
>
> On 7/1/13 11:15 , Ian McMahon wrote:
> >
> > On Jul 1, 2013, at 11:45 AM, Matt Shaver
> wrote:
> >
> >> OK, I want to start making a "HOWTO Contribute To The Project"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/2/2013 10:42 AM, Sebastian Kuzminsky wrote:
>
> 1:
> http://buildbot.linuxcnc.org/doc/scratch/v2.5.2~contributor-docs-1~f892e30/html/code/Contributing-to-LinuxCNC.html
Looks
>
great! One thing I would add is in step 3 where you say "Push
your
On 7/1/13 08:44 , Matt Shaver wrote:
> On Tue, 25 Jun 2013 16:36:25 +0300
> "Alex Joni" wrote:
>> - we can do one-off's quite easily, just mail me or another wiki/web
>> admin with a link, and I can d/l it directly to where you want it
Alex, would you please add yourself as "Wiki Admin" on this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/2/2013 11:05 AM, Steve Stallings wrote:
> Thanks Seb, this is concrete progress. I would like for the
> current efforts at improvement of developer support and governance
> to be more visible. How do people feel about showing more current
> event
I've been tinkering with learning Python and converting my
C programs that generate G-code for the common operations
I perform to Python. I have the first one done, a program
to cut rectangular slots, called treprect, for trepan rectangle.
It makes one cut inside the final diameter and spirals dow
There are a bunch of them on the wiki...
JT
On 7/2/2013 12:27 PM, Jon Elson wrote:
> I've been tinkering with learning Python and converting my
> C programs that generate G-code for the common operations
> I perform to Python. I have the first one done, a program
> to cut rectangular slots, call
Thanks
On 7/2/2013 11:05 AM, Michael Haberler wrote:
> Am 02.07.2013 um 13:53 schrieb John Thornton :
>
>> Do you have a git branch set up for this? I'd like to follow along with
>> the SQL and Python part, I've tried to learn C and C++ but don't get
>> very far.
> I'll spin out a branch containin
On 07/02/2013 10:27 AM, Jon Elson wrote:
> I've been tinkering with learning Python and converting my
> C programs that generate G-code for the common operations
... snip
> Some others do a ramp-down version of treprect,
> step-down and ramp down versions of a round hole,
> a round pocket program,
So, two comments on the topic:
One, and this may be pretty minor, but when you use github and friends, it has
a nice big "this is the git url to clone" at the top of the page. Gitweb
doesn't, and it's not immediately obvious how to translate what's in gitweb to
a clone url.
Two, if I want to
And three, github and friends are relatively easy to deal with in terms of key
management and authentication. I think I gave Michael an ssh key once upon a
time for my access to his repo, but I don't really remember, and if so, which
key?
On Jul 2, 2013, at 2:20 PM, Ian McMahon wrote:
>
> S
I've use both git and mercurial for various projects (as well as svn,
and cvs). I prefer mercurial because it has a lower learning curve, and
can do everything that git can do with a little more work. Basically
the day to day things are simple, and the huge things like merging
repositories ta
I would have to disagree with the "...but in the maker community, being
open-source isn't a plus, it's more like a minimum barrier for entry."
I have never seen this at all. Where did you run into this? The only
people I have run into that had a problem with it wanted to sell
machines withou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am referring to the RepRap 3D printer crowd, as well as people
building things like the Lasersaur:
http://labs.nortd.com/lasersaur/
http://www.kickstarter.com/projects/nortd/lasersaur-open-source-laser-cutter-0
I do not mean "maker" as a general t
On Tue, Jul 02, 2013 at 02:20:41PM -0400, Ian McMahon wrote:
>
> One, and this may be pretty minor, but when you use github and
> friends, it has a nice big "this is the git url to clone" at the
> top of the page. Gitweb doesn't, and it's not immediately obvious
> how to translate what's in gitwe
Not sure lasersaur is a great example of "open" development, when their model
is "give us $32 and we'll give you our 'open' source"
On Jul 2, 2013, at 3:58 PM, Charles Steinkuehler
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I am referring to the RepRap 3D printer crowd, as
Beautiful!
On Jul 2, 2013, at 4:30 PM, Chris Radek wrote:
> On Tue, Jul 02, 2013 at 02:20:41PM -0400, Ian McMahon wrote:
>>
>> One, and this may be pretty minor, but when you use github and
>> friends, it has a nice big "this is the git url to clone" at the
>> top of the page. Gitweb doesn't
A lot of industrial "open" standards are like that.. Send us $495 and
we will give you the open standards/interface
specifications/protocol/sample source code, etc.
So "Open" does not necessarily mean free.
I wonder how they came up with $32 ? That seems like an odd amount.
Dave
On 7/2/201
On Tuesday 02 July 2013 19:55:44 Dave did opine:
> A lot of industrial "open" standards are like that.. Send us $495 and
> we will give you the open standards/interface
> specifications/protocol/sample source code, etc.
>
> So "Open" does not necessarily mean free.
>
> I wonder how they came u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/2/2013 6:56 PM, Gene Heskett wrote:
> On Tuesday 02 July 2013 19:55:44 Dave did opine:
>
>> A lot of industrial "open" standards are like that.. Send us
>> $495 and we will give you the open standards/interface
>> specifications/protocol/sampl
On 07/02/2013 09:46 AM, John Morris wrote:
> On 07/02/2013 09:23 AM, Sebastian Kuzminsky wrote:
>> I haven't started testing them yet, if anyone wants to take them for a
>> spin that would be useful.
>
> The r8168 driver is still missing. A lot of folks needed that last time
> we were testing.
42 matches
Mail list logo
