[A_Camera]

Dan, there is an ongoing discussion on CNCdrive forum about this. I also thought it was fixed, but now after a few more minutes of thinking perhaps it is not possible for UCCNC software to take care of this for anything else than itself and for the macros since that is under the control of UCCNC. Everything else, like a plugin, is actually independent of it and must take care of the culture info on its own. So I think when Balázs answers my last post, his answer will be this. In other words, I think you need to add those two lines at the very beginning of the plugin.

[Dan911]

I will definitely read the on going discussion after this post. I addressed it with the zip file for Kelevra83 and hopefully he replies back with success and then I will post a revised version.

Thanks for your help,
Dan

[Kelevra83]

I will definitely read the on going discussion after this post. I addressed it with the zip file for Kelevra83 and hopefully he replies back with success and then I will post a revised version.

Thanks for your help,
Dan

Hey guys,

I will give this a shot as soon as I get home from work.
The culture info issue makes sense though since I'm using a german windows.

Regards

//edit:

Here's an update guys.
I've gotten the Plugin to work now and it performs beautiful, the only slight negative is a delay when adjusting spindle speed on the fly but i can live with that.
The new zip you uploaded didn't work though Dan. It causes the relay of the VFD to trigger but it didn't set rpm.
The key thing to get it working was that i had to change windows to english and all the problems went away magically.
Currently i'm running it on 1.2029 with the Plugin version 1.0006 and so far i havent expierienced any crash at all.

Thanks alot to everyone for the help and the hints, and maybe Dan can use some of the information to fix this little thing with the next update.
If i left anything unclear feel free to ask.

regards
Patrick

[Dan911]

Hey guys,

I will give this a shot as soon as I get home from work.
The culture info issue makes sense though since I'm using a german windows.

Regards

//edit:

Here's an update guys.
I've gotten the Plugin to work now and it performs beautiful, the only slight negative is a delay when adjusting spindle speed on the fly but i can live with that.
The new zip you uploaded didn't work though Dan. It causes the relay of the VFD to trigger but it didn't set rpm.
The key thing to get it working was that i had to change windows to english and all the problems went away magically.
Currently i'm running it on 1.2029 with the Plugin version 1.0006 and so far i havent expierienced any crash at all.

Thanks alot to everyone for the help and the hints, and maybe Dan can use some of the information to fix this little thing with the next update.
If i left anything unclear feel free to ask.

regards
Patrick

Hi Patrick,

I'm glad the plugin is working for you. The Kelevra83 zip file I uploaded for you was slapped together quickly and was meant to see if you comp stopped crashing and was a culture info class problem, not to control your VFD.

Just a heads up Patrick, that version your using has the UCCNC spindle pulley's implemented in it so make sure you keep spindle pulleys checkbox unchecked, otherwise it will set your frequency to the ratio of pulley selected in UCCNC.

Also I haven't really fully tested other than with a Serial Monitor so consider yourself a beta tester...LOL

The delay your referring to is with the spindle override, and yes was something I seen and intend to tweak. This is sort of the same issue that caused the cultureinfo problem, its being calculated in a thread that the cultureinfo wasn't addressed in.

These issues will be addressed in the plugins final version.

Dan

[Dan911]

Hey guys,

Here's an update guys.
I've gotten the Plugin to work now and it performs beautiful, the only slight negative is a delay when adjusting spindle speed on the fly but i can live with that.

regards
Patrick

Did you change your Sact field on run screen to 2050 from 870 per instructions??

If not the plugin is continually writing frequency's and will cause a much longer delay. I strongly suggest you do this than you will also see what your RPM is at whatever percent you have spindle override set to.

[Kelevra83]

Did you change your Sact field on run screen to 2050 from 870 per instructions??

If not the plugin is continually writing frequency's and will cause a much longer delay. I strongly suggest you do this than you will also see what your RPM is at whatever percent you have spindle override set to.

Yes Dan,
I've updated the screenset according to the instructions. The delay feels a little timing dependant like the plug in writes the spindle speed every 0.5 seconds or something comparable.

