>I'm not sure why you would care about that, but there is a file in the >source tree describing that: >http://cvs.linuxcnc.org/cvs/emc2/directory.map?rev=1.28 > >The first part describes the layout of the emc2 source tree, the second part >where everything gets installed. > >Again, I am not sure what information you try to gain from that.
I take from that that I know what happens in my system and this gives me more feeling of security. It is important to feel reassured in order to go on learning. >That folder holds all the configuration files for emc2. >The ini is the first file that gets read, it contains links to all other >files (.hal , .tbl, .var, .nml). > >The emc2 runscript (found in /usr/bin/emc) reads that file (either after you >chose it from the config picker, or if you specify it directly "emc >~/emc2/configs/mymachine/mymachine.ini" or if you run the last configuration >"emc -l"). >It reads the section describing that the NML file is called (usually >emc.nml), then start to load emc2 components. >For the various tools you have, it reads the tool table file defined in the >ini (called *.tbl). >For saved offsets and variables, it reads the var file (called *.var). > >Then it starts setting up the hardware part of emc2, which is handled using >HAL. >For HAL you can have more than one .hal file, to keep things easier to read. >Basicly the hal files define how many stepgen's to be loaded, and to what >pins on the parport to connect them. >Further they define the timings for the stepgens and so on. That's exactly what I was looking for from the beginning, thank you. >The ini file format and options is described here: >http://www.linuxcnc.org/docview/html//config_ini_config.html >Understanding the HAL files is probably a bit more complicated than just >looking at some tables. >I would start by reading: >http://www.linuxcnc.org/docview/html//hal_basic_hal.html >http://www.linuxcnc.org/docview/html//hal_general_ref.html >http://www.linuxcnc.org/docview/html//hal_drivers.html (only parport stuff) >http://www.linuxcnc.org/docview/html//hal_rtcomps.html (probably only >stepgen) Great - I'll get into these! >All the above docs are included in the emc2 documentation, but as it's >really vast, it's probably hard to keep an overview. >"Understanding what the system does in detail" is probably a task that will >take a couple months/years (depending on the dedication ;). >Maybe you mean understanding what components are in emc2, and how they >interact, that's more like a realistic goal, but for running emc2 you don't >need any knowledge of details. Of course, I don't want to be a EMC developer, but for me it's essential to know what I am dealing with - wouldn't drive a car without knowing how the motor works, and when I buy a technical device, first thing will be I take it apart and look inside! >Regards, >Alex Many thanks again, you answered to most of my problems (as of now)! Peter Blodow ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
