Messages

31

Mach4 General Discussion / Re: Mach4 problems when moving.

« on: July 10, 2018, 03:56:44 AM »

I'm sure the CycleStop is the right way to stop work. The instantaneous stop of the step pulses is incorrect. I have never encountered the error of servomotors at a stop, only in mach3 and mach4.

I agree, however Mach3 requires Feed-Hold then Stop if exact position is not to be lost and this will never change. Mach4 is under development and who knows, future changes may be made to the Stop process to avoid the need for Feed-Hold.

Tweakie.

If you need to keep the exact position - then I use a Feed-Hold.
In any other situation - CycleStop. But it should not cause errors in the servo system of the machine.

It is not clear that the correct operation of the manual movements and the return to the ...

32

Mach4 General Discussion / Re: Mach4 problems when moving.

« on: July 10, 2018, 01:58:41 AM »

Hi,

Sounds like most of the servos havent been tuned yet possibly?

The servomotors are tuned.

Why not increase your decel in tuning?

This laser cutting machine, I need high acceleration and deceleration values, and high PID control of servo motors.

Also depending on how much weight on each axis you might need regen resistors on certain axis depending on how much decel you need also.

Servomotors up to 750 volts have a built-in braking resistor.

Hi Craig, thank you for the constant help.

Hi,
yes you could  set a max de-acceleration in your servo but with a Cycle Stop command where the
pulse stream stops immediately the servo must overrun a little bit and you end up with a following error
rather than an over current or over voltage fault.

I'm sure it's wrong to stop the impulse step instantly. I use other CNC systems, different manufacturers - there are no problems with braking, there are no problems with manual movements and return to cutting.

I don't think CycleStop is the correct way to stop Mach, the sudden cessation of movement is effectively
an infinte acceleration and any servo will fault. If there is a means to cause Mach to de-accelerate gracefully
in response to a CycleStop I don't know what it is.

I'm sure the CycleStop is the right way to stop work. The instantaneous stop of the step pulses is incorrect. I have never encountered the error of servomotors at a stop, only in mach3 and mach4.

I think the correct way is <FeedHold> followed by <CycleStop>.

Craig, watch the video. The laser cutting machine and milling machine are different machines and work differently. If you use a FeedHold, the machine will stop after a long distance, this is not correct.
https://www.youtube.com/watch?v=O0oDtbkMR7A

For the following machines, I want to increase the speed from 30 meters per minute to 50 meters per minute. Problems with stopping, manual movements and returning to the cutting edge will become even greater.
Guys, thanks for trying to help!

33

Mach4 General Discussion / Mach4 problems when moving.

« on: July 09, 2018, 02:53:54 AM »

Hi,
I use Mach4 on a laser cutting machine and ran into several problems when moving. The machine has high speed and acceleration. Servo Drives 400W.
1. CycleStop. During operation, if I need to stop the GCode execution, I press CycleStop, the machine stops very quickly and the servo drives issue an overload error. Is it possible to increase the braking from 0 to 1 second, 2 seconds ...
2. Jogging. I use the keyboard of the computer for manual movements. If you move one axis, then everything works well. If you move two axes at once, then smooth braking does not work, the axes stop abruptly as with CycleStop and servodrivers issue an overload error. Everything works fine on Mach 3.
3. RunFromHere. If you press this button, the correct position window pops up, select the axes, click Move Select. If you need to move along one axis - then everything works. If two of them - it's moving along a strange trajectory and when one of the axes reaches the required position of the first one, it stops very quickly, as in the case of Jogging, with instantaneous braking and an error of servo overload can appear.

Sorry for my English.

34

Mach4 General Discussion / Re: Mach4 3713 + Lua Socket + IPG Laser = Problems

« on: March 28, 2018, 01:30:55 AM »

This script helped me.
local JSON = require ("json")
local a = '{строка Json}'
local b = JSON:decode(a)
print(tostring(b["..."]))

35

Mach4 General Discussion / Re: Lines in the tool path window

« on: March 26, 2018, 01:37:21 AM »

I saw that in Mach 4 version 3713 you can change the thickness of the lines. Thanks to the developers for this feature.

36

Mach4 General Discussion / Re: Mach4 3713 + Lua Socket + IPG Laser = Problems

« on: March 26, 2018, 01:32:51 AM »

