Nachrüstung CNC

Halo
although I have already posted in this forum I would like to introduce myself, and immediately afterwards burden you with a problem.

My name is Thomas and will work as stonemaze in My own company and also have an German electrical engineer education .
I have already implemented a 3 axis saw with UCCNC and an ETH300 in my company which works fine with 2-fold closed loopsystem .

My new project is a retrofit of a 4+1 axle machining center (which is a real heavyweight with a total weight of 10 tons).
The axes 3 phases 500V 2.2 KW are controlled via regular VFD closed loop over PWM or clock/direction, the path encoder is to be queried via a MESA 7i95
The plan was to take a Raspberry Pi 4 Model B with 4 GB as an HMI / controller on which I have now installed Linux Debian Buster RT with LinuxCNC 2.9.0 becuse it is more flexible and give the chance zu use RT Encoder

Machine configuration
Controller - Raspberry Pi 4 Model B 4GB and USB 3.0 SSD 32GB, 32GB SDHC Disk
Software Controller - Linux Debian Buster RT with LinuxCNC 2.9.
Software CAM - W10 with Solidworks (postprocessor still unknown)
Axes every 2.2 KW VFD with PWM / clock direction and encoder 2500 increments ABZ and TTL data
wayencoder TTL-Data / ABZ DN (Siemens)
Dimensions travel distances - working range 2000 * 3000 * 500, 360 O mm limits 2200 * 4000 mm
Spindle Modbus Controled
IO PLC - S7400U 64 inputs and outputs

The following problems occurred during the planning!
- Installation of Probe Basic failed (already requested in this forum)
- Mesa 7i95 is not in the list of PNCCONF
- Establishing a Modbus connection to the PLC to evaluate the I/O

i will be very pleased if these forum wil give me support to get these thin running.

thanks

Thomas

The 7I95 is not supported by pncconf yet but you can use a pncconf
configuration created for a 7i96 and hand edit it to work with the 7I95

Things that need changing:

Change the card name in the ini file to "7i95" ( using the "Use INI substitution for Mesa board names" option)

Change the inputs from GPIO to INMUX
that is change:

gpio.000.in
to
inmux.00.input-00

etc

hi,
thanks for your suport

the first act is done and LinuxCNC starts with gmoccapy.

the next step (Tomorow) is to rewrite the .ini file to correct the Gpio to Inmux like shown on Mesaflash --device 795 ....

I think tomorrow I can assemble the machine.

PS : Don't think I'm a grammatical spastic, but I'm not familiar with writing in foreign languages, sorry for that.

hi,

I´m using - mesaflash --device 7i95 --readhmid - for readout.

there are only 3 encoders for m,uxedQCount (0 1 2) 57 ports at all

the next is an error Parameter or pin ´hm2_7i95.watchdog.timout_ns´not found

The 7I95 has 6 encoders (using multiplexed inputs these 18 signals are reduce 10 to FPGA pins)

"the next is an error Parameter or pin ´hm2_7i95.watchdog.timout_ns´not found"

This is likely a typo or editing issue or the driver failed to load for some reason

Once you get LinuxCNC to start with the 7I95, you can list all available pins with:

halcmd show all hm2

ok, i get LinuxCNC running after setup new on PCNconf as 3 Axis.

(at this time i study the HAL tutorial , a little bit dry but .... )

where is it posible to change gpio to Inmux ?
i havent found it in the mashine .hal or . ini

thomas.heisig wrote:

ok, i get LinuxCNC running after setup new on PCNconf as 3 Axis.

(at this time i study the HAL tutorial , a little bit dry but .... )

where is it posible to change gpio to Inmux ?
i havent found it in the mashine .hal or . ini

With linuxcnc running.
Open up a terminal and type.
halcmd show all hm2

That should give you a list of all the pins.

You edit the hal file. With a text editor.

hi,

i think i am to stupid to fin these gpio.000.in in the .HAL
or what did i do wrong ?

I'm sorry got it wrong.

[edit]
Looking at your .hal file it seems that you have not used any digital inputs or outputs yet:

so apparently you have not declared any in the pncconfig tool. So you can just declare by adding them manually to your .hal file using the form:

hm2_7i95.0.inmux.00.input-00

As an example for input number 0.