Hi @ all,
I decided to switch my CNC from a flimsy GRBL controlled one, to a more solid one.
For this, I "dared" to buy a NVEM, but the V2 (newer version, driver seems to be not compatible with V1.1)
My setup is Mach3 + NVEM v2 + 3*DQ542MA + 3*Nema23 + 1.5kW VFD/Spindle
Up till now, I found a couple of problems, and it would be great if someone can double-check with a V1.1 if these are there too (and maybe provide some insight on how to mitigate them)
- the controller will only move at 2/3 (66%) of the specified speed. If F1000 is specified in the g-code, Mach3 will output 666mm/min, if F3000 is specified, Mach3 will output 2000mm/min. This is not related to the motor settings, since its displayed at "unites/mm" in the Feed-Section of Mach3. So the controller moves slower that what is specified. Using a DB25 BOB, I'm able to achieve the specified speed with the same settings.
- DHCP is not working 90% of the time. The controller will not reliably obtain an IP from a DHCP server, regardless which kind of router used. In addition, the LAN-port is not correctly isolated from the power supply, since powering the controller with 24V will also have 24V on the LAN port, basically common ground (which fried a LAN port of my expensive AVM router while trying to use DHCP)
- Slow Zone setting for Soft Limits is not working. The Slow Zone parameter seems to be not recognized at all, which causes the machine to hit the soft limit at full speed, and by doing so exceeding the soft limit since the machine needs more time to slow down.
- When soft-limit is hit with G-Code, coordinate system is messed up: When hitting a softlimit with G-code, the controller will stop the movement as supposed to, but after that the coordinates are no longer correct. Using G-code, it will only allow movement for small increments, always displaying that softlimit is still exceeded, even if not. Using keyboard, movement is ok. The controller will not recover (even when manually zeroing) until complete power cycle or reset and homing again
- Sporadic disconnect, NVEM no longer reachable: after about 90 minutes the NVEM looses connection. Mach3 displays "device not ready", and NVEM is no longer recognized, plugin-config displays "unknown". LAN port still shows activity, LED is flashing. Only a power cycle of the NVEM does fix this. Then, even without restarting Mach3, all is working again
- Single block mode is not displaying correctly: When using single block mode, the selected line is not displayed. The line cursor is jumping through the g-code, not highlighting the current line or the next which is executed.
- Probe command G31 not working as supposed to. When using G31 to probe a surface for autolevelling, the controller will hang after 5 - 10 G31 commands, not executing any more G-code. Sometimes it's even skipping lines of G-code which are after the G31 commands. NVEM will only recover after a reset, only working for a couple of G31 again. In addition, for some G31 probing commands, even when probe is hit (digitize LED lit in Mache) the probing cycle will not stop until the maximum depth is hit
- G31 probe command not working at all.The Mach3 G31 probe command is not executed correctly.The controller will move the axis specified in the G31 command, but will not report back the coordinates at which probe was triggered.So there is no probing functionality, since offset cannot be set. This might be the worst problem so far.
Rather long post... but replies are appreciated never the less :-)
Thx & regards,
David