I get this line:
{"ver":"1","RIMON":"0.2","RMT":"CW","ROP":"Off","RPP":"Off","RCT":"32.0","RBT":"33.0","RET":"31","STA":"67108864","RID":"YLR-1500-MM-WC","RFV":"32.7.101;2.95;3.7.1","RSN":"R18020185","RCS":"0.0","RPW":"10.000","RDC":"10.0","RDCmax":"99.0","RPRR":"10.0","REC":"1","RMEC":"0","RLHN":"IPG-A15-0044","RDHCP":"OFF","RIP":"10.9.9.10","RMASK":"255.255.255.0","RDGW":"10.9.9.5","RMAC":"D8-80-39-59-D8-95","FST":"10","RPRRL":"1.0","RPRRH":"50000.0","RBAUD":"8","RCFG":"141","WFCFG":"0","WFID":"0"}
It can be of different lengths, but the number of parameters does not change. How do I remove brackets (for unknown string length), divide the string by the symbol "," and move it to the table?
t[ver] = "1"
tRIMON] = "0.2"
t[RMT] = "CW"
?

37

Mach4 General Discussion / Re: Mach4 3713 + Lua Socket + IPG Laser = Problems

« on: March 26, 2018, 01:23:57 AM »

This script helped me.
socket = require("socket")
client = socket.connect("10.9.9.10",10001)
--client:send("GET /monitor.cgx HTTP/1.1\n")
client:send("SDC 105.0\n")
client:settimeout(0.1)
repeat
  --print "read"
  line,err,rest = client:receive()
  --print "read done"
  --if line then print(line) end
  if rest then print(rest) end
until err

print "all done"

38

Mach4 General Discussion / Mach4 3713 + Lua Socket + IPG Laser = Problems

« on: March 23, 2018, 08:44:00 AM »

Hello.
I use Mach4 3713, the computer is connected to an Ethernet network, IPG Laser also connected to it. The laser accepts text commands in one line.
For example: "ABN" - turn on Beam Guide (return response "ABN"), "ABF" - turn off Beam Guide (return response "ABF"). If the command is accepted by the laser, but is not implemented, it returns "BCMD"
I made a module IPGEthernet.lua , put it in a folder "Modules".

Code: [Select]

local IPGEthernet = {}
local inst = mc.mcGetInstance()

package.path = package.path .. ";./Modules/?.lua;"
package.cpath = package.cpath .. ";./Modules/?.dll;"
--package.cpath = "C:/src/Mach4/Modules/?.dll;"
rs232 = require("luars232")
socket = require("socket")

---------------------------------------------------------------
-- IPG -- Ethernet -- TCP/IP
---------------------------------------------------------------
function IPGEthernet.Ethernet(IP, message, len)
local port = 10001
local tcp = assert(socket.tcp())
local data
tcp:connect(IP, port)
tcp:send(message .. "\n")
data = tcp:receive(len)
tcp:close()
data = tostring(data)
if data == message then
wx.wxMessageBox("Command "..message.." executed!")
else
wx.wxMessageBox("Command "..message.." unfulfilled!")
end
--return data
end
--
return IPGEthernet
I made a button on the screen:

Code: [Select]

local A, B, C
A = scr.GetProperty('txtIp', 'Value')
A = tostring(A)
--wx.wxMessageBox(A)

B = "ABN"
--wx.wxMessageBox(tostring(B))

C = string.len(B)
--wx.wxMessageBox(tostring(C))

IPGEthernet.Ethernet(A, B, C)
The script works.
Problem: If I specify the wrong length in "data = tcp:receive(len)", then the script hangs.
Command "STA" (Read Device Status) returns "STA: 4100" (32-bit word), can return "STA: 4294967295", can return "STA: 1".
Question: how to write the script correctly to calculate any length (without knowing it)?
Thanks for the help. Sorry for my English.

39

Mach4 General Discussion / Re: Mach4 PCID to get for LUA.

« on: December 29, 2017, 08:09:33 AM »

It works now: 

Code: [Select]

local testmod = require "mymodule"
testmod = nil
package.loaded["mymodule"] = nil

40

Mach4 General Discussion / Re: Mach4 PCID to get for LUA.

« on: December 28, 2017, 07:25:32 AM »

package.loaded.MyModule = nil -- unload the module so it cant be used
Thank you will test.