Huanyang VFD controller plugin

[BK]

Hello All,
Hope you can help me with my communications problem between my Huanyang VFD and Mach3, Set up as indicated and can see data being sent to VFD but no responce back.
Just wondering if anyone has got this plugin to work with HXSP-2108G USB to RS485 or do I need to get the F version?
Thanks in advance,
BK.

[BK]

Hello Again,
Sorry forgot to give details of comms, please see what mach3 sends via your plugin and below that responce ordered F version hopefully will be with me in a week but any help or advice would be greatfully received.
Port opened by process "Mach3.exe" (PID: 5404)

 01 05 03 00 00 00 CD 8E 01 05 03 00 00 00 CD 8E   ......ÍŽ......ÍŽ
 01 05 03 00 00 00 CD 8E 01 05 03 00 00 00 CD 8E   ......ÍŽ......ÍŽ
 01 05 03 00 00 00 CD 8E 01 05 03 00 00 00 CD 8E   ......ÍŽ......ÍŽ
 01 03 01 01 31 88 01 03 01 01 31 88 01 03 01 01   ....1ˆ....1ˆ....
 31 88 01 03 01 01 31 88 01 03 01 01 31 88 01 03   1ˆ....1ˆ....1ˆ..
 01 08 F1 8E 01 03 01 08 F1 8E 01 03 01 08 F1 8E   ..ñŽ....ñŽ....ñŽ
 01 03 01 08 F1 8E 01 03 01 08 F1 8E 01 03 01 08   ....ñŽ....ñŽ....
 F1 8E 01 03 01 08 F1 8E 01 03 01 08 F1 8E 01 03   ñŽ....ñŽ....ñŽ..
 01 08 F1 8E 01 03 01 08 F1 8E                     ..ñŽ....ñŽ


Port opened by process "Mach3.exe" (PID: 5404)

 7F 7D 7E 7F 7D 7E 7F 7D 7E 7F 7D 7E 7F 7D 7E 7F   }~}~}~}~}~
 7D 7E 7F 7E 7F 7F 7E 7F 7F 7E 7F 7F 7E 7F 7F 7E   }~~~~~~
 7F 7F 7E 7F 7F 7E 7F 7F 7E 7F 7F 7E 7F 7F 7E 7F   ~~~~~
 7F 7E 7F 7F 7E 7F 7F 7E 7F 7F 7E 7F 7F 7E 7F      ~~~~

Thanks,
BK.

[mikie]

Hey Matty, guys,

I spent the entire day trying to get my VFD working with this application.
I managed to get connectivity working without issue. I see 2 & 2 for PD001 & PD002 in Mach3.

Problem: (This seems to be the same issue seen by Sergio in previous posts)

1. Start the spindle with M3 S1200
2. When I try to change speed say by setting S2000 i don't see anything
3. M5 also does nothing

As per Sergios posts, I get the error attached below when I hit the Estop or in some instances when I try to set different speeds or stop the spindle. In short nothing happens after the 1st command is issued.

I'll try to get a dump of the communications layer and post it on the forum tomorrow. I've had enough of this for today.

Additional question: I have the same RS485 converter as pictured by Matt, when I loaded the driver for this I used the RS485/422 Windows XP installer. I assume this is the correct driver for this unit?

[mikie]

Okay,

Couldn't wait to see some other ideas I had, so I went back into the shed and tried to simplify the operation.
I created a new profile which uses the Parallel port instead of the smooth stepper.
This is all based upon a PC with a freash build with SP3 and only Mach3 and Huanyang spindle drivers loaded.

So, I still see Mach3 lockup after commencing the spindle. I am sure this is not related to EMF as the hardware setup works fine when not using the RS485 interface.

I took a dump of Comms 3 for perusal and the 4 output screens are below:

Line View

[03/07/2010 20:33:24]
1  IRP_MJ_DEVICE_CONTROL - Request operates a serial port
   STATUS_SUCCESS
         IOCTL_SERIAL_PURGE - Request cancels the specified requests and deletes data from the specified buffers
           
----------------------------------------------------------------------------------
[03/07/2010 20:33:24]
3  IRP_MJ_WRITE - Request transfers data from a client to a COM port
   STATUS_SUCCESS
      01 05 03 0e 52 00 91 2d                            ....R.‘-
----------------------------------------------------------------------------------
[03/07/2010 20:33:24]
5  IRP_MJ_READ - Transfers data from a COM port to a client
   STATUS_SUCCESS
      01 05 02                                           ...
----------------------------------------------------------------------------------
[03/07/2010 20:33:24]
7  IRP_MJ_READ - Transfers data from a COM port to a client
   STATUS_SUCCESS
      0e 52 3d 51                                        .R=Q
