Search Results (Searched for: )

  • meister
30 Dec 2025 19:36
Replied by meister on topic LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)
not with my VFD, if it set to RS485 mode, all other inputs are disabled.

But I'm already trying something.
I'm currently writing a simple Modbus simulator in Python.
I already have an idea of how I can implement it.
  • PCW
30 Dec 2025 19:32
Replied by PCW on topic 7i97t Mesaflash Problem
Can you post your hal/ini files?
 
  • Robin123
30 Dec 2025 19:21
Replied by Robin123 on topic 7i97t Mesaflash Problem
First of all, thank you so much for the quick replies! With the spontaneous help of a colleague, I downloaded the latest version of mesaflash, etc., did the same thing, and it worked for him. However, the problem is still that I can't control the analog outputs. I got the idea about the firmware because I read somewhere that I need a different version so that analog output is available instead of PWM. Currently, I have PWM 00...05, with both value and enable settings. When I set enable, the Mesa outputs about 0.35V at the analog output. Scale = 10 Max_output = 10 Do I need to adjust anything else? If you need any further information, please let me know! Thank you!
  • Dave3891
30 Dec 2025 18:20
Replied by Dave3891 on topic LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)
Could the speed command be sent in the modbus loop and then I could use regular gpio for the start stop?
  • meister
30 Dec 2025 18:04
Replied by meister on topic LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)
It could be a bit difficult. To be honest, I've never really thought about how to integrate a VFD using normal Modbus commands.

The main problem is that Rio sends the values in a loop, and individual commands cannot be triggered by a button, for example (to start/stop).

I think I'll have to expand it a bit for that,
but you can try reading out a few values to test the communication.

in json it looks like that to read BusVoltage and RunningFrequency:
Code:
{ "type": "modbus", "pins": { ... }, "config": { "BusVoltage": { "address": 1, "type": 3, "register": 4098, "values": 1, "datatype": "int", "scale": 1.0, "unit": "", "error_values": "", "format": "d", "timeout": 100, "delay": 60, "priority": 0, "direction": "input" }, "RunningFrequency": { "address": 1, "type": 3, "register": 4097, "values": 1, "datatype": "int", "scale": 1.0, "unit": "", "error_values": "", "format": "d", "timeout": 100, "delay": 60, "priority": 0, "direction": "input" } } },
  • PCW
30 Dec 2025 16:32
Replied by PCW on topic 7i96S card arrived what setup is recomended
I think I would choose the alarm polarity so its "ON" for alarm, then the can be wired in parallel

To wire the enables in parallel, a single 5V step/dir pin may not have enough current
so a better scheme would be to use an isolated output for this, say:

+5V --> OUT0+
OUT0- --> ENAX+,ENAY+,ENAZ+
5VGND --> ENAX-,ENAY-,ENAZ-
 
  • Crusader2050
30 Dec 2025 16:23
Replied by Crusader2050 on topic Following errors
yeah that's the chap..
  • rodw
30 Dec 2025 16:18
Replied by rodw on topic Following errors
Sorry, I misunderstoeod the issue. Tuning the PREEMPT_RT kernel to minimize latency can solve some following errors and it is not documented anywhere in one place and those who follow my guide have had some impressive results as shown in user comments in the video.
This was a very hard topic to put together in a coherent manner.
  • Dave3891
30 Dec 2025 16:10
Replied by Dave3891 on topic LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)
The drive is a WK600 series VFD, looking at the modbus manual, I think it is true modbus?
I have attached the modbus details
  • tommylight
30 Dec 2025 15:34
Replied by tommylight on topic Following errors
Rod,
Analog drives with following errors on some axis/joints, so why are you pushing your video that will not help?
How is your software solution going to help for hardware issues???
  • tommylight
