Gmoccapy - A new screen for linuxcnc

Norbert,
I current have a master branch 2.6.0-pre0-3204-g8db1115 installed into a VM for testing.

I used the version of gmoccapy from git so I assume that it is the latest.

I am trying to run in sim mode and those are the .hal files I seem to have issues with.

Not sure that I am familiar with the rip-environment but will check on that.

I looked over the wiki and did not see anything that helped.

Matt

In the virtual machine, do the following:

Do you use virtualbox, or an other virtual machine, virtualbox is ok but vmware some times makes problems.

Norbert

I am using VMware so perhaps there is an issue there.

I have already done what you have posted but re-ran again.

There seems to be a problem with getting libmodbus-dev:

sudo apt-get install libboost-python-dev libmodbus-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package libmodbus-dev

There also seems to be an error with the make:
linuxcnc-dev/src$ make
Makefile:55: Makefile.inc: No such file or directory
Makefile:66: *** Makefile.inc must specify RTPREFIX and other variables. Stop.

Matt

Please try from virtualbox, and install on it the 10.04 LinuxCNC CD, then run the code I posted and everything will work out of the box!

Norbert

mariusl wrote: Andy
I am using a standard three stepper config with Gmoccapy. So I am fairly sure it is trivkins and Halui is loaded. If nothing goes wrong in between and you dont have to restart the process, it seems to be ok. Only thing is you have to change the mode to AUTO by hand before closing the dialog.

Can I suggest that it would be useful to try running the gantry/gantry sample config, and see how things work out? That is a parport config, so doesn't know that there is no hardware connected.
If you modify it to load halui it would be useful to know if it randomly drops back to joint-mode.

Hi Norbert
I am busy testing the mill functions of Gmoccapy and found that I cannot highlight a line of code to show it in the backplot nor does the code highlight when a move is selected on the backplot. If I want to use "Run from line" then these two functions should be active.