Chris Radek wrote:
>
>
> It's in the DRO, a star on the Absolute numbers.
>
I watched for that, but this display is not very clear, so I must have
missed it.
>
>> Also, the indication of
>> which axis is currently selected is hard to determine.
>>
>
> This is because some of the ubun
On Sun, Jan 16, 2011 at 08:06:03PM -0600, Jon Elson wrote:
> OK, I now have touchy running on a newly-built system. I have a few
> things I've found that seem like they could be improved. One is that
> there is no indication that an axis is homed.
It's in the DRO, a star on the Absolute numb
OK, I now have touchy running on a newly-built system. I have a few
things I've found that seem like they could be improved. One is that
there is no indication that an axis is homed. Also, the indication of
which axis is currently selected is hard to determine. I would expect
that the axis
On Sun, Jan 16, 2011 at 01:47:17PM -0600, Jon Elson wrote:
> /usr/bin/touchy:73 GtkWarning: gdkdrawable_get_source_drawable:
> assertion 'GDK_IS_DRAWABLE (drawable)" failed
This warning is caused by a gtk bug and can be ignored.
> One other oddity, after commenting out the line in the [HAL] sec
Jon Elson wrote:
> Hello, all,
>
> I am trying to get Touchy working on an EMC 2.4.6 system. I adapted
> the changes made on that Gateway Profile system with the touch screen I
> had at the CNC Workshop, but couldn't get it to run. I removed the hal
> file touchy.hal from the list of hal file
Hello, all,
I am trying to get Touchy working on an EMC 2.4.6 system. I adapted
the changes made on that Gateway Profile system with the touch screen I
had at the CNC Workshop, but couldn't get it to run. I removed the hal
file touchy.hal from the list of hal files called in the .ini file, b
Kirk Wallace writes:
>It may be that an Arduino could do this, but my impression is that there
>aren't enough AVR pins coming out to where one could get to them. The
>price of the smaller Arduino's seems to fit my plan though.
The RepRap and MakerBot use a different AVR chip that has a dozen mor