Retrofitting a 1986 Maho MH400E

Fully customize the software to the machine is what the companies do, but linuxcnc is buil in a way to adapt to a large range of machines without the need for changes in the core, we have to first try the tool the developers of linuxcnc have given to us before changing the way linuxcnc is working. Debugging, helping others and ask for help is a lot easier fallowing the mainstream road.
John

i think, you have not understand what this is.
This is an simple comp file (like classic ladder for example) and not an change to the core or some other basics.
In the final state this will be an universal component for Maho and Deckel Transmission like the other ones around for
turrets or handwheels.....
simple load it in hal, assign pins and set some parameters.

Hi I was talking for changes in python, and the way linuxcnc handle signals and variables.
John

Thanks for posting your gearchange comp file Dominik. So far I have no C programming experience, just a little python. The fragments of C code I have collected in the past for the gear shifting were not clear enough for me to understand, or even for C programmers at work to understand. Yout code is a lot more complete and really nicely structured. I m sure I'll have a bunch of questions.

Q1/ If I understand this correctly, your 700's spindle brake is controlled by the NC controller. On the 400E, the spindle brake is controlled electrically by a relay off the spindle on relay. I need to comment out all the brake stuff?
Q2/ What was your plan with the manual change stuff? I was planning to only have automatic control, and simply change gear with an MDI S command if needed.
Q3/ Does you code do a Z retract off the work if it encounters a speed change in the middle of contourings?

I appreciate that John has put a lot of work into getting the timing and switching into the classic ladder, but that would still need some glue to get it called and responding to S codes in the NGC files.
Mark

Hello Mark

Q1 after your question i noticed that your power schematic on page 1 of this thread is a little different to the 700C. There have to be made some changes because your brake for toggeling is engaged by the triangle Relais. Can you tell me what kind of device 1K6 is and what its contacts do?

Q2 I let the Heidenhain Panel stay in the Machine and it has these buttons for manual milling, simple set the auto input fix to true.

Q3 No, this has to come out from the NC Programm, following the standart way is that you can not send Axis movement commands from hal,comp or ladder. But i never note about speed changes while the tool is in the material, normaly this comes with an toolchange or a new chapter of your Cam Application.

Thanks for your help Dominik.

db1981 wrote: Q1 after your question i noticed that your power schematic on page 1 of this thread is a little different to the 700C. There have to be made some changes because your brake for toggeling is engaged by the triangle Relais. Can you tell me what kind of device 1K6 is and what its contacts do?

-available gear states = position count [line114]
-you have to set the rpms for the singles states (so much as position count) [see line 73-79]
-the positions for the single gear states are defined in the Extra_Setup Part line 177 ff.

Q1 1K6 is a time delay relay. It is set for 7.5 seconds.

I've expanded the 7 to the 18 gear ratios of the MH400E, entered the resulting speeds, expanded the single gear states list, entered the MH400 States, and expanded the data.pos[N].max_rpm = max_rpm_N+1 list.



Q2 I wasn't sure what you meant by auto input fix.

Thanks clarifying that you cant do axis motion from a comp, hal or ladder. Is there any standard behavior associated with spindle speed which will need to be deactivated when this COMP is added?

Mark