1
Support Questions / Re: Modbus fix
« on: January 17, 2017, 08:35:06 AM »
Will try today, thanks.
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.
2
Support Questions / Re: Modbus fix
« on: January 16, 2017, 01:36:38 PM »
When running your new patch the following error starter to come immediately after I try to connect to the second PLC
"A first chance exception of type 'MfgControl.AdvancedHMI.Drivers.Common.PLCDriverException' occurred in MfgControl.AdvancedHMI.Drivers.dll"
So I went back to the one that is working because I want to run a test for several days.
"A first chance exception of type 'MfgControl.AdvancedHMI.Drivers.Common.PLCDriverException' occurred in MfgControl.AdvancedHMI.Drivers.dll"
So I went back to the one that is working because I want to run a test for several days.
3
Support Questions / Re: Modbus fix
« on: January 15, 2017, 12:58:09 PM »
Ok Archie,
I own you this response. (good news)
I have being running tests after receiving the Automation direct adapter. Unfortunately I lost track of all the various patch that you prepare so I only was able to run test with the original release "t" and the last one you made. With the original I continued having problems, but with the last patch the program communicated with the two Clicks, from time to time I can see that there is a pause of a second or two in communication but it catch right away, witch I think that at the moment is acceptable. My original objective was to be able to communicate with more than two devices, but I don't have at the moment the necessary hardware to test.
During the test I change the BPS to various rates and find out that the hugest reliable speed that I can use is 38400, also it is clear now that the model and USB port of the converter have a huge importance, If I connect the adapter to one of the USB ports on my computer screen I get a tremendous amount of missing communication packages, but connected directly to my computer USB port then I get acceptable results.
I will still keep testing whenever I have the time to improve it as much as possible. If and whenever I have new issues I will place them in a new post since I am assuming that this case was satisfactory closes.
Thanks you for your help.
I own you this response. (good news)
I have being running tests after receiving the Automation direct adapter. Unfortunately I lost track of all the various patch that you prepare so I only was able to run test with the original release "t" and the last one you made. With the original I continued having problems, but with the last patch the program communicated with the two Clicks, from time to time I can see that there is a pause of a second or two in communication but it catch right away, witch I think that at the moment is acceptable. My original objective was to be able to communicate with more than two devices, but I don't have at the moment the necessary hardware to test.
During the test I change the BPS to various rates and find out that the hugest reliable speed that I can use is 38400, also it is clear now that the model and USB port of the converter have a huge importance, If I connect the adapter to one of the USB ports on my computer screen I get a tremendous amount of missing communication packages, but connected directly to my computer USB port then I get acceptable results.
I will still keep testing whenever I have the time to improve it as much as possible. If and whenever I have new issues I will place them in a new post since I am assuming that this case was satisfactory closes.
Thanks you for your help.
4
Support Questions / Re: OPC driver problem
« on: January 11, 2017, 01:44:31 PM »
Godra,
Spend the last two and a half day working with Archie in the modbus, finally it appears that now my problems are centered in the communication adapter I was using, I ordered the one that he is using hoping that everything will be ok when I get it.
Now going back to this thread, your last suggestion of using "Label1.Text = OpcDaCom1.Read("M20943_A1_Scaled_Value", 1)(0)" did not produced any error, but also returned an empty string. tonight I will try using a subscription to see if I get any result.
Regards
Victor.
Spend the last two and a half day working with Archie in the modbus, finally it appears that now my problems are centered in the communication adapter I was using, I ordered the one that he is using hoping that everything will be ok when I get it.
Now going back to this thread, your last suggestion of using "Label1.Text = OpcDaCom1.Read("M20943_A1_Scaled_Value", 1)(0)" did not produced any error, but also returned an empty string. tonight I will try using a subscription to see if I get any result.
Regards
Victor.
5
Support Questions / Re: Modbus fix
« on: January 11, 2017, 12:28:15 PM »
I just place the order to see if I can get it before the week end. (better price than B&B).
Will let you know what happen then.
Once again, Thanks for your help.
Will let you know what happen then.
Once again, Thanks for your help.
6
Support Questions / Re: Modbus fix
« on: January 11, 2017, 12:08:19 PM »
Archie,
Now that I found and installed the analyzer yesterday I went back to test with the Cimplicity (GE HMI) and found out that at this point your program and Cimplicity are acting very similar, the amount of timeouts (UP and DOWM) that I am getting in Cimplicity is horrendous.
When I started having problem, I was able to communicate with one device at the time, and Cimplicity appeared to be doing a better job, but now after all the reviews that you have done I can communicate with both devices, intermittent but is talking to both of them as well as Cimplicity so I can say that you have done you part and now if up to me since appears that my problems now are related to the communication adapters that I am using.
At the present I have an inexpensive RS-232 to RS-485 converter model # XS201A from USconverter.com connected to a USB to Serial converter model # TU-S9 from Trendnet, somewhere in there seem to reside my most recent problems. I am going to get something from B&B electronic, a brand that I always trusted to continue my test, I will then test with all your patch (including the original release of version t and will let you know the result here or in a new post. I think that at this point I can say your help had being outstanding.
Just before I close this until new development. Can you tell me what kind of adapters are you using for your test? I may want to get the same one.
Thank you for your help and patient dealing with this issue.
Victor.
Now that I found and installed the analyzer yesterday I went back to test with the Cimplicity (GE HMI) and found out that at this point your program and Cimplicity are acting very similar, the amount of timeouts (UP and DOWM) that I am getting in Cimplicity is horrendous.
When I started having problem, I was able to communicate with one device at the time, and Cimplicity appeared to be doing a better job, but now after all the reviews that you have done I can communicate with both devices, intermittent but is talking to both of them as well as Cimplicity so I can say that you have done you part and now if up to me since appears that my problems now are related to the communication adapters that I am using.
At the present I have an inexpensive RS-232 to RS-485 converter model # XS201A from USconverter.com connected to a USB to Serial converter model # TU-S9 from Trendnet, somewhere in there seem to reside my most recent problems. I am going to get something from B&B electronic, a brand that I always trusted to continue my test, I will then test with all your patch (including the original release of version t and will let you know the result here or in a new post. I think that at this point I can say your help had being outstanding.
Just before I close this until new development. Can you tell me what kind of adapters are you using for your test? I may want to get the same one.
Thank you for your help and patient dealing with this issue.
Victor.
7
Support Questions / Re: Modbus fix
« on: January 11, 2017, 09:35:58 AM »
And this is the log from my application.
8
Support Questions / Re: Modbus fix
« on: January 11, 2017, 09:35:02 AM »
Good morning Archie, I see you are getting somewhere, both applications (your temp. controller and my click) are acting similar now, you can see activity in both PLCs for a few seconds, then stop and restart again. Here I am attaching two files, the Driverlog.txt that your Temp sample generated, and then in the post below this the log of my application generated by HHD device monitoring since my application still refuses to generate the Driverlog.txt.
victor.
victor.
9
Support Questions / Re: Modbus fix
« on: January 10, 2017, 04:32:14 PM »
Interesting, I don't know if it was because in on my last testing I slowdown the bps to 9600 or because you modification of the driver slow it also but now I see less error, still every couple of minutes you can see the communication stoping on both units (nothing in, nothing out) I still can't get the log for my application but here is the one from your sample.
Did you saw the last pic I sent you of the analizer, it seem that the program is the one that is not sending command evenly.
Thanks.
Did you saw the last pic I sent you of the analizer, it seem that the program is the one that is not sending command evenly.
Thanks.
10
Support Questions / Re: Modbus fix
« on: January 10, 2017, 03:35:12 PM »
I got a analyzer demo and this is what I saw, it appears that is the program that start sending to one of the PLC then for couples of commands sent to both and then switches to the other PLC.
11
Support Questions / Re: Modbus fix
« on: January 10, 2017, 02:31:57 PM »
Well after installing the Visual Studio Express 2015 I was able to run your test and here is the DriverLog running at your original rate override of 50 As you can see it pulls from one and then after a while it switches over.
13
Support Questions / Re: Modbus fix
« on: January 10, 2017, 01:31:33 PM »
Yes the same test (your test) was not working until I increased the Rate Override to 1000 then started to work. Here is the port configuration of the CLICK.
I also try increasing the rate on my app, but went all the way to 3000 and it is better but still intermittent between PLCs.
Not much to do with the log when not working it is just an enable/disable flag, nothing else, still will keep trying from time to time.
I also try increasing the rate on my app, but went all the way to 3000 and it is better but still intermittent between PLCs.
Not much to do with the log when not working it is just an enable/disable flag, nothing else, still will keep trying from time to time.
14
Support Questions / Re: Modbus fix
« on: January 10, 2017, 01:05:15 PM »
Yes I try the button and the Msg was "True".
I also went back to my application and increase the time to 1 second, now I can see how data return is sort of intermittent between the units PLC 1 return data for a few seconds, then switch over to PLC 2, and so on, but never the two of them, I will increase it even more to see if I reach a point where data come to both. Remember someone mentioning before that perhaps finding a way of enable/disable subscription in a fashion that the command don't go out almost simultaneously could be a solution. Obviously I have way more data in each window instance of my application than in your test.
I also set the EnableLogging to True in my application and no data is being logged.
I also went back to my application and increase the time to 1 second, now I can see how data return is sort of intermittent between the units PLC 1 return data for a few seconds, then switch over to PLC 2, and so on, but never the two of them, I will increase it even more to see if I reach a point where data come to both. Remember someone mentioning before that perhaps finding a way of enable/disable subscription in a fashion that the command don't go out almost simultaneously could be a solution. Obviously I have way more data in each window instance of my application than in your test.
I also set the EnableLogging to True in my application and no data is being logged.
15
Support Questions / Re: Modbus fix
« on: January 10, 2017, 12:25:29 PM »
Still not getting the LOG but I was able to get the two controllers working by bringing the PllRateOverrrite to 1000. In your test.