----------------------------------------------------------------------------------
[03/07/2010 20:33:24]
9  IRP_MJ_DEVICE_CONTROL - Request operates a serial port
   STATUS_SUCCESS
         IOCTL_SERIAL_PURGE - Request cancels the specified requests and deletes data from the specified buffers
            Flags - 8
----------------------------------------------------------------------------------
[03/07/2010 20:33:24]
11  IRP_MJ_WRITE - Request transfers data from a client to a COM port
   STATUS_SUCCESS
      01 05 03 0e 52 00 91 2d                            ....R.‘-
----------------------------------------------------------------------------------
[03/07/2010 20:33:24]
13  IRP_MJ_READ - Transfers data from a COM port to a client
   STATUS_SUCCESS
      01 05 02                                           ...
----------------------------------------------------------------------------------
[03/07/2010 20:33:24]
15  IRP_MJ_READ - Transfers data from a COM port to a client
   STATUS_SUCCESS
      0e 52 3d 51                                        .R=Q
----------------------------------------------------------------------------------
[03/07/2010 20:33:25]
17  IRP_MJ_DEVICE_CONTROL - Request operates a serial port
   STATUS_SUCCESS
         IOCTL_SERIAL_PURGE - Request cancels the specified requests and deletes data from the specified buffers
            Flags - 8
----------------------------------------------------------------------------------
[03/07/2010 20:33:25]
19  IRP_MJ_WRITE - Request transfers data from a client to a COM port
   STATUS_SUCCESS
      01 03 01 01 31 88                                  ....1ˆ
----------------------------------------------------------------------------------
[03/07/2010 20:33:25]
21  IRP_MJ_READ - Transfers data from a COM port to a client
   STATUS_SUCCESS
      01 03 01                                           ...
----------------------------------------------------------------------------------
[03/07/2010 20:33:25]
23  IRP_MJ_READ - Transfers data from a COM port to a client
   STATUS_SUCCESS
      00 f0 48                                           .ðH
----------------------------------------------------------------------------------
[03/07/2010 20:33:34]
25  IRP_MJ_DEVICE_CONTROL - Request operates a serial port
   STATUS_SUCCESS
         IOCTL_SERIAL_PURGE - Request cancels the specified requests and deletes data from the specified buffers
            Flags - 8
----------------------------------------------------------------------------------



Terminal View

....R.‘-....R=Q....R.‘-....R=Q....1ˆ....ðH


Dump View

[03/07/2010 20:33:24] - Written data

01 05 03 0e 52 00 91 2d                            ....R.‘-

[03/07/2010 20:33:24] - Read data

01 05 02 0e 52 3d 51                               ....R=Q

[03/07/2010 20:33:24] - Written data

01 05 03 0e 52 00 91 2d                            ....R.‘-

[03/07/2010 20:33:24] - Read data

01 05 02 0e 52 3d 51                               ....R=Q

[03/07/2010 20:33:25] - Written data

01 03 01 01 31 88                                  ....1ˆ

[03/07/2010 20:33:25] - Read data

01 03 01 00 f0 48                                  ....ðH



Table View

