On 25 November 2013 18:36, Charles Steinkuehler wrote:
>
> A trim probably makes more sense than a mux, but both could work in
> different contexts. My immediate application is tweaking print
> temperature, where a trim seems appropriate. For other applications
> (like the cooling fan) a full ov
On 11/25/2013 11:38 AM, John Kasunich wrote:
> As Seb says, those pins are outputs from motion, and can be
> controlled ONLY by g-code.
I don't mind controlling the value with g-code, but this is "jog while
UN-paused"...I'd need to be able to inject gcode into a running program
stream. Not easy t
As Seb says, those pins are outputs from motion, and can be
controlled ONLY by g-code.
I think you can do better than the mux approach though. For
example, use a summer, and add a manually adjustable (PyVCP
or gladeVCP) "temperature trim" value to the main value coming
from the g-code.
Or maybe
I'm not an expert, but maybe it is because your analog output is associated
with a given axis/joint,
If you remove the axis, so that it is not controlled by the motion
controller, may be it is possible to set the value as you intend.
In this case the given motion.analog-out-00 is not "hal-wired"
On 11/25/13 10:02 , Charles Steinkuehler wrote:
> $ halcmd setp motion.analog-out-00 32
> :0: pin 'motion.analog-out-00' is not writable
>
> So how can I update these values manually if a program is running?
The motion(9) manpages says that those are output pins from motion, set
by M67/M68, that
I want to switch to using motion analog/digital outputs and M6x commands
for control of temperatures, fans, etc. on my 3D printer, but I can't
figure out how to change these values manually.
When I use an M1xx code and a HAL signal, I can just use halcmd to set
the desired value regardless of whe
