Advanced Search

Those Maho's are already CNC from the factory, meaning they have motors on each axis and have ballscrews, so very easy to retrofit.

Means a similar retro fit like these ones? 



forum.linuxcnc.org/12-milling/33035-retr...86-maho-400e?start=0




 

Servo Zentralantrieb in allen drei richtungen
means
central (single) servo drive for all 3 directions
So not hydraulic, but the tool lock is hydraulic, both for horizontal and vertical head.
In short, retrofitting to full CNC would require removing the central drive and gearbox and adding motors to each axis on the hand crank, most probably.
Also, normally, this type of machine uses trapezoidal screws and brass nuts, so have a lot of backlash, that can be fixed in software to a certain degree, but do not expect much precision.

In one of the pictures in a sales catalogue it says There is a WF5 and a WF5NC, which seems to be a control to move.

The attached picture of the original post clearly says WF5 NC on the machine tag. 

It says "punkt-strecken-gesteuert", I guess that means it can move one axis from a given position to another given position at a time?

 

p.s. that thing must be from the last century , older than computers.
 

Hello.  After incorrect firmware loading all three LEDs on the board light up and mesaflash not found board. I try jtag flash. The firmware is uploaded successfully and light up only yellow power led. Mesaflash found board, but when I try to write a bit file an error occurs: Error: BootSector is invalid.
--fixbootblock doesn't help. What shoud i do to wrtie bit file in EEPROM?
 

Thank you for the reply, attached you find the current HAL and INI files
Sigi

 
 

四个伺服驱动器使用 EtherCAT。Mesa 卡用于控制 MPG、急停、对刀仪和冷却液。

Hi Peter,

Is the file you uploaded correct? It is listed as 7I96S and I can't seem to find a .bit file.

Thanks,

Dan

Tengo cables blindados en todos los cables (motores, encoder, interruptores de limite) y están conectados a tierra solo en el lado de los controles. También tengo cables blindados entre los drivers y la tarjeta mesa 7i96s (no se si son necesarios ya que están dentro de una caja metalica)

Y ahora ya estoy dudándolo creía que la conexión diferencial era menos susceptible a EMI (me podrías decir como lo tengo conectado como en el diagrama que te envié) y si lo tengo conectado de manera equivocada cual es la correcta. No se como es la conexión en single ended.

Editado 

Creo que lo que me recomiendas es esto me lo puedes confirmar.

 * Alimentación de +5V a los pines de entrada positiva del driver CL86T:  

 * Conectar los pines PUL+, DIR+ y (ENA+ si se usan para controlar el habilitado) del driver CL86T a una de las salidas +5VP de la Mesa 7I96S.   Los pines +5VP en los conectores TB1 (por ejemplo, TB1 Pin 6, 12, 18, 24 para los ejes 0-3) TB2 (por ejemplo, TB2 Pin 6, 20 para el eje 4). Estos pines son salidas de 5V protegidas contra cortocircuitos por PTC.

 * Señal de Paso (STEP):   Conectar el pin STEPx- de la Mesa 7I96S (donde 'x' es el número de eje, por ejemplo, STEP0- para el Eje X en TB1 Pin 2) al pin PUL- del driver CL86T.

* Señal de Dirección (DIR): 

  * Conectar el pin DIRx- de la Mesa 7I96S (donde 'x' es el número de eje, por ejemplo, DIR0- para el Eje X en TB1 Pin 4) al pin DIR- del driver CL86T. NO SE SI ESTO ES OBLIGATORIO NO LO TENGO CONECTADO!

 * Señal de Habilitación (ENA - Opcional pero recomendado): 
 * La Mesa 7I96S tiene cuatro salidas DC aisladas de alta corriente (OUT0- a OUT3- y OUT0+ a OUT3+). 
  * Conectar el pin OUTx- de la Mesa 7I96S (por ejemplo, OUT0- en TB3 Pin 13) al pin ENA- del driver CL86T. Asegurando de que ENA+ del driver CL86T esté conectado a los +5V de la Mesa. Debería configurar esta salida en LinuxCNC.
Diagrama Esquemático SimplificadoMesa 7I96S (TB1/TB2/TB3)
  +5VP (Mesa) ->PUL+  DIR+   ENA+ (si se usa control por ENA)  (de TB1 Pin 6, 12, etc. o TB2 Pin 6, 20) |  

 STEPx- (Mesa)  ->PUL-  
DIRx- (Mesa) -> DIR- 
  OUTx- (Mesa) (Opcional para ENA) -> ENA- 

Gracias.

Hello pippin,

Thanks!

its called "Streamdeck" in my case the XL Version. Its a programmable lcd wirh buttons. Streamers/Cutters/etc use it for shortcuts and so on.


Smarter people than me are working on it to make it even more usable with LinuxCNC!

forum.linuxcnc.org/show-your-stuff/52628...for-linuxcnc?start=0




greetings
Tom

Which type of servo drive do you use?

Martin87 wrote:

I also have an automatic tool change that already works, but I'm prompted to do so every time I change a tool and have to confirm the tool with the OK button.
I don't know how to delete it from the system. It should run automatically without the OK button.
Do you perhaps have experience with this?
Kind regards

I also have an automatic tool change that already works, but I'm prompted to do so every time I change a tool and have to confirm the tool with the OK button.
I don't know how to delete it from the system. It should run automatically without the OK button.
Do you perhaps have experience with this?
Kind regards

pippin88 wrote:

Suggestion / request:
Overrides
When starting a program running (cycle start): user is prompted that an override (rapid, feed, or spindle) and asked whether they want to continue with override, or want to reset to 100%

HansU wrote:

I could imagine make an optional warn dialog with a settable limit. For all overrides? Feed, rapid and spindle?

Yes, something like attached.



Warning pop up if any override is on.

Switching from `pigpiod` to WiringPi resolved the issue—SPI communication is now working as expected.
Thank you very much for the detailed explanation.

I followed your instructions and used the following `gpio` commands to generate the clock:

gpio mode 7 clock
gpio clock 7 5000000

While I couldn’t measure the actual frequency, the FPGA responded properly after applying this change, so it seems that the commands produced an 18 MHz clock as you suggested.
My `board.json` already contained the following settings:

"clock": {
"osc": "18000000",
"speed": "29812000",
"pin": "35"
}

After this setup, the `rio-test` tool returned valid results, and LinuxCNC no longer shows the `"HXHP"` error.

It appears that the 5 MHz clock generated by `pigpiod` was not suitable for the ICE40, and this prevented the FPGA from functioning correctly.

Thanks again—this completely solved the problem.