Huanyang Plugin

[ger21]

My VFD is from solar.jean, but mine is 2.2kw

[pupdogg]

I just heard back from solar.jean who was kind enough to point me to a Chinese video showing RS485 communication with this drive. From the looks of it, their communication method uses ASCII 8N1 vs RTU 8N1. Video link: https://youtu.be/30TzoQUEsqU. You can see at 3:07 his ASCII 8N1 setting in the proprietary software. I will give that a shot tomorrow and see if there’s any luck. I highly doubt it but it’s worth a try.

[Dan911]

Hi Dan: thank you for your prompt reply. As per their manual (screenshots attached) I modified PD011 to be 140 (8400RPM), and PD072, PD073 to be 140 and 300 respectively. I also changed the plugin lower limit to 8400, saved the settings/profile and restarted UCCNC with not additional luck. I have already once RESET the VFD to factory settings already prior to trying all of my efforts.

pupdogg, put pd11 and pd73 back to 120 and set your minimum RPM in plugin to 8000 to test. When UCCNC starts it sets your rpm to your minimum rpm you set in plugin and if it's lower than these settings (pd11,pd73) it's not going to start. I do think there may be another problem based on the Serial Port data you posted but this will be a problem for sure.

PD163 1 Vfd address (here 1)
PD164 1 Line Speed(1 for 9600 bauds, this must match com port settings)
PD165 3 (here 8N1 RTU)

[Dan911]

Your HY parameters you posted show PD011 and PD072 = 120 (7200rpm)
Your UCCNC Profile you posted show minimum rpm set to 6000rpm.

On UCCNC start it sets your rpm to 6000 and since you have VFD min set 7200 it could be stopping the plugin from starting.

Dan

[pupdogg]

Hi Dan, I tried both of your suggestions and still no luck! I don't believe the problem is with your plugin...I'm thinking it's between the USB->RS485 dongle and the VFD. I went ahead and ordered 2x additional dongles from Amazon to try and see if I can get it to work. I tried using latest version of SpindleTalker but it also said "VFD not responding". Then I whipped out my RS232Analyzer software to try and see if I could send it raw HEX commands as highlighted below. The software was sending commands just fine, they just weren't getting acknowledged and nor there was a response. So, getting these cheap dongles is 1 way to isolate my issue. If it still continues, then it's time to showcase my baseball bat! Will keep you posted.

Code: Select all

Start CW    01 03 01 01 31 88            (VFD address 01, write control data 03, data length 01. data 01, checksum 31 88)
Start CCW   01 03 01 11 30 44
Stop        01 03 01 08 F1 8E
Set Speed   01 05 02 9C 40 D0 3C         (05 is write frequency control data (2 bytes))  9C 40 Hex =  40000 or 400.00 = 24000rpm


[Dan911]

Hi pupdogg,

My 2 suggestions were actually referring to the same thing trying to make first more clear, and it was more of a heads up. You shouldn't
set min rpm in plugin lower than min rpm(frequency) set in VFD parameters.

It was clear to me from your first post with Serial Port monitor data you posted that there was a communications problem, I mentioned several times throughout thread. What has yet to be determined is the cause and hopefully it's the RS485 converter. These cheap dongles are a hit or miss, there great for testing but if RS485 is going to be your permanent control it will probably be wise to look into a quality RS485 converter.

I also keep a baseball bat in my toolbox for tough fixes and was used several times...lol

Dan

[pupdogg]

Well, well, well...so guess what do I find out today! Nothing wrong with the Huanyang VFD...it was the god $#*% JBTek USB dongle!!! Yes, the same USB dongle sold on Amazon at http://amzn.to/2oN8iiG. But as you (Dan911) stated, it is definitely a HIT or a MISS since they are so cheap...1 of the 2 that I received today worked right out of the box. It seems like the issue with the bad one was that upon opening the COM port, it was sending data just fine but was not receiving any response back.

So, to help anyone else that might incur this exact same issue in the future, an easy way to tell if your USB dongle is bad or not is to download yourself a FREE copy of Serial Port Monitor and monitor the COM port while using UCCNC...if all you see is data being sent from the port and no response, then your USB dongle has issues. But hold on a second...I also learned something new...as you're monitoring this COM port, if you do see a response but your VFD still does not work...then check to see if your response string starts with a 01 or a 7F...if it starts with a 7F, that means you need to reverse the polarity of the A+ and B- communication wires. An easy way to do that would be at the VFD since the screw-terminals on the USB dongle are too darn small. Moving forward, I will try and look into what can be to fix a bad USB dongle. Attached you will find 3x pics of 1) my VFD with communication wires, 2) the good USB dongle (connected to PC) and 3) the bad USB dongle (taken out of its plastic casing).

[Dan911]

Thanks for the update! Happy to see you got it working.

Dan

[laki]

Hello,
I am the new user of UC300ETH motion controller and UCCNC software version 1.2047.
The computer works under Win XP sp3.
Everything works properly except for a spindle connection.
For connection I use RS485 and Huanyang plugin ver. 1.0012. UCCNC reports an error (UCCNC has encountered a problem and needs to close) when VFD is on. If I start UCCNC with VFD off, it is normally loaded and running. If I turn on the VFD after a few seconds, the error reappears. Although a reported error, the connection between the VFD and UCCNC works, (I can turn the spindle on and off and change the speed). The Sact field does not show a change in speed. The field with the reported error remains on the screen.
I set the parameters for VFD and plugin according to the instructions from the plugin (attached pictures).




For Mach3 I use royaumedeole mach3-plugin-for-huanyang-vfd 1.7.1 and everything works properly.
Can you help me, please?

[Dan911]

Hi Laki,
There was another user having your similar problem with UCCNC crashing and went back to read thread but it was never posted what or if solution. I suspected editing labelnumbers for UCCNC fields
improperly was the cause but this was never confirmed, I am as eager or more to determine what your problem is.

You will NOT see any change in Sact field unless you edit field# and suggest not doing so until you find cause of crash. If you are using the UCCNC default screen there is NO reason to edit any Textfield labelnumbers with Amp disabled.

I suggest deleting the HYplugin from plugin folders and if you attempted to edit any fields than reinstall 1.2047. If problem persist PM me your email address and I will send you a different HYplugin to try.

Dan