Traub Bosch cc100 retrofit

aventtini wrote:

Why are so many files on the zip folder of the VMC

Because it is a complete working simulation of a machine with spindle orient and a toolholder.

Expand the zip in your configs directory and you should be able to watch it work on screen almost like the real thing.
(well, after installing carousel.comp anyway)

aventtini wrote:

i see it has spindle hal and toolchanger hal . So i need to delete the existing one from my machine and include and mod this

Noooo!

Keep what you have if it works, but look at the new config and see how that works. Don't expect to be able to blindly use HAL snippets, you have to work on understanding the underlying logic.

aventtini wrote:

I understand i can do this on ClassicLadder and Hal file

If you are more comfortable with Classic Ladder then use Classic Ladder, if you are more comfortable with G-code then you can run the tool-change sequence from a G-code subroutine.

The sample config I made uses G-code because I haven't bothered to learn CL yet.

aventtini wrote:

Why are so many files . I have seen all the setup has minimum 10 file .

Have you tried running the sample configuration I wrote? It might make more sense if you do, and you can experiment with config changes on the simulated machine rather than make expensive mistakes with real hardware.
(It won't actually run until you install the carousel component, as detailed below)

The files are as follows:

arm.stl, base.stl, carousel.stl, head.stl, table.stl. You can ignore these, they are files that define the shapes of the parts of the simulated machine

carousel.comp - You might need this, it is a new HAL component that I have written to control toolchanger carousels. It will hopefully become a standard part of LInuxCNC in the future.
sudo comp --install --install-doc carousel.comp should install the file into your system, then you won't need it again.

README is a text file that is displayed in the LinuxCNC config picker. It describes the config.

remap.py - You need this to make M6 call a G-code routine. But you don't need to edit it.
remap.pyc can be ignored.
toplevel.py is another file related to the M6 remapm you need it, but don't need to change it.

sequencer.comp is another custom HAL component. But the config isn't using it at the moment, it is an alternative to both CL and G-code remapping. Ignore it.

sim_vmc.hal is a HAL file that makes the simulated machine look like a real machine to HAL. Ignore it if you have a real machine.

spindle.hal is a HAL file that controls the spindle, including spindle-orient on the M19 command.

toolchange.hal is the HAL file that sets up the toolchanger. You would need to tweak this for your machine, but probably not much. The inputs and outputs need to be linked to real IO pins.

toolchange.ngc is the G-code subroutine that runs the tool change sequence.

vmc.hal is the standard HAL file for the sample machine. This is exactly equivalent to your existing HAL file.

vmc.ini is the INI file for the config. You will need to copy a few things from that INI file to your INI file, but you won't want the file. The [PYTHON] section, the extra files added to the [HAL] section and the REMAP= commands in [RS24NGC] and the spindle control PID parameters are what you need from there.

vmc.tbl and vmc.var are standard tool table and var files. Ignore them.

vmcgui is the Python file that runs the Vismach simulation.

So, The only files from that config that you need are remap.py, toplevel.py, toolchange.hal and toolchange.ngc. And you only need to understand the last two.

aventtini wrote:

Now if the drive wants taco and we dont have can i hook one of the chanels of the encoder ?

No, the tacho outputs an analogue voltage and it should go directly to the drive and nowhere else.

What is the position sensor? (The tacho isn't a position sensor, it is a velocity sensor) but every servo needs position feed back too.