- This topic has 18 replies, 3 participants and was last updated 9 years, 4 months ago da
.
-
Post
-
I was able to connect and view the web server homepage SlimLine via USB at 192.168.1.122. Unfortunately when I enter username and password (Admin and Admin) both Firefox and Explorer browsers tell me connection error the page cannot be loaded. So I can't change the COM port values.
Do you have any advice? I have also restarted but nothing.
Unfortunately there is a bug in a link in the configuration pages, I am attaching the updated version of the configuration web pages for download (Mdp020b430).
To transfer the pages you need to connect in FTP (See post) and overwrite the files in the folder System.
I tried with Filezilla both with address 192.168.1.122 port 21 and with the one in the guide 192.168.0.122 but I think it is for the ethernet connection, not my case which is USB.
Filezilla says:
Status: Connecting to 192.168.1.122:21…
Error: Connection timed out
Error: Unable to connect to the server
Status: Waiting for a new attempt ...Also in this case I used Admin Admin as username and password.
If the connection is via USB the default IP address is 192.168.1.122. You have correctly set the parameters in Filezilla by looking at this screenshot ?
If necessary, use the Windows Explorer (the one that allows you to view the contents of your PC's disks). By typing in the ftp address bar followed by :// Username:Password@Device IP address, you can view the file system of the SlimLine (Screenshot). Now you can operate on files as you normally do on the PC even with drag and drop operations.
I was able to update the files on Slimline with Filezilla… simply changing the mini-USB cable… I restarted the PLC and the PC but the problem of not logging into the Web server persists.
It's not that new access credentials have been defined, if you connect to Telnet (Port 23) can you log in with Admin, Admin? In Reference manual for Telnet CPU commands SlimLine find all available telnet commands. I recommend that you upgrade the operating system (Code SFW184 ** 00) see KB.
The unit has the firmware Software code SFW184A870 I saw in the list SFW184A890 download this?
I install Toolly and try.Toolly does not start writing the firmware, how should the COM port be set 115200, 8 bit, no parity, no flowcheck?
Are the connection cables good for GND, TX and RX or do the others want too?
As indicated by the FAQ I connected the RS232 cables. I moved the jumper with the PLC off to Firmware Upgrade. I have activated Toolly and turned on the PLC, but it seems to do nothing, more and more "..." characters appear in Toolly but the process bar below does nothing.
Toolly automatically sets the correct serial parameters, the KB shows the cable construction diagram. For the firmware upgrade, however, the signals Tx, Rx and GND are sufficient. Be careful not to confuse firmware upgrades with bootloader upgrades. You must perform a firmware upgrade and in this case there is no need to move any jumper on the CPU module, everything happens automatically by switching on the CPU module while Toolly displays the ...
I put the jumper back in its original position. I have always performed a Firmware Upgrade, but it seems that Toolly cannot download the firmware during the Send. The PLC starts normally and after 3 or 4 seconds from power on the started PLC program is available. It seems to skip the firmware update completely. The steps I take are:
1-I turn off the PLC
2-I leave the Jumper on Normal Operation
3-Premo Send on Toolly
4-I turn on the PLC
5-I find myself with the PLC started and Toolly continuing to add “…” in the window
6-I'm going to check on the Web Server and the firmware is still the previous one SFW184A870.Do the additional modules connected to the PLC unit need to be disconnected? Can the USB cable cause problems during the operation? Is the COM0 of the PLC that of the CPU module?
The maneuvers you do are all correct and Toolly should block the CPU module from starting and transfer the new firmware. The COM port you need to use is COM0 (The one next to the expansion connector) of the CPU module, the extension modules are irrelevant as well as the USB cable.
Have you checked that the COM port set in Toolly is actually the COM port of the PC you are using?
Also check the functionality of this serial port, you can connect pins 2 and 3 to each other (Loopback) and through the Toolly terminal try to send characters you should see them again displayed.
In my experience when you could not load the firmware it was always a cable problem, customers using Null-Modem extension cables, broken extension cables, cables with badly pinched RJ45 connector. Check with a tester that the cable is actually wired as described in the FAQ and that it is connected to the serial port of the PC. If you use a USB / Serial converter, make sure it has the correct voltage levels on the signals (Topic).
You can also connect in serial with LogicLab to the CPU module and try if you can transfer and / or debug the program (Topic).
I was able to update the firmware of the slimline. The RJ45 cables were crossed and therefore I was wrong between the green-white and blue-white cable, but the problem persists and I cannot log into the Web Server. Let's try to bypass the problem.
I have to connect to the COM0 port of the SlimLine a Weintek touchscreen the MT6050ip with MODBUS (I think you can not change the settings) and to the COM1 port (the COM port of the expansion module) a PC for receiving ASCII strings with data.
How can I set the settings from LogicLab, I saw another discussion (link) I tried the code with Toolly but it only works for COM0 where I have the character echo ... I tried to set both COM1 and COM2 with that code, using the COM port of the expansion module for that but it doesn't work. If you have other possibilities to fix the Web Server then please advise me.
I do not understand why you can not log in, you have used your username and password admin (Case sensitive) However, for your needs it is not necessary to modify the configuration of the CPU module, if not used by the user program all COM ports of the CPU module support the Modbus RTU protocol. Then on the Weintek panel you only need to set the 115200 baud rate, and, 8 and define the 1 node as a Modbus node (See manual connections). In the Weintek terminal section you will find many examples of use (In this topic you will find a startup program) .I remind you that for the Modbus protocol on the extension module ports it is not natively managed but you have to create a program that manages it (You can find examples in the forum). Your CPU module has only one serial port COM0 so the advice is to connect the operator panel to this port and this is also why the echo program you mentioned works on this port. To access the serial ports on the CPU module, use the function Sysfopen defining the name of the port to use. There are extension modules that are equipped with serial ports, access to these ports is exactly the same as that of the ports on the CPU module, you must define the name of the port to use the definition PCOMx.y where x indicates the address of the module and with y the port number present on the module. (Example PCOM0.0 defines port 0 present on module 0, PCOM1.2 defines port 2 present on module 1 (Topic).
Thanks, the analog expansion module in use has address 16 # 01 in fact using address 1 in the function block SysGetAnInp I can take an ADC value and decide whether or not to switch a relay output of the CPU module. It only has one COM port and the manual attached in the box is called COM0. The problem is that by setting: Sysfopen ('PCOM1.0', 'rw') Toolly is unable to receive the echo characters. The module is a PCB126B110 I read now that perhaps the RS232 is not usable by the user (See link). Does that mean I can't use it? If so maybe I need the PCB126C110 version.
- You must be logged in to reply to this topic.