Test LinuxCNC without motors and encoders connected

Peterdeleu wrote: Maybe I was not clear (English is not my native language )

It is mine, I have no excuse at all for my lack of reading comprehension there.

You _could_ try software OpenGL. This used to be common advice a long time ago, I am not sure how relevant it still is:
wiki.linuxcnc.org/cgi-bin/wiki.pl?Troubl...oftware_based_OpenGL

I've tried to install the OpenGL (or update)
But it is not possible because it was already installed an a many more blablabla...

I've tested my OpenGL whit that OpenGL geartest.. I have 950 frames per second.. that should be sufficient I guess

I've just created a Stepconf, and her it works fine!
My not working configuration is a Pncconf

What hardware are you actually using, though?

The PC LinuxCNC:
I'm using the onboard graphic card NVIDIAR GeForce 6150 + nForce 430. The motherboard is a M2NPV-VM ASUS

Mesa hardware:
5I25 - 7i77 and a 7i84

At this moment there's no CNC hardware connected.
Before I rebuild my machine (Biesse Rover 18) I try to find out how LinuxCNC works.
I know already a lot about the wiring of the Biesse and everything is documented.
I will use the LinuxCNC build-in PLC to control the hardware on the machine.
But I want to work save. The machine have very strong servo's, and first I want to understand LinuxCNC before I connect it with the Biesse.
What I did on LinuxCNC is simulating the Home and limit switches, the Estop, ... with buttons connected to the IO's.
I've created virtual buttons on the user interface of LinuxSNS to control the IO's. This will make it possible to wire the machine to the Mesa, and test all the hardware by pressing the virtual buttons. (Spindle on, vacuum cups, spindle down, tools down, ....

Well, just be aware that Stepconf isn't that much help for a Mesa setup.

(It is some help, the INI won't be far off, and all the important files will be created.
The HAL pins will be in the right places, but half the names will be wrong.