Hi all,
I am still Learning LinuxCNC and I again have a few questions.
I am trying to figure out the best way to "drive" LinuxCNC from a C++
program.
This program would receive general commands from the user, something
like: "execute procedure 1" and translate this into telling LinuxCNC to
open
> I am trying to figure out the best way to "drive" LinuxCNC from a C++
> program.
> This program would receive general commands from the user, something
> like: "execute procedure 1" and translate this into telling LinuxCNC to
> open a specific file and run the G-code therein.
If you are using
xemc.cc is a C++ program that uses the relevant APIs. It is far from
being tutorial documentation, but at present we don't *have* any
tutorial documentation about using these APIs.
(such documentation would be a great contribution to LinuxCNC. You
could start with a new page on the wiki and late
LinuxCNC externally with C++ program
Hi all,
I am still Learning LinuxCNC and I again have a few questions.
I am trying to figure out the best way to "drive" LinuxCNC from a C++
program.
This program would receive general commands from the user, something
like: "execute procedure 1
lter Cigana [mailto:walter.cig...@gmail.com]
> Sent: Monday, 21 October 2013 5:22 PM
> To: Enhanced Machine Controller (EMC)
> Subject: [Emc-users] Controlling LinuxCNC externally with C++ program
>
> Hi all,
>
> I am still Learning LinuxCNC and I again have a few questions.
&g
On 11/03/2013 08:04 AM, Walter Cigana wrote:
> So, I have played with the xemc.cc code to uncover some C++ interfaces and
> I have also played with using linuxcncrsh to control remotely, which is
> obviously simpler.
>
> In my situation, I also need to monitor an analog input which will return a
>
On Sun, Nov 03, 2013 at 09:12:06AM -0700, Sebastian Kuzminsky wrote:
> Then in linuxcncrsh you can read HAL pins & signals like this:
>
> set mdi (debug, #<_hal[axis.1.f-error-lim]>)
> get operator_display
> OPERATOR_DISPLAY 0.01
Personally, I discourage use of this feature, because it ignor
On 4 November 2013 13:33, Jeff Epler wrote:
>> set mdi (debug, #<_hal[axis.1.f-error-lim]>)
>> get operator_display
>> OPERATOR_DISPLAY 0.01
>
> Personally, I discourage use of this feature, because it ignores one of
> the main points of linuxcnc's hal:
...
> As a concrete example: suppose y