[Dan911]

Yes Dan,
I've updated the screenset according to the instructions. The delay feels a little timing dependant like the plug in writes the spindle speed every 0.5 seconds or something comparable.

Yes, that is the delay I was referring to in post #56 that I found annoying. Did have a snow day (Blizzard) here today and had a chance to look at it and not sure if its worth the troubles to fix. You can click on the override percent as quick as you like and that updates instantly, but it takes the RPM that 1/2 second to catch up. Each click is sending a frequency to the VFD. I probably can have the RPM update instant like the percent but it still going to be that delay for the VFD to read and respond. If it was actual RPM it would take longer for the spindle to actually reach that speed.

Dan

[Kelevra83]

Yes, that is the delay I was referring to in post #56 that I found annoying. Did have a snow day (Blizzard) here today and had a chance to look at it and not sure if its worth the troubles to fix. You can click on the override percent as quick as you like and that updates instantly, but it takes the RPM that 1/2 second to catch up. Each click is sending a frequency to the VFD. I probably can have the RPM update instant like the percent but it still going to be that delay for the VFD to read and respond. If it was actual RPM it would take longer for the spindle to actually reach that speed.

Dan

Yeah that makes sense.
Would have been great to use a potentiometer with an arduino or an encoder connected directly to the controller to adjust the overrides of the spindle and the feed on the fly but if its just the vfd not catching up fast enough its a whole different story.

Thanks a ton for all your effort dan, i really appreciate it.

Patrick

[A_Camera]

Yeah that makes sense.
Would have been great to use a potentiometer with an arduino or an encoder connected directly to the controller to adjust the overrides of the spindle and the feed on the fly but if its just the vfd not catching up fast enough its a whole different story.

Thanks a ton for all your effort dan, i really appreciate it.

Patrick

Unfortunately you are using the UC400 and that does not have any analogue inputs. If you had a UC300ETH you could easily connect a potentiometer since that has two analogue inputs as well as two analogue outputs. So, if you want to save time and effort you should get a UC300ETH.

[Kelevra83]

Unfortunately you are using the UC400 and that does not have any analogue inputs. If you had a UC300ETH you could easily connect a potentiometer since that has two analogue inputs as well as two analogue outputs. So, if you want to save time and effort you should get a UC300ETH.

I already dropped the idea when i saw that the new version of UCCNC has aux encoder inputs for the ethernet controllers that to you can map to override the feeds and speeds.
Thats going to be way easier than get the arduino thing working.

[Dan911]

Hello all,

To anyone who downloaded and using this plugin this new final version is a must have. It addresses any bugs that came up from previous version and fixed a serious issue with using excessive CPU usage. The slight delay using spindle override was also fixed. It is by far the most stable version released thus far. If any questions don't hesitate to post.

Dan

Attachment 350184



Another important change that's in the instructions but should be mentioned for those who already using plugin is the plugin now writes to 20050 for Sact (actual spindle speed) field. This is an important step because plugin checks this and if not set correctly it will continually write frequency to it and may make spindle override a little slower to its response.

[ger21]

Dan,
Not sure if it's possible, but it might be a good idea to let the user define the field number for the Sact. Otherwise, at some point, you may see conflicts with screensets or other plugins. I use 50 different fields in my 2017 screen, but I start at 20300, so there's no issue there. But I've already changed some numbers in my screen due to a confilct with another plugin.
Just a thought.

Now, the question is, are all Huanyang VFD's on Ebay the same, and will they all work with the plugin. I guess it would be worth spending the extra $30 to get one that claims to be the real deal?

UPDATED 2.2KW VARIABLE FREQUENCY DRIVE INVERTER VFD 220V 3HP 10A HIGH QUALITY | eBay

[Dan911]

Dan,
Not sure if it's possible, but it might be a good idea to let the user define the field number for the Sact. Otherwise, at some point, you may see conflicts with screensets or other plugins. I use 50 different fields in my 2017 screen, but I start at 20300, so there's no issue there. But I've already changed some numbers in my screen due to a confilct with another plugin.
Just a thought.