0   03/07/2010 20:33:24   IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_PURGE)   DOWN   STATUS_SUCCESS   08 00 00 00    
1   03/07/2010 20:33:24   IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_PURGE)   UP   STATUS_SUCCESS      
2   03/07/2010 20:33:24   IRP_MJ_WRITE   DOWN   STATUS_SUCCESS      
3   03/07/2010 20:33:24   IRP_MJ_WRITE   UP   STATUS_SUCCESS   01 05 03 0e 52 00 91 2d    
4   03/07/2010 20:33:24   IRP_MJ_READ   DOWN   STATUS_SUCCESS      
5   03/07/2010 20:33:24   IRP_MJ_READ   UP   STATUS_SUCCESS   01 05 02    
6   03/07/2010 20:33:24   IRP_MJ_READ   DOWN   STATUS_SUCCESS      
7   03/07/2010 20:33:24   IRP_MJ_READ   UP   STATUS_SUCCESS   0e 52 3d 51    
8   03/07/2010 20:33:24   IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_PURGE)   DOWN   STATUS_SUCCESS   08 00 00 00    
9   03/07/2010 20:33:24   IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_PURGE)   UP   STATUS_SUCCESS      
10   03/07/2010 20:33:24   IRP_MJ_WRITE   DOWN   STATUS_SUCCESS      
11   03/07/2010 20:33:24   IRP_MJ_WRITE   UP   STATUS_SUCCESS   01 05 03 0e 52 00 91 2d    
12   03/07/2010 20:33:24   IRP_MJ_READ   DOWN   STATUS_SUCCESS      
13   03/07/2010 20:33:24   IRP_MJ_READ   UP   STATUS_SUCCESS   01 05 02    
14   03/07/2010 20:33:24   IRP_MJ_READ   DOWN   STATUS_SUCCESS      
15   03/07/2010 20:33:24   IRP_MJ_READ   UP   STATUS_SUCCESS   0e 52 3d 51    
16   03/07/2010 20:33:25   IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_PURGE)   DOWN   STATUS_SUCCESS   08 00 00 00    
17   03/07/2010 20:33:25   IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_PURGE)   UP   STATUS_SUCCESS      
18   03/07/2010 20:33:25   IRP_MJ_WRITE   DOWN   STATUS_SUCCESS      
19   03/07/2010 20:33:25   IRP_MJ_WRITE   UP   STATUS_SUCCESS   01 03 01 01 31 88    
20   03/07/2010 20:33:25   IRP_MJ_READ   DOWN   STATUS_SUCCESS      
21   03/07/2010 20:33:25   IRP_MJ_READ   UP   STATUS_SUCCESS   01 03 01    
22   03/07/2010 20:33:25   IRP_MJ_READ   DOWN   STATUS_SUCCESS      
23   03/07/2010 20:33:25   IRP_MJ_READ   UP   STATUS_SUCCESS   00 f0 48    
24   03/07/2010 20:33:34   IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_PURGE)   DOWN   STATUS_SUCCESS   08 00 00 00    
25   03/07/2010 20:33:34   IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_PURGE)   UP   STATUS_SUCCESS      
26   03/07/2010 20:33:34   IRP_MJ_WRITE   DOWN   STATUS_SUCCESS      



After this request Mach3 locked up and I can use it any more.

I wonder if issues are because of versions of mach3 used? I'm using the latest V3.42.40

Note: I tried to load spindle talker on my machine, but it also errored and said there was a missing file or one of the associated files was missing. I'll have to capture this error next time as i didn't get a chance with my PC rebooting itself.

/Michael

[mikie]

Okay here is the spindle talker issue that I came across. I tried on my local PC and it spits out the same error. I downloaded this from the woodies forum where either Matty or Mark posted it as a ZIP file.

/Michael


EDIT:
I fixed this up by adding the missing file and running

regsvr32 c:\windows\system32\mscomm32.ocx

at Start - Run to register the file in the registry.

/M

[mhasting2004]

Hi Micheal

That seems to me like a windows issue. Do you have that file in your c:\windows\system32 folder? 

I'm not a window guru but a quick google came up with few suggestions.

I'll try and get a better anwser next week when I'm back at work.

[mikie]

Thanks Mark,

I did work it out and I posted the fix below in the previous post.

Q. How can you tell if the RS485 unit is a G or F version?

/M

[mhasting2004]

So does spindle talker work now? Not sure on the versions of the 485 board but don't think that should really matter. If you can get spindletalker to work then at least you know that the comms are ok (it has no error checking like the plugin so its a basic test)

I've got a later revised version of spindletalker that allows you to read all the registers (wasn't interpreting hex addresses in the previous version so didn't recognise A-F) in advanced mode. This isn't the issue you are having so no need to confuse the issue with a newer version just yet.

Also don't know if this OCX file is needed by the plugin... maybe you fixed two things?

cheers

Mark

[BK]

Hello Mickie and All,
I tried the diagnostics and port monitor supplied with these cards and got the same results you did.
I downloaded a simple free port monitor from here,
http://www.serial-port-monitor.com/
The difference between and the G and F version seems to be G version is RS485 / RS422 compatible and F version is only RS485.
If you run the serial comms program I would be interested if you could please check if you get the same output and data received as I did above.
My wiring is RS- to T+/B and RS+ to T-/A I also found no difference if ground was connected between units or not.
Hope this helps I will let you know if F version cures the problem when my card arrives from China so could be over a week?
Just wondering if any one has managed to get G version working with this plugin?
All the best,
BK.

[mikie]

Hi Mark,

Okay I can't let it lie and I went out to the shed and braved the cold.
SPindle talker fired up on my machine after installing the missing OCX file.
When I started spindle talker I could once again start the unit spinning, but it failed to do any other commands. In one instance the PC crashed and rebooted.

I think I have answered my question about versions. On the dongle is a G, so I have a G version I suspect.

BK,

I think you are on the right path with the F and G versions causing different output. I suspect the driver written for each unit is different in some way and the ST program is not able to receive feedback from the spindle. I am interested in seeing if you get it working when you get your F dongle.

I wonder if someone could post the driver for the F version on this site. I will download and update my driver with it and see if this fixes the issues.
BK, my capture is shown above in my previous posts so i'm not sure if it is similar to yours

/Michael