Actually I can think of a much simpler solution which is doable right now
(multiple LinuxCNC2 instances) with a Python HAL user component.
The difference to what I laid out in my previous mail is: synchronisation is
achieved at the HAL pin level, not at the 'precondition for issuing a message'
Hi
If the Raspberry is to difficult to run as a CNC controller, maybe it
would be suited as the basis of a pendant?
Regards
Darren Conway
On 10/09/2012 9:35 a.m., Jon Elson wrote:
> Kent A. Reed wrote:
>> On 9/9/2012 1:54 PM, Jon Elson wrote:
>>
>>> <...> I have not reported any thread late
Thnks for your input EBo!
Part of the project is promised to take shape this week.
That means it's in the nuts&bolt-phase, at least partially.
The GUI is prioritized and Glade is suggested to be used.
Pythons TCP-inteface is also in the pipe.
Tried this yesterday:
Am 10.09.2012 um 04:56 schrieb EBo:
> On Sat, 8 Sep 2012 14:10:27 +0200, Michael Haberler wrote:
>> Am 08.09.2012 um 12:46 schrieb Dave Caroline:
>>
>>> While people are dreaming of new things for a version 3
>>> I thought I would throw in a few items.
>>> I was staring at the sliding head think
Which reminds me of Citizens recent sliding head machines
they have two spindles opposite each other
front spindle will have all its operations done then the rear spindle
moves to hold the item
while it is parted off, during this time the two spindles are synchronised.
after parting the rear spind
> Date: Thu, 6 Sep 2012 07:54:55 +0200
> From: philippe.fross...@free.fr
> To: emc-developers@lists.sourceforge.net
> Subject: Re: [Emc-developers] Shutting down after a while ...
>
> Le 05/09/2012 13:10, andy pugh a écrit :
> > On 22 August 2012 09:04, Philippe Frossard
> > wrote:
> >
> >> c
On Sat, 8 Sep 2012 14:10:27 +0200, Michael Haberler wrote:
> Am 08.09.2012 um 12:46 schrieb Dave Caroline:
>
>> While people are dreaming of new things for a version 3
>> I thought I would throw in a few items.
>> I was staring at the sliding head thinking of the "right thing to
>> do"
>> and real
>
> I haven't touched Gwiz in ages. This is the first time I've heard of
> such a message. It is clearly related to some sort of graphic interface
> problem
>
> Ken
>
Clearly nobody is using it lately :)
Not surprising as it took quite a bit to figure out how it works.
Documentation is scat
I haven't touched Gwiz in ages. This is the first time I've heard of
such a message. It is clearly related to some sort of graphic interface
problem
Ken
On 9/9/2012 4:27 PM, Chris Morley wrote:
> mostly for Ken Lerman...
>
> I played with Gwiz to get it working with linuxcnc (vrs emc2)
> I push
Kent A. Reed wrote:
> On 9/9/2012 1:54 PM, Jon Elson wrote:
>
>> <...> I have not reported any thread latencies for the Beagle.
>>
>>
>> Sorry, Jon. Looking back I see you were talking about how fast one could
>> drive GPIO pins. My memory is getting rustier by the day.
>>
And, mine i
I guess that the only thing I can add at this point is that you can
have course- or fine-grain parallelism. I can easily see how to do #3
below using a course-grained approach by writing separate programs in
each one of the work envelope regions, and then having a master command
the machines i
mostly for Ken Lerman...
I played with Gwiz to get it working with linuxcnc (vrs emc2)
I pushed those changes it should work with linuxcnc and linuxcnc-sim
I only tried sim.
When started I get a warning message about 'ignoring setting cHRM of RGB
triangle
with area of zero"
If you don't cance
The upgrade to gremlin in master (well gscreen based on master)
to report g code errors gives me an error report:
Traceback (most recent call last):
File "/home/chris/emc2-dev/lib/python/gladevcp/hal_gremlin.py", line 70, in
self.gstat.connect('file-loaded', lambda w, f: self._load(f))
On 9/9/2012 1:54 PM, Jon Elson wrote:
> <...> I have not reported any thread latencies for the Beagle.
Sorry, Jon. Looking back I see you were talking about how fast one could
drive GPIO pins. My memory is getting rustier by the day.
> <...> I have never run an RT kernel on the
> Beagle, but wo
Kent A. Reed wrote:
>
> What with the differences between different IP cores from ARM Holdings,
> different CPUs from licensees of the IP cores, and different boards
> integrating lots of other stuff to these CPUs from folks like
> BeagleBoard, the Raspberry Foundation, etc., I am in a state of
On 9/8/2012 3:18 PM, Michael Haberler wrote:
> also, this was a stock kernel and I dont know if the configure options are
> great or useless
>
> maybe somebody aware of rt-preempt configuration can look over
> this:http://git.mah.priv.at/gitweb/raspberry-test.git/blob/7791f6c3f5c37242334511fda718
16 matches
Mail list logo
