NativeCAM is Features renamed

I am confused why I am getting that when so many others are running the same sim file you provide and apparently not getting that error. In the file, the comments say it loops the motor command back to the motion module for simulation purposes. I would suspect the simulator would not function without it.

I fully plan on implementing it on the Bridgeport mill configs next anyways. I am very excited about using Ncam on a very regular basis on that machine. (just finished the retrofit today)

One other question: I plan on using a Pyvcp side panel with axis with some checkboxes and led's for such things as selecting hi and low range in the hal files config. Many use Pyvcp side panels for such purposes. How will that work with NativeCam implemented? Will the Pyvcp panel be adjacent to the axis/NativeCam window? I am a bit worried about how this will work out.

I really know nothing about this but is that just a symptom of running NativeCAM on master
(which is JA-XX based so doesn't have axis.0.motor-pos-cmd anymore but just the joint
equivalent)

Playing further I may see part of the problem. I cloned the repo into my linuxcnc directory, it created a folder in the linuxcnc folder named NativeCAM. When launching either the embedded sim or my own machine config I get errors referencing files that are not found, always referenced in a folder "ncam", there is no such folder.

Looking over the sim mill ini file, it also references a ncam directory, which does not exist.

Apparently the directory names and locations are not matching up.

Did the software change perhaps and this was not updated?

PCW wrote: I really know nothing about this but is that just a symptom of running NativeCAM on master
(which is JA-XX based so doesn't have axis.0.motor-pos-cmd anymore but just the joint
equivalent)

Makes perfect sense. I am surprised however, Fern is using Master I believe, I wonder why he does not have this issue?

Apparently the sim file is not compatible with the latest releases of master.

Hi,

gmouer wrote: I cloned the repo into my linuxcnc directory, it created a folder in the linuxcnc folder named NativeCAM. When launching either the embedded sim or my own machine config I get errors referencing files that are not found, always referenced in a folder "ncam", there is no such folder.

Looking over the sim mill ini file, it also references a ncam directory, which does not exist.

Apparently the directory names and locations are not matching up.

I do not know if you cloned after your previous post but here is what I see in it :

• You seem to be running 'LINUXCNC - 2.8.0-pre1-2761-g2b678aa' which may be part of the problem
• Machine configuration directory is '/home/bridgeport/NativeCAM/configs/sim/axis/ncam_demo' not under linuxcnc directory as you state

Also './core_sim.hal' is part of LinuxCNC and NativeCAM does not need it. A couple months ago when I started lcnc, it gave a message that some files needed to be updated and proceeded. I can not tell what has changed since I deleted the backup files after I was sure it was working fine.
For your info, other users had that problem before
forum.linuxcnc.org/40-subroutines-and-ng...named?start=20#81411

Including the printed message will help me pointing the problem and the solution

Regards
Fern

I just checked your files directly on the github, core_sim.hal is included in your files.

I found this info on joints/axes and the changes in Master related to it.
linuxcnc.org/2016/06/27/Joints-Axes-merged/

The core_sim hal file in github for Nativecam has references to axis.0. Core_sim.hal in the sims that come with master refer to joint 1 per the new standard. What is interesting is that according to the doc I linked to, Master should automatically update the hal file to the new standard using joints, apparently that does not happen for some reason and the error message results. I had a near identical error in the homing hal file for similar reasons.

The other errors, referring to a "ncam" directory are still a mystery. There is no ncam directory doing a standard setup.

Hope this helps a bit.