Csoto
-
Posts
8 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Events
Blogs
Downloads
Articles
Media Demo
Posts posted by Csoto
-
-
2 hours ago, Flex727 said:
The COM 1 that Unitronics is referring to is COM 1 on the PLC. COM 1 on your PC is different. The driver will choose a COM port on your PC and you should use that. The COM port number on the PLC and the COM port number on your PC are totally unrelated.
Thanks, is what I imagined. But I have not managed to identify the COM1 in V570, is COM1 the PORT1?
-
On 3/7/2021 at 3:54 AM, AlexUT said:
Csoto,
Change communication Timeout to10 sec and test again.
What USB-to-Serial converter model do you use?
B.R.
Thanks, I'll try 10 seconds. I have been using a USB to MiniUSB cable via MiniUSB port.
On 3/8/2021 at 3:12 PM, Flex727 said:No, you can use the USB-MiniUSB cable to connect to your PLC for Firmware update. Just be sure you have the correct driver installed from VisiLogic.
Thanks, when the program indicates "COM 1", does it specifically refer to "COM 1" on my PC?
-
On 3/6/2021 at 3:49 PM, kratmel said:
Thank you Aus.
As my professor taught me many years ago: The device can be well repaired only when you have established exactly why it failed.
Therefore, this topic probably lacks a history of the conditions under which and how long the PLC worked before this problem arose. Especially in terms of preventing interference and overvoltages caused by the absence of RC on AC coil and diodes on DC coils.
As correctly noted by one of the gurus of our forum - Vision PLC is almost impossible to destroy by software - there is always a way to restore to working condition.
However, in this case, I suspect that something happened at the hardware level.
Hi, thanks, because it had been operating without changes or problems, I also suspect that it is a hardware problem. But first I want to see if it is possible to solve it via software, since if it is hardware, the solution is more complicated and beyond my current skills.
On 3/6/2021 at 3:51 PM, Joe Tauser said:Those were the exact thoughts I had. I am not familiar with BGA reballing so I Googled that up. Wow - that is not a skill I have.
https://www.youtube.com/watch?v=EjAdz8jQL4k
Joe T.
-
On 3/6/2021 at 10:21 AM, Ausman said:
Does this mean it has been off for a fairly long time? As in CVirus shutdown?
It shouldn't make any difference on this error, but did you actually check the battery condition and substitute a new one? Just to make sure all the ducks are lined up properly.
And gee whiz, doesn't Kratmel persist in repairing something. Well done!
cheers, Aus
Hello, no, it has been operating for the last 3 years almost non-stop, the failure was noticed the day after it happened. Changing the battery is also in the plans, I haven't done it yet, but I will. I appreciate the advice.
-
On 3/5/2021 at 8:28 PM, kratmel said:
Hi, if panel is new maybe best solution - replace it under warranty.
I found the same problem with V1040. I worked around this panel and do some test. At the test i used cooler and heater hardware for rectify chip with problem.
After step by step confirmation i found that grafic chip is the main issue.
If i cool this chip before panel start - i see BOOT2.2 in identification and BOOT load process started with succes.
And after correct download of all firmware and project - panel started. After some time of normal work - the same issue happend.
I asked service for bga reballing grafic chip. Process was prepeared via bga reballing machine.
After this panel sucessfully started with no issue. I load program and test panel in all possible mode. Problem solved.
Try to use older software (65 version for example) and PORT 1 (not USB) for firmware download.
Also try to download firmvare parts separately - in Advanced mode.
Hello, thank you, the equipment is already 3-4 years old, the warranty is no longer an option. Sorry, but I don't know what "cooler and heater hardware" refers to.
I tried with the version of Visilogic 8.0.1, for others the website tells me that I should send an email to support, I will. Regarding the connection, I have been using the USB-MINIUSB cable and seeing the comments I understand that I should be using “Port 1” with a USB-serial cable for this purpose, is it correct?
-
Good day, I come to request your help with the following problem. Returning to the plant, we found our V570 plc with the following error screen.
Prior to that, it was operating normally and no modifications had been made. I have followed the procedure that I found in the forum:
As follow
But it always fails in step 3 "installation of PLC BOOT"
I have also disconnected the battery for 1 min, there were no changes.
Is there any other method to fix the problem?
Thanks in advance
-
Good day. I´m new at using PLC so i reach to you for some guidance.I have a PLC v570 and i need to register a table when the bobine is turned on or off, in other words, registering 0/1 (or off/on). I´ve registered other information in the table before without any trouble but with the bobine´s registry i found myself a little lost. I'd really appreciate your help. Greetings.
PLC V570 Factory Boot "Boot error"
in Vision & Samba PLC + HMI Controllers & VisiLogic Software
Posted
Previously I installed the USB driver and it operated without problems until the failure occurred. And as for the configuration for serial communication, I have it as indicated:
https://content.invisioncic.com/r129856/monthly_2021_03/imagen.png.4bc4b46f71c82361edca523943d26d9b.png
And it works fine until step 2 of the installation of "Binary Library version".