30 Dec 2025 15:26
Replied by tommylight on topic Is this QTPlasmac Expected behaviour - Cycle Start and Jog disabled.
From what a vaguely recall, i did some test and had no success of pinpointing it.
This sort of issues are lingering on from PlasmaC where it would run several cuts then stop at random and do nothing, requiring stopping the machine and using "run from here" to continue.
PhillC did find the issue but apparently not the exact source of the issue, the Z axis would not retract to set height and remain waiting, did fix it to a certain extent where it was very usable and happening rarely.
QtPlasmaC has another similar issue, where running a program would start, got to pierce coordinates and wait there indefinitely despite Z axis being at the correct height. This happened in PlasmaC about once or twice in a full days work, on QtPlasmaC happens way more often, sometimes 3 to 5 times per sheet.
All this is way past being important, i did voice my concerns during the development about not implementing useless features into it and PhillC ignored most of it to the point that i recused myself from participating anymore, it was disheartening to see:
-PhillC sabotaging his work by implementing useless features, always, always requested by users with a single plasma machine and mostly no or little experience
-my complaints being ignored, while i had over 15 machines in daily use
-my input about the functionality being ignored completely, like : float switch MUST react and stop the machine even during jogging, this has ruined many torches and would have ruined much more if they did not have magnetic holders.
-UP/DOWN/ARC_ON LED's on the main screen MUST be usable even while not cutting to check standalone THC's like Proma
-seeing all the effort made by PhillC and later you going to waste as PlasmaC and QtPlasmaC got so bloated and so unreliable that i had to stop using QtPlasmaC completely, and actually thinking of slowly moving the remaining PlasmaC machines to my old hal THC stuff, that never fails, ever. Yes, PlasmaC is usable and mostly reliable
-etc etc
-
Sorry Snowwy and Phill, but i have discussed this before with both of you, even on the phone, so to recap, this is not fixable, must be started over.
  • matasbuk
30 Dec 2025 15:23
Replied by matasbuk on topic Retrofitting a 1986 Maho MH400E
You should also measure the voltage drop through the contactor feeding the Indramat, it can be worn out and making a poor connection, failing when under load.
  • rodw
30 Dec 2025 14:51
Replied by rodw on topic Following errors

was this ever resolved? one of the youtubers I watch is currently having a similar problem with a different make of mill but with the same "following" error..
Yes its resolved but its a process, not a simple switch. My video shows  best practice for PREEMPT_RT tuning which should resolve following errors.

 
  • redek3
30 Dec 2025 14:46
Replied by redek3 on topic Retrofitting a 1986 Maho MH400E
   Hi,
I have done a similar retrofit. My machine is a Polish AVIA FND 32. Very similar to MAHO. Analog DC servos with tacho. Servo in velocity control mode with analog +/-10V input. Feedback connected via MESA to LinuxCNC. Position loop closed in LinuxCNC.

I think that if you have "axis following error", there will be a problem with the Indramat driver.
1. If I understand well, this error is triggered when the axis doesn't react properly to the LinuxCNC command. So check analog voltages from mesa to the drives. An oscilloscope would be useful in this case.
2. If signals are good, I think that the problem is with the drivers. It can be partially fried.
In my machine, I had two problems with drives. One was seized bearing in the motor. The driver wasn't able to follow the speed command.
The second time was a damaged signal transformer in thyrystor driver. Axis was slowly moving in one direction. This was a crazy failure, but I am an electronic eng., so I fixed it.
I suggest you to remove the cover from Indramat driver and inspect it visually. Maybe some components are overhited and broken. You can try to publish photos here. Problems with two axes suggest that there is a problem with the circuit common to the whole driver. Check +/-15V power supply.

I would like to help you, but I live too far away.
  • redek3
30 Dec 2025 14:44
Replied by redek3 on topic Retrofitting a 1986 Maho MH400E
   Hi,
I have done a similar retrofit. My machine is a Polish AVIA FND 32. Very similar to MAHO. Analog DC servos with tacho. Servo in velocity control mode with analog +/-10V input. Feedback connected via MESA to LinuxCNC. Position loop closed in LinuxCNC.

I think that if you have "axis following error", there will be a problem with the Indramat driver.
1. If I understand well, this error is triggered when the axis doesn't react properly to the LinuxCNC command. So check analog voltages from mesa to the drives. An oscilloscope would be useful in this case.
2. If signals are good, I think that the problem is with the drivers. It can be partially fried.
In my machine, I had two problems with drives. One was seized bearing in the motor. The driver wasn't able to follow the speed command.
The second time was a damaged signal transformer in thyrystor driver. Axis was slowly moving in one direction. This was a crazy failure, but I am an electronic eng., so I fixed it.
I suggest you to remove cover from Indramat driver and inspect it visually. Maybe some components are overhited and broken. You can try to publish photos here. Problems with two axis suggest that there is a problem with circuit common to whole driver. Check +/-15V power supply.

After all you can buy used drive on eBay. It is not super expensive.

I would like to help you, but I live too far away. Good luck.
Displaying 9331 - 9345 out of 11914 results.
Time to create page: 0.784 seconds
Powered by Kunena Forum