Now, the question is, are all Huanyang VFD's on Ebay the same, and will they all work with the plugin. I guess it would be worth spending the extra $30 to get one that claims to be the real deal?

UPDATED 2.2KW VARIABLE FREQUENCY DRIVE INVERTER VFD 220V 3HP 10A HIGH QUALITY | eBay

Hi Gerry,

Yes this will be very simple to do, when VMAX549 emailed me and pointed out UCCNC recommends USER number 20000 - 20999 and I intended to do that but forgot, I will add this sometime today and update with a newer version.

If this plugin will work with these cheap Huanyang copies I really don't know, if not I would assume it communicates Modbus Standard. I do believe I can use this plugin to communicate with any VFD by implementing there function strings, and if ever became a demand I could make these strings editable just like I'm going to do with the Sact field for UCCNC.

Dan

[ger21]

I'll order one in a few weeks, and see if I can find some time to do some testing.
And see if the $125 spindles I bought are any good.

[vmax549]

Teh thing I have seen with HY type VFDs is they could be anything pretending to be a HY. On the zone is an example now of a counterfit HY vfd that has different internals(non HY) but was sold as a HY (;-) In that example it did not even have a Comport to talk to (;-)

as to teh User number range THAT is going to be an on going problem. No Matter what number you pick someone will possibly pick teh same number after all there are only 1000 possible numbers .

I can garrantee that I have already walked over everyones number ranges with teh experiementing I have done with Macros.MacroWizards,Plugins,MacroLoops.

I have even walked all over some of my OWN numbers may times forgetting what I had already used.

I have come up with several ways around it BUT without some standards being developed and used that to is worthless (;-)

One thing you may want to check on is CAN teh HY ouput teh actual RPM values in any form ??. Pulses. freq,values ,analog ???

(;-) TP

[bs85]

Hi Dan,

Replaced ver 1.0006 with 1.0007 dll file and the plugin no longer shows on the UCCNC plugin screen. put 1.0006 back and it shows up on the plugin screen.

Using UCCNC ver 1.2032

Thanks

[Dan911]

Hi TP, I modified the plugin so the user can edit the Labelnumber to there choosing and could change it if later versions conflict with it. I just logged on to upload it but first I'm going to download UCCNC ver 1.2032 and see what bs85 problem is first.

[Dan911]

Hi Dan,

Replaced ver 1.0006 with 1.0007 dll file and the plugin no longer shows on the UCCNC plugin screen. put 1.0006 back and it shows up on the plugin screen.

Using UCCNC ver 1.2032

Thanks

Hey bs85,

This is the second time I heard of it not showing up in the plugin list and a little confused why, no trouble on my end. Try the version below, you will have to input your labelnumber for your Sact field in the configuration set up. Please let me know if this works for you, ver 1.0006 uses a lot of unnecessary CPU usage.

Attachment 350450

[ger21]

Version 1.2033 was just released.
http://www.cncdrive.com/UCCNC/setup_1.2033.exe

[Dan911]

One thing you may want to check on is CAN teh HY ouput teh actual RPM values in any form ??. Pulses. freq,values ,analog ???

(;-) TP

Using a RS485 connection to receive RPM from the HY VFD is to send a function read RPM command and it returns the current running frequency. I monitored the 2 Mach3 plugins and Spindle Talker and all use this only method. I seen it as a waste of resources to have the VFD and plugin continually reading and writing to receive the same Frequency that it was set to. The only gain was to see the frequency(RPM) accelerate to its set speed and decelerate when shutting down. That's why I aborted implementing RPM. If the spindle was ever under load and actually slowed RPM the HY VFD will never show this because it still going to be sending set frequency.

What was needed is to see your RPM when using spindle override, because the Sset field wouldn't change. That's what the Sact field shows.

Sorry for making an essay out of a sentence...lol

Dan