Javier Galaz
-
Posts
22 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Events
Blogs
Downloads
Articles
Media Demo
Posts posted by Javier Galaz
-
-
29 minutes ago, Ausman said:
Older versions of OS are in older versions of Visilogic, which you can get at "previous versions" here:
https://www.unitronicsplc.com/software-visilogic-for-programmable-controllers/
Yes I did that, thought that maybe there could be a repository with the older OS.
-
16 minutes ago, Fernando Castro said:
I am not sure, but i think that the OS are downloaded to ubitronics software based on the visilogic version you have C:\Program Files (x86)\Unitronics\Unitronics VisiLogic_C\Data\Os\Vision Enhanced\V700\OS
Yes, but I wanted older versions, in my computer I could only find 4.10, but, no problem I installed all the versions on my windows virtual machine and copied the different OS's, for now I'm still trying to downgrade my program to .65
When that's done I'm going to try everything we've discussed. -
Hola @Fernando Castro , I'm trying to downgrade the OS, do you know where I can get the corresponding .uos file?
-
Thats right, I've just checked with my Vision 130, and it works just like yours. Maybe the problem is with the touch HMIs?
-
14 hours ago, Ausman said:
Why doesn't that work? My limited use of Anydesk has it operating things ok. But I don't use touchscreen models at all.
Don't know, when I tried to go to info mode from visilogic using the "Online Test" it simply says, "No can't do" xD
14 hours ago, Ausman said:And good luck with the downgrade. Hopefully your project will open OK in 8.65.
today's the big day, let's see what happens.
-
20 minutes ago, Flex727 said:
I can't send you a whole program, but here is the part that matters.
Thanks, really appreciate it. I've perused this program and see no relevant difference to my software.
15 minutes ago, kratmel said:I try to read Bug report, it is solved in new Vislogic
VisiLogic V9.8.94 Bugs Fixed
• Fonts: In some cases, fonts were not shown correctly in VisiLogic.
.........
• Socket Init: if this was set to PCOM, Modbus did not work.I think something new Ethernet based is added to Visilogic after 9.8.65....
And now this changes make some trouble in "standard" application.
Now seeing this and with everything Flex has said, I'm definitely gonna try downgrading to 9.8.65 and see If that is the issue. Although his is gonna have to wait until monday when I have physical access to the PLC, to also check info mode and try to downgrade my software.
Until then, THANKS VERY MUCH guys, you've been so helpful and nice It has been a really lovely experience for being my first time here.Best Regards to all of you.
-
12 minutes ago, Flex727 said:
This is confusing to me. What is the USB connection? Between what & what? What is the full path of connection to the PLC?
On site I have a notebook directly connected to the PLC using standard micro USB cable. On that notebook I have Visilogic running and doing the tests we've been talking about.
To that notebook I connect from my home computer using Anydesk (a remote desktop software). -
33 minutes ago, Flex727 said:
Just as a data point, I have used V700s as MODBUS TCP slaves on port 502 for SCADA systems many, many times without incident, though not using 9.8.94 - mostly 9.8.65, as mentioned by Joe.
Do you have a working program that I can test?
-
17 minutes ago, Ausman said:
Thanks Flex.
I know I'm a dumbo on this sort of thing, but one difference I see b/n the example and this project is that there is no Slave TCP address reference in the IP config area. In the example there is. Does this matter?
I supposed that is relevant only when using as Modbus Master, but I'm trying to set it up as Slave.
Anyway I've tried setting the address as per the example, and still no luck.
-
21 minutes ago, Ausman said:
I'm assuming you've tried a different network ID other than 255. I don't use TCP for modbus but this looks odd. Someone explain the 255 ID use to me in this case...I'd like to learn something. Why do a general ask and not a specific one?
And Joe, I only have 8.65 as you mention, but by trying to open the file I get an error message and things close on screen, you then have to go to task manager to actually end the task, double click the project again and up come other messages along the way to opening the project ok. This has always been my consistent way to read later version projects. Perhaps some info gets lost along the way that is only available in later versions, but it will show me basics.
cheers, Aus
Yes I've tried.
16 minutes ago, Flex727 said:To the best of my knowledge, the network ID is not used for MODBUS TCP. I've always just left it at 255.
That did not work for me going from 9.8.91 to 9.8.94. It used to work for earlier versions.
I'm hoping 9.8.94 fixed some of the glaring problems with 9.8.91 and will be trying it out on my next major project.
In the V130 working software if I put 255 in the address and don't use it in my client I get empty response, but if I put something (not just 255) I get the correct answer. with V700 I've tried this variations too.
-
1 hour ago, Joe Tauser said:
I installed version 9.8.94 and was able to open the program. I also looked at the V700 Example for Modbus TCP slave and it does not assign port 502 to socket 2, which is a conflict of the Help description of default port 20258 as you describe.
Are you using one of the canned Modbus masters as mentioned above? Have you loaded the V700 with some data? I usually load up MI 0.. MI9 with the values 1 to 10 when establishing first contact and set the Modbus master to read 10 registers starting with 40001.
I wonder if the Creators even tested this example. I don't have a V700 in my home smoke-filled workspace cave but I can grab one from the office. I'll have to get back to you on this. I am now extremely curious.
Joe T.
There is some data on those registers
This is the connection config using Modbus poll (I believe that is what you mean by canned Modbus master):
This is the read configuration
P.S. : I'm gonna try the older more stable version.
-
2 hours ago, Flex727 said:
Did you confirm in INFO Mode that the Socket was actually set to port 502?
No, I haven't, I'm remoting this unit through a field computer connected through usb. And info mode is not supported in online mode. On monday I can get to it.
-
17 minutes ago, Flex727 said:
Yes, that is correct.
It doesn't work, I can't even connect to port 502.
Without that FB I can establish a connection to 20258, even if only to get empty responses. -
11 minutes ago, Joe Tauser said:
This is a very good idea as it isolates troubleshooting to one side of the conversation.
I would try socket status request #28 to verify the socket is actually in modbus mode.
You've posted snippets of your PLC program. Can you upload the whole thing so we can have a look?
Joe T.
I've done that, I get a 1 with request #28, and according to the help page that corresponds to modbus mode.
-
Just now, Joe Tauser said:
Sorry - I didn't see that you did that in your first post. It was embedded in a paragraph as opposed to standing alone.
Joe T.
I've actually made some changes with the help I've gotten in this thread. Here's an update.
-
7 minutes ago, Flex727 said:
Thanks. Oddly, that does not appear in my version of the Help file that came with VisiLogic 9.8.94, nor is the operand description in the operands list in VisiLogic.
I have the same VisiLogic version, the Help version is V300-21-G23 Rev: 3.00.
The operand descriptor decscription is also blank, but the number increases when I send a request.
-
I've read that, thank you for pointing that out, however, pymodbus uses addresses starting with 0, just like Unitronics Modbus.
Anyway if I was reading coil number 1 using address 0001 it should still give me register number 2 and not empty response.
I've tried using Modbus poll and CAS Modbus scanner (I saw in that thread that someone used them to some degree of success), and they both gave me timeout.
using the same page in Help you suggested, namely "Vision700 - Using Ethernet", I found that It receives packages and is supposed to be sending them too.
both numbers update every time I send a modbus request, but my client receives nothing.
-
3 minutes ago, Flex727 said:
By the way, where did you find this?
In the help, the page that Kratmel pointed out: "Vision700 - Using Ethernet". At the bottom to be more precise.
-
8 minutes ago, Flex727 said:
Yes, that is the default, but when you perform a Socket Initialization, that changes the properties.
So, if I understand correctly, if I use this:
like this
I would get Modbus port in port 502 instead of 20258 which is the default?
-
18 hours ago, kratmel said:
Plese read this topic
And find in Help file
"Vision700 - Using Ethernet"
Thanks for your reply, I've read that and found more info, however I still receive 0 bytes responses.
I've read that the V700 socket 2 port is actually 20258 and not 502. So I've changed my modbus client accordingly.
My SDW 61 register is actually incrementing every time I try to read coils (1), read input registers (3), or read holding registers (4), but I still get 0 bytes in response.
If relevant, I'm trying to read using a python library called pymodbus, https://pymodbus.readthedocs.io/en/latest/readme.html
-
Hi, I've just joined this forum because I have a problem and I can't find the solution.
I've a V700 HMI with a V200-18-E2B Snap-in I/O module.
I need to use this HMI as a TCP/IP slave using port 502.
I have a ladder that works on V130, but it doesn't work on this V700.
could you please help me?
ENAMI HMI 2 Solo Modbus.vlp is the trimmed down version of the program, because I wanted to remove every other variable in order to try to debug my program, I believe this should let me read and write every available modbus address (coils, input registers, etc), but when I try to read coils I get 0 bytes read.
[SOLVED] V700 Modbus TCP/IP slave
in Vision & Samba PLC + HMI Controllers & VisiLogic Software
Posted · Edited by Javier Galaz
changed for clarification
OMG!!!
IT'S ALIVE!!!
Thank you so much to all of you guys.
In order to register what worked:
I believe the culprit was OS version, I'm going to try with Visilogic 9.8.91 and 4.008 (10) OS Version, and come back here to tell you my results.
Again thanks to all of you, you are great!