Thanks Andy, it works great.
On 2014-09-04 17:10, andy pugh wrote:
> On 4 September 2014 15:52, Marius Liebenberg wrote:
>
>> motion.analog-out-00 => mycomp-float-in.
> Yes, exactly that.
>
--
Regards /Groete
Marius D. Liebenberg
+27 82 698 3251
+27 12 743 6064
QQ 1767394877
---
On 4 September 2014 15:52, Marius Liebenberg wrote:
> motion.analog-out-00 => mycomp-float-in.
Yes, exactly that.
--
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manifesto
--
Slashdot TV.
Video f
Thanks Andy
Do I understand it correctly. I have to send the value from gcode to an
analog pin that is connected to my float input in HAL to get the actual
value. Scaled obviously.
I.E
motion.analog-out-00 => mycomp-float-in.
On 2014-09-04 16:32, andy pugh wrote:
> On 4 September 2014 15:17,
On 4 September 2014 15:17, Marius Liebenberg wrote:
> I understand that one can get a value from HAL into a gcode sub routine.
> I am trying to set a HAL pin from my gcode but it seems not to want to
> happen.
The #<_hal[hal.pin.name]> format is read-only, so the easy option is
unfortunately not
Hi All
I understand that one can get a value from HAL into a gcode sub routine.
I am trying to set a HAL pin from my gcode but it seems not to want to
happen.
Firstly is it possible to do and secondly, how do I debug to see what is
happening?
--
Regards /Groete
Marius D. Liebenberg
+27 82 69
