Hello Guest it is March 29, 2024, 09:33:21 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - techie4971

Pages: 1 2 »
1
Brains Development / Re: DELTA-E VFD MODBUS BRAIN Help Needed
« on: February 07, 2017, 04:44:37 PM »
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.

2
Brains Development / Re: DELTA-E VFD MODBUS BRAIN Help Needed
« on: February 26, 2015, 10:34:54 AM »
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.

3
Brains Development / Re: DELTA-E VFD MODBUS BRAIN Help Needed
« on: February 12, 2015, 10:39:07 AM »
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.

 

4
Brains Development / Re: DELTA-E VFD MODBUS BRAIN Help Needed
« on: February 11, 2015, 03:07:07 PM »
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.
 


 

5
Brains Development / Re: DELTA-E VFD MODBUS BRAIN Help Needed
« on: February 11, 2015, 09:36:48 AM »
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.



  




 


6
Brains Development / Re: DELTA-E VFD MODBUS BRAIN Help Needed
« on: February 09, 2015, 04:02:54 PM »
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.

7
Brains Development / Re: DELTA-E VFD MODBUS BRAIN Help Needed
« on: February 08, 2015, 12:01:06 AM »
Here is the MODBUS and Brain operation.

8
Brains Development / Re: DELTA-E VFD MODBUS BRAIN Help Needed
« on: February 07, 2015, 11:51:09 PM »
Here are the revised ports and pins configurations.

9
Brains Development / Re: DELTA-E VFD MODBUS BRAIN Help Needed
« on: February 07, 2015, 11:48:19 PM »
Here are the parameters pulled from the VFD after I test and close MACH3.

10
Brains Development / Re: DELTA-E VFD MODBUS BRAIN Help Needed
« on: February 07, 2015, 11:29:44 PM »
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.


Pages: 1 2 »