Machsupport Forum
Mach Discussion => Brains Development => Topic started by: techie4971 on February 01, 2015, 04:04:44 PM
-
I have hit a wall with setting up my VFD and I need some help. Here is my situation. I have a Delta-E VFD connected via serial Modbus. I use a RS-232 serial 9 pin to RS-485@ 9600bps. My goal is to setup the spindle control using brains to control the VFD. Seems simple enough to do, but I have been working on this for the last two weeks and have gotten only so far. I am currently stuck at the point where I can control the motor On/Off/Fwd/Rev from the Modbus Serial Control Monitor. I have made brains to control the action, but nothing happens. I am lost at the point where the software connection is made to trigger the VFD to start. I have not even attempted the frequency setting at this point. I have included screen shots of my various setup screens so anything out of the norm please let me know. If you have already made a brain for this please give me a piece or your mind or brain.
I am dealing with commands that are -1 Start Spindle, 1 Stop Spindle, -2 Changes Direction, -3 Stops or puts in jog mode ?
I have included screenshots of the following:
Serial Modbus Setup-Ports and Pins settings.
My Modbus Config
My Modbus Tests
Part of the Delta VFD-E Manual
My simple brain
My Complex brain.
-
Additional Attachments
-
And More Attachments
-
Hi,
I'm using Delta E series VFD via serial modbus, but I'm not using REV feature at all. I've attached "mbele_techie_vfd.brn" brain that should work for you (if I did binary conversion correctly :), but I have not tested it in real environment (and I will not have any means of testing it in the next few weeks).
I've also attached screenshot of my serial modbus config and various VFD related brains (zip) I'm using, that you may find useful.
Regards,
Mihael
-
Mihael,
Thank you so much for the response. I went out to the shop to test it out. I didn't have any luck. I set the modbus cfg to match and loaded and enabled the brains. I did the brain editor and watched it go green, but there was no starting the spindle. I check the register with the modbus test and couldn't start the spindle either. I rechecked the parameter 2.01 on the VFD and set it to RS-485. Started again and no action, but it did change the VFD register 2.01 back to 0. So I know that the brain is working. I double checked my config registers and reset the VFD communication to 485 and it changed it back. So I know there is communication there to the VFD that is a baby step from me, but it is forward. I am going go over your brains a little more in detail on tomorrow. Thanks again for the response.
-
I'm enabling/disabling VDF modbus control (p02.00 & p02.01) using button/led on screen via "enable spindle ctrl.brn", but you could do it when starting stopping. I've attached updated brain that uses serial modbus cfg#2 (you'll have to configure it as address 513, 1 register, output holding) to set p02.01 to 3 when starting, 0 when stopped.
I must say I've never had an issue with VFD resetting params on it's own - btw default value is 1, not 0, so either manually setting the p02.01 to 3 failed, or something changed it back to 0. Check that you do not have any other modbus related brains running that can interfere, and test manually using modbus serial control monitor.
Good luck!
-
I checked my parameters on the VFD and they are resetting when your Brain is enabled. So that means I can rule out any modbus connectivity issue. I am getting some response from MACH3, not what I wanted but it is something I can work with. I tried downloading the brain above and it appears to not be attached or is corrupted. I am going to review my parameters again on the VFD and go test through the brains you provided.
-
The first brain I've uploaded, it writes decimal 18,34 or 1 to cfg#1 which is wrong #cfg if your serial modbus settings are the same as in screenshot you've posted earlier. "corrupted" brain did the same, and used cfg#3 to write p02.01 (not cfg#2 as I wrote). I've attached the corrected brain.
To perform test, first, manually set p02.01 to RS485, and then, using serial monitor, write decimal values 18, 1, 34, 1 respectively to decimal address 8192 (2000H) to test if those values are correct. If that works as expected (spins forward, stop, spin backwards, stop), manually set p02.01 to 0 (digital keypad), and using serial modbus monitor, write decimal 3 to decimal address 513 (0201H). Manually check if the p02.01 value on VFD is correctly set to 3 (RS485). If that worked, perform first test again. If all good, check serial modbus configuration, disable all #cfg but cfg#0 and cfg#2, make sure that cfg#0 is set as in the screenshot you've attached(port1, address 8192, registers 1, output-holding), and that cfg#2 is set to the same values as cfg#7 in the screenshot I've attached (port1, address 513, registers 1, output-holding). Disable all brains but the one attached, view that brain. Outputs 1 & 2 should be inactive and modbus output for MOD:1-P:0 (address 8192) should be 1 (stop), and for MOD:1-P:2 (address 513) should be 0 (digital keypad). Enter M3 command in MDI. Modbus output MOD:1-P:0 should read 18, and MOD:1-P:2 should read 3, and spindle should run forward. If that works, check M5 and M4 commands. If any of these steps fail, it should point out where the problem is. Brains I'm using will probably not work out-of-the-box for you, since my screen set is totally customized...
-
Here is what I have. I set the VFD 2.01 to RS-485 and tested with MODBUS Test 18,1,34,1 and I get forward, off, reverse, off. I then set 2.01 to 0 then tested 513 to 3. I checked the VFD and it changed. I then tested 18,1,34,1 and it works.
I loaded your brain and then disabled all other brains. I then viewed the brain. I then hit the spindle button on the screen and all MODBUS outputs registered correctly. Nothing turned on brain looks correct. I rechecked serial MODBUS config and it matches your settings with parameters. I then when into serial MODBUS test. I got nothing when I retested. I thought this might be some sort of communication problem. I checked P2.00 and it was 0, then checked P2.01 it was zero. I then set P2.00 to 4 and P2.01 to 3 and then 8192 - 18,1,34,1 it works. So I toggled P2.00 from 4 to 0 and it kills all communication.
So I made a brain based off of yours figuring the order might make a difference. So I made a Brain that set the following when active 512-4, 513-3, 8192-18. I saved, reloaded, enabled then viewed that Brain. It looks to be sending the correct signal. I manually check the VFD and when I do I get P2.00-0, P201-0. When I set them manually to p2.00-4 and p2.01 to 3 they immediately go to 0 on both.
I don't know what it could be. I test in serial MODBUS test and it works and the second I enable the brain it is like it is locked at 0. See 2.00 enables rs-485 and with it off it is dead. Somehow the VFD gets set to 0. I checked the parameter book and nothing seems to apply. I don't think it is the brain. I mean it looks like it should work. I test the parameters and they work. Enable the brain and locked out. It is like it is some sort of safety deal. I set to not use the reset and still locked out. I am wondering if when the brain is enable the first command the VFD gets is wrong and it defaults to off. Like it is being misread and decides to switch to manual operation. Have any idea if this is a parameter setting or something I missed in MACH3?
-
my other views
-
Let's focus just on fwd/rev/stop.
While the brain that sets p02.01 is enabled, manually setting that param on VFD will not work, since as soon as you set it, the brain resets it. It will lock p02.01 to 0, while outputs1&2 are inactive.
When you say:
I then hit the spindle button on the screen and all MODBUS outputs registered correctly. Nothing turned on brain looks correct.
I'm not 100% sure I know what you mean. I'm not native English speaker, and my screenset is completely custom, so I'm not sure which button you mean, and how "nothing turned on" is correct. That's why I suggested using M3,M4 and M5 commands via MDI. If the button you're pressing is "Spindle CW F5" on standard screenset, brain view should show a change of output1 state and the outputs of modbus terminators should read MOD:1-P0: 18.0000 and MOD:1-P2: 3.0000
Please re-check that.
I found (but I may be wrong) that the order of brains doesn't matter if you're not using the output of first brain to feed the input of second brain, which output is used as part of the input of the first brain (some sort of state lock) - and that the results of that are not consistent/dependable on. You can look at the brain as switch, it just reacts to input states and holds the output state in regards to processing done on those input states (regardless of the input state, active or inactive). Same with the modbus, it's just a "virtual memory", like a table with cells that hold some value, either Mach or VFD can read/write into those cells.
To verify that there is no error in communication, please check the value of the VFD param 09.02 "Transmission fault treatment" - it defaults to 3 ("no warning"), so set it to 2 ("warn and coast to stop") - the error, if there's one, will be displayed on digital keypad. I've noticed that you have "Use RTS for transmit" enabled on serial modbus config screen. I'm using RS232 to RS485 converter that does not need that option enabled, you may try disabling it also.
I don't quite understand what you mean by:
I set to not use the reset and still locked out.
I presume that by "locked out" you mean that you can't change the p02.01 manualy, but what you mean by "to not use reset" ?
The only things that come to my mind in regards to Mach3 or VFD settings are that the outputs 1/2 may be used by some other Mach3 feature you have enabled (mine are configured as active, port 0, pin 0, active low), and the VFD param p02.01 is being set by some VFD input - config group 04.xx (I've never changed those, all are default)
-
I am still having trouble getting the VFD to respond to MODBUS Commands. I have issued the M03,M04,M05 commands and the spindle does not turn. I believe that the brains are functioning correctly. When the M03 command is issued I see the brain change the outputs to MODBUS 4,3,18 as directed by you brain config.
I set the parameter 9.02 to 2 and no errors were displayed. I also ran the VDtool from Delta and pulled all the parameters. I also toggled the RTS check-box and nothing changed.
When i mention that I am locked out means that once Mach3 is running the commands at the VFD keypad stay locked at 2.01 = 0, 2.01 = 0. They can not be change with Mach3 3 running. I can change them when testing Modbus but when I close the test they go back to 0. I am wondering if Mach3 or something else could be setting them to 0.
I went into Ports and Pins and matched your settings 0,0,Active Low. Still no change.
I know computer control over the VFD works because I used the VDtools software to control the motor. I know that the modbus test is working in Mach3 because I can turn on the spindle. As soon as I stop it goes to back to 0 for 2.00 and 2.01. I have made so many changes to both the VFD and Mach3 I need to attach the images and parameters.
-
Here are the parameters pulled from the VFD after I test and close MACH3.
-
Here are the revised ports and pins configurations.
-
Here is the MODBUS and Brain operation.
-
When i mention that I am locked out means that once Mach3 is running the commands at the VFD keypad stay locked at 2.01 = 0, 2.01 = 0. They can not be change with Mach3 3 running. I can change them when testing Modbus but when I close the test they go back to 0. I am wondering if Mach3 or something else could be setting them to 0.
...
When i mention that I am locked out means that once Mach3 is running the commands at the VFD keypad stay locked at 2.01 = 0, 2.01 = 0. They can not be change with Mach3 3 running. I can change them when testing Modbus but when I close the test they go back to 0. I am wondering if Mach3 or something else could be setting them to 0.
That's normal behavior if the brain is enabled. Try disabling the brain, change those params via modbus test feature and/or manually via VFD keypad while mach is running, and see if they change back. If they do not change back to 0, then it's the brain who is changing it back to 0. Prove that by enabling the brain and check the params again. If they do change back to 0 while the brain is disabled, then something else changes them - but that's highly unlikely.
Brain constantly(every 250ms in your case) writes 0 to p02.01 when the outputs1&2 are inactive, or 3 when either of those two outputs is active.
I've attached screenshots of my config - please compare to your settings. There are differences, but I'm not sure if they matter (eg. serial timeout, outputs active low settings, motor output-spindle enabled, spindle setup-motor control...)
When debugging, it's important to change only one thing at a time and reduce the number of variables to minimum.
You could test if you can change VFD param via modbus using brain: disable all brains, create and enable brain that uses some onscreen led as input and writes something to some VFD param, for example:
[input LED: 815 - softlimits on]->[no-operation]->[formula: a]->[modbus: MOD:1-P:4 (create cfg#4: address 776 - p03.08/fan control)]
clicking the softlimits button should change the value of fan control param. If that does not work, step back, and try it manually using serial modbus test feature.
-
I have done a few tests and I can manually set the VFD P2.00 to 4 and P2.01 to 3. I can operate Delta’s VD tools and the commands stays in the VFD. I load Mach3 and instantly the parameters both switch to 0. Which should be normal with the brain enabled. I go to brain control, disable all brains, and close Mach3. I then set the VFD parameters again to P2.00 to 4 and P2.01 to 3 and open Mach3 and once again the settings on the VFD are set back to 0. I confirm from brain control to that no brains are enabled. They are not enabled. I can open the serial Modbus test and set P2.00 and P2.01 and spin the motor. Once I close down the test window, they are set back to zero.
My tests review:
VFD parameters are set P2.00 to 4 and P2.01 to 3
Parameters remain set using and closing VDTools.
Mach 3 is launched with no brains enabled and VFD is set to P2.00 to 0 and P2.01 to 0
I cannot seem to find anything that is causing this activity. I think it has to be something in Mach3, because Delta’s VDTools has no issues.
I believe that the reset to 0 is the reason that I cannot issue commands from Mach3 brains. Is it possible that the VFD has disabled the RS-485 connectivity by something when Mach3 starts up? I changed the communications port to 4 and same issued occurred.
Could the VFD be resetting the parameter to 0 when a communication timeout occurs. Like VFD times out before command is issued by Mach3. Like Mach3 opens port but VFD is no longer waiting and defaults to 0.
You are correct there is very little changes in your configuration when compared to mine. I went ahead and matched your configuration to mine assuming that one of those little changes could have made some major difference. I was thinking that the timeouts on the VFD could have expired on the VFD and then it goes to manual operation. I don’t know how Mach3 could be sending the information to disable P2.00 and P2.01.
I tired the following brain suggestion and nothing happened. This is what is pointing me to a possible VFD timeout or command failure issue.
[input LED: 815 - softlimits on]->[no-operation]->[formula: a]->[modbus: MOD:1-P:4 (create cfg#4: address 776 - p03.08/fan control)]
I think my next steps for testing is to take out all serial Modbus configurations and set the VFD P2.00 and P2.01 and open Mach3 and see if the changes occur. I think if I can determine if it is Mach3 or the VFD I can focus on the problem area. If the problem still occurs after removing the serial Modbus configuration. I will remove and reinstall Mach3 and start over.
I am open to any suggestions if you have any you think I should try.
-
It's a long shot, but try using modbus address 0 instead of 1 in brain terminator. It doesn't make sense, but I've just checked, and all my original brains use address 0. I think that address "0" means that mach will "broadcast a message" to all modbus slaves, but there can also be missmatch between indexing systems, where one system uses "0" based indexes, and another "1" based indexes...
Mach 3 is launched with no brains enabled and VFD is set to P2.00 to 0 and P2.01 to 0
This is the key, it shows that something in mach is responsible.
Maybe before taking out all the params, you could try turning off "ModBus Run" option on "ModBus Configuration" screen and/or disabling "ModBus InputOutput Support" on "Ports and pins" screen. This would show if the modbus plugin is doing this or some other part of mach.
Before uninstalling, try a fresh install on another PC, if you have that option. When I got the VFD, I did all the serial modbus experiments with plain mach3 install on my notebook PC, just to figure how all this works, and then copied relevant settings to the shop PC.
If you do uninstall, be sure to backup your xml file and all the custom stuff.
I'm running Mach version R3.042.020.
-
First thing I did was change the modbus address to 0 in the brain terminator. No change on on the VFD.
The next thing was to turn off the "Run Modbus" in the Modbus configuration. I could set the VFD manually. I quit Mach3 and re started it and there was no change to the VFD settings. So I need modbus run check to enable the modbus. I then set modbus run and the VFD setting reverted to 0 on p2.00 and p2.01.
I went into ports and pins and then disabled "Modbus Input/Output Support" , I was able to set the VFD, but once again it reverted back to 0 when "Modbus Support was checked"
I then got another laptop running 32 bit and downloaded and installed Mach3 and setup the comm port to 4 and matched your settings for the baud rate. I set the VFD on p2.00 and p2.01 to 4 and 3. The VFD keeps the settings and once "Run Modbus" or "Modbus Input/Output Support" is checked the VFD goes to 0.
I also tested with serial modbus and it of coarse worked. After I entered 512 to 4 and 513 to 4 and 8192 to 18. Once I close the comm port, I noticed the VFD sets to 0. When I open the comm port I have to enter them in to turn the spindle.
I tried the attached brain. On failure I changed the terminator to 0 and received the same response.
Something is messing up on either the VFD or Something from Mach3 serial control is throwing an error.
I know this is a lot to ask. Is there a way you can use Delta's VDTools to read the parameters from your VFD and send me the file for comparison.
I think that somehow the VFD is getting some sort of timeout or is wired incorrectly and by default sets to 0 for manual operation.
I am using a Delta VFD-E. I have manual controls for VFD on/off, Fwd/Off/Rev, Emergency stop. There are two switches set to ACI and PNP.
I attached the pictures of VFD. I have to take off the keypad to install the cover.
-
Sorry I'm a little new to this thread and issue, but where is the modbus connections and it looks like your switched for current but supplying 0-10v
I just bought a Delta EL and have just started looking into how to implement it for my needs, so am viewing your thread with interest.
Just that what I see in your photo made me scratch my head. Maybe I'm missing something from what I read in the document that came with my drive!
Hell I might be all wet, as I just put power to it to see if it at least spins my motor. It does... now to figure out how I want to control it. So I hope you get your issue figured out.
-
I know this is a lot to ask. Is there a way you can use Delta's VDTools to read the parameters from your VFD and send me the file for comparison.
It's not a problem. I'll do that on Saturday or Sunday. Can you post a link where I can download the application ? In the meanwhile, here's the list of params I've changed (IIRC) from default to custom (mostly unrelated):
00.03=3, 00.05=60 (all unrelated)
01.00=400, 01.01=200, 01.09=1, 01.10=1 (all unrelated/not applicable)
02.00=0, 02.01=0, 02.04=1 (not applicable/related to digital keypad)
03.08=2 (unrelated)
09.01=3, 09.02=?, 09.04=6 (modbus settings)
As you can see, there's not much here...I wanted to change a lot more, but I could not get detailed info on params I was interested in.
I am using a Delta VFD-E. I have manual controls for VFD on/off, Fwd/Off/Rev, Emergency stop. There are two switches set to ACI and PNP.
I thought that you're using digital keypad accessory like I am. I do not have any auxiliary inputs / external terminals connected (just RJ connector) and I have no experience with that wiring method or related params.
If you're using ext terminals for manual operation, then the values for p02.01 should be 1 or 2 for manual operation and 4 for RS485 control (0=digital keypad), check the manual for p02.00 settings too.
Once I close the comm port, I noticed the VFD sets to 0
How did you noticed that without digital keypad display ? By running vdtools app ?
I then got another laptop running 32 bit and downloaded and installed Mach3 and setup the comm port to 4 and matched your settings for the baud rate. I set the VFD on p2.00 and p2.01 to 4 and 3. The VFD keeps the settings and once "Run Modbus" or "Modbus Input/Output Support" is checked the VFD goes to 0.
Notice that params go to 0, not to 1, which is the default value for those params, and which you should use since you're not using digital keypad. This means that something is setting those params to that value, and that it is not a fallback in case of error (actually, in case of error param value should not be changed).
It may be that we've missed some simple step in configuring mach for modbus since you experienced the same behavior with fresh install, or it can be related to the usage of external inputs and related VFD params (have you tried disconnecting them, backup/reset the vfd params and start from scratch ?). Have you also tried toggling RTS after changing the modbus address from 1 to 0 ? I'm using rs232 to rs485 converter http://www.ebay.com/itm/RS232-RS485-RS-232-to-RS-485-Converter-Port-Powered-/231331240225?hash=item35dc6a9921 (price went up x2.5 since I bought it) which does not need that option, but since you've mentioned port number 4, I presume you're using USB to rs485 converter, and I've read that people had issues with RTS and those converters.
-
Here is the link to VDSoft program is located at http://www.delta.com.tw/product/em/drive/ac_motor/download/software/Delta_VFDSoft%20V1.48_20130903.zip
Yes VDSoft will let you read all parameters from the from drive. I posted up a previous txt file.
I have a lathe that I can run in by hand or by CNC. I can give up manual operation. I have limited space and have to take off the keypad when covering the VFD. I have the keypad installed. I also included recent photos of the VFD and RS-485 connector. I like yours much better.
I am wondering if the manual configuration is the issue. Maybe the VFD senses the manual operation and goes to 0 from the VFD firmware. I wonder if this could be the fall back option you mentioned. Which doesn't make sense because VDSoft can control it with no issues, but that might be special to VDSoft.
There are two switches on the VFD AVI/ACI and NPN and PNP the documentation is lacking on what these are called and what they do. I just looked at the book and switched them to match the wiring.
On my old laptop I have a USB converted. On the desktop, I have a physical serial port. I did toggle the RTS on and off and in modbus test it worked correctly. I just left it off.
Ya-Nvr-No I am trying to run the motor direction and RPM with the Modbus configuration. I looked at the Delta-EL series manual and they are the same. You should be able to control the EL with the same configuration.
I will send out my VFD parameters and if you could check your switches on the VFD that might give me a clue on the issue. I will research removing my manual controls.
-
VFD params export is attached. Default switch states are NPN and ACI (I never changed them), just like you have them on the picture.
I do not have heating in the workshop, and when temperatures are expected to go below -10*C, I disconnect VFD and take it home. I can't just disconnect rs232-rs485 converter because it's buried in the control box together with the PC and directly connected BOB covered with shielding plate, and all the cables have connectors that match control box case connectors...so I can only do tests in the workshop, and it's very cold these days.
-
I did a comparison between the our VFD parameters. Attached is the excel, I highlighted the parameters I am going to look at. A large amount of the parameters are the same. There are some variations due to voltage and frequency but mostly me match up.
I installed a shop heater a few years ago. It was worth the money, but at zero it can not keep up and costs a small fortune to heat up and keep warm. I no longer live in a place that gets colder that -6. I have been meaning to ask where do you live? I am in Dallas,Texas. I travel for work all over the world working in large data centers and on computer network systems.
I appreciate you taking the time to help me solve this problem this has been stressful due to the amount of investment I have put into my equipment. I checked the MACH3 version and I have Mach version R3.043.66. It is the newest downloaded version. I have an older machine that is using the older version. If I can not sort out the parameters, I will dig out that machine and set it up.
-
In my case, params 02.00 and 02.01 depend on the "modbus control" led state when mach is closed, and I may have changed param 09.08 accidentally.
I live in Zagreb, Croatia, I'm self-employed computer programmer, and I really do not like to travel :D
I know how frustrating it can be... I have VFD noise issue... :) People on this forum have been very kind to me, and I like to return that if I can.
-
Here is the update on the Delta VFD-E drive. I have been down with the flu and bad weather hit Dallas last week.
I was able to get the brain active and signals going to the VFD. I adjusted 09.03 which was the timeout detection. I also adjusted 09.07, which is response delay. I had the brain on and entered the motor command. To my surprise the motor turned, but only briefly. Adjustments in those two values changed the amount of time the motor turned. I thought this was a positive sign that the communication to the motor worked, but the motor would spin then stop randomly and also change direction. I thought the communication delays allowed the motor to turn, but the actual signals stopped the motor.
I looked at the VFD display and it was flashing as the communication hit. I looked at P02.00 and P02.01 and they flashed between 0 and 3. I then decided it was time to remove the motor, VFD, and start over from the beginning.
I used the VDSoft tool to pull the motor parameters and save the settings in a CSV. I then decided it was time to wipe the VFD of all setting and return to factory default with parameter 00.02 to 10. The VFD made a beep and flashed the display and I knew it returned to factory default.
I used VDSoft and entered the motor parameters. I exited VDSoft and physically checked the values on the VFD display. Once I knew they were correct, I started MACH3 and sent the M03 command. To my surprise, the motor started up and worked perfectly. I now have on and off control. All I can think of is that the VFD had some internal parameter conflict. Even viewing the parameters in VDSoft and matching them had no change to the problem.
My next task is to control the speed and display the RPM. I have been working on the brain for that. I have included pictures and the brain for review. I am looking on the best way to control the motor speed with the S commands. I was able to get the motor to increase and decrease speed, but I have not found out the DRO field to display the RPM and bar graph to the side.
-
I'm glad you got it behaving :)
I suggest that you keep the brains for various VFD features in separate files. Once you got every feature working you can redo it in single file, if that's your preferred way.
To set the spindle speed, use the value from "Spin RPM - Ovrden DRO", this DRO contains actual commanded RPM including override. My spindle has max 24000RPM , and max freq 400Hz, so, for each Hz, RPM changes by 24000/400=60 - that's also my user-defined coefficient (p00.05) . To get frequency value from RPM, divide RPM by this coefficient. Frequency value for address/param 2001H can have two decimal places, so desired frequency should be multiplied by 100 to get the value that should be written. If you check my spindle speed brain, you'll see this formula (I think you can actually use that brain, just change the coefficient(60) to a value specific for your spindle).
I do not need to read actual spindle speed/freq from VFD - I've connected digital display to VFD with ribbon cable and mounted it outside the VFD enclosure, so I can see it. When I was thinking about doing it, I remember that there were some "logic" problems, so I just abandoned the whole idea.
I have two hints, first, check the Config/Spindle pulleys..., you can limit min/max RPM there (I have it set to min=4200,max=24000,ratio=1), and second, be careful when using "run from here", this feature does not execute S commands in g-code program (RPM will be read from DRO) and be sure to check "Start spindle" checkbox on "preparation move" form - it is unchecked by default (but once you check it, it stays checked).
-
Hello, im intrested with Mach3 Brains settings for Delta VFD EL can you tell if this issue have been fix?
-
So the main issues that I encountered was that the Delta VFD needed to be reset to default. Once it was reset, the communications starting working correctly. I would suggest resetting to default on the VFD and then setup the parameters to match what was listed in this thread.
I do have the MACH3 brains working and controlling the Delta VFD.
-
Can you provide your settings I'm or some assistance, A video would be nice, if its possible.
-
After searching the net for several hours, these are the settings that work. The USB to RJ11/RJ45 utilized from factorymation.com Part number -- IFD6500 Delta Communication Interface, USB-to-RS485 converter ** was VFD-USB01** Cost $43.00. Also, please adjust your comm. port for your setup.
(http://)