2.4. Building emc2 (realtime)

Whats strange is that the hal code and tool table worked when I ran emc2 installed from
the live disk. I will fix the hal code and mess with the tool table file.

stepgen.7 for the moment is used as a fail safe for my high power servo drive board.
The output is connected to a hardware retriggerable one shot with a time constant of
50 us and triggers on rising and falling edges. the output is connected to the drive
enable.

If there is a software failure while the motor is running at speed the drive shuts down
and coasts to a stop. other wise the servo drive would be subjected to very high currents
and bursts into flames.

Sorry a bit more advanced diagnostic tactic than I am capable of with out more
understanding.

A couple curious clues the tool table file error has disappeared since my last session.
(shut down & startup)

A checked for the hal code problem that that produces the error
"custom.hal:31: parameter or pin 'stepgen.7.position-scale' not found"

There appears to be nothing wrong with this line of hal code but I replaced it with a fresh
line setp stepgen.7.position-scale 1 just in case of something weird I could not see on the
line of text this made no difference same error.

When I launch emc from the emc2-dev it is defiantly using the custom hal file in
/home/me/emc2/configs/my-mill which was created by the config wizard some time ago.
I assume this supposed to happen.

I did a major house cleaning removed all the accumulated junk emc2 files and folders
except one configuration.

I opened a terminal cd to emc2-dev and typed emc hit enter and EMC2 loaded and
ran correctly.

I assume I am now in the RIP mode and the code that was compiled in the emc2-dev
dir is running the show now. Is there any simple way to know if this so?

OK The installed emc2 still works correctly, had a go at running the RIP
but something went wrong when I did the right commands to run the RIP
version.

me@CNC:~$ cd emc2-dev
me@CNC:~/emc2-dev$ . ./scripts/emc-environment
me@CNC:~/emc2-dev$ emc
EMC2 - 2.5.0~pre
Machine configuration directory is '/home/me/emc2/configs/my-mill-2'
Machine configuration file is 'my-mill-2.ini'
Starting EMC2...
libnml/buffer/physmem.cc 143: PHYSMEM_HANDLE: Can't write 10824 bytes at offset 60 from buffer of size 10208.
libnml/cms/cms_in.cc 1383: CMS:(emcStatus) Error writing 10824 bytes to global memory at offset 0x81f6d38
(See libnml/cms/cms_in.cc line 1386.)

**********************************************************
* Current Directory = /home/me/emc2/configs/my-mill-2
*
**********************************************************
* BufferName = emcStatus
* BufferType = 0
* ProcessName = emc
* Configuration File = emc.nml
* CMS Status = -3 (CMS_INTERNAL_ACCESS_ERROR: An error occured during an internal access function. )
* Recent errors repeated:

PHYSMEM_HANDLE: Can't write 10824 bytes at offset 60 from buffer of size 10208.

CMS:(emcStatus) Error writing 10824 bytes to global memory at offset 0x81f6d38
(See libnml/cms/cm

* BufferLine: B emcStatus SHMEM localhost 10240 0 0 2 16 1002 TCP=5005 xdr
* ProcessLine: P emc emcStatus LOCAL localhost W 0 1.0 0 0
* error_type = 5 (NML_INTERNAL_CMS_ERROR)
************************************************************

libnml/buffer/physmem.cc 143: PHYSMEM_HANDLE: Can't write 10824 bytes at offset 60 from buffer of size 10208.
libnml/cms/cms_in.cc 1383: CMS:(emcStatus) Error writing 10824 bytes to global memory at offset 0x81f6d38
(See libnml/cms/cms_in.cc line 1386.)
libnml/buffer/physmem.cc 143: PHYSMEM_HANDLE: Can't write 10824 bytes at offset 60 from buffer of size 10208.
libnml/cms/cms_in.cc 1383: CMS:(emcStatus) Error writing 10824 bytes to global memory at offset 0x81f6d38
(See libnml/cms/cms_in.cc line 1386.)

--- SEVERAL DOZEN MORE LINES OF THE SAME THEN --

Maximum number of errors to print exceeded!
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
A configuration error is preventing emc2 from starting.
More information may be available when running from a terminal.
Shutting down and cleaning up EMC2...
Cleanup done
EMC terminated with an error. You can find more information in the log:
/home/me/emc_debug.txt
and
/home/me/emc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal
me@CNC:~/emc2-dev$

YOW! what a mess of errors. The " configuration error" is this referring to
a problem with the my-mill-2.ini file?

It's Alive! Success EMC 2.5.0 is running!

Many, many thanks John