Bryll

Has someone here used BACNET with a FX3U ? Are there any protocol converters available ? Any ideas will be much appreciated.

TIA-Portal for the 1200 and 1500 series. Step 7 (classic) for the S7-300 family, and if not using PCS7 also Step 7 for the S7-400. Was recommended by a Siemens sales rep. not to use the TIA-Portal for S7-300 and S7-400 PLC's

Thanks for your answers, have to find the "bug" then

I have to wake this old thread up, since my questions are about the R-registers. The setup is a FX3U connected to a Beijer E1101 panel. I found the R-registers quite handy for data storage since they are battery backed. Wrote a small FB that traces certain events and logs a time stamp and current login level in the panel. There's no problem to show these registers in the Beijer panel, so I don't have to use any D-registers. But it seems that some of the data is lost during a PLC reboot. Will check the code again, but I'm almost sure it is as it should. Anyone else discovered data loss in the R-registers after a reboot ?

You can create UDT's under the tab "PLC data types". I attached a small picture to make it a bit clear what I mean.

PLC: FX3U Software: GX IEC Developer 7.04 Tried to create a function that creates a short pulse with a fixed pause to open a relief valve when the system pressure reaches a certain level. This to prevent the systems safety valve to open. When doing this in the code was the active time of the pulse not constant. So, I made an interrupt routine (time based) and increments a counter value for pulse output high length, and the same for pulse output low length. When simulating overpressure by the analog pressure register is the function activated. But, the funny thing is that you can hear the variation of the pulse length, thought that the interrupt would cure the variations of the pulse length, but no. Any suggestions ?

Hello again, Yes, I will rewire the outputs to the PLC outputs, and of course also use the REF instruction. Didn't think of the delay caused by the Modbus communication until you asked about the outputs. Guess the brain stalled due to other issues (HW) we had at the same time. We actually trashed a flow sensor, a compressor and a dew point sensor. All silly expensive EEX classed items Thanks again for your help

Hello Inntele, You got me there Your question made me aware of the fact that the output used is on a distributed I/O unit with Modbus TCP/IP communication. Not strange at all that I get a pulse variation. I have to rewire the output to Y0 - Y7. Thanks a lot

Anyone here ever tried to use a Modbus TCP connection between an E1151 (Beijer HMI) and a HIMA HIMax system? We are facing some problems when trying to exchange data between these two systems. Tips and tricks are much appreciated

Select from the menu "Extras -> Options" and then in the window that pops up "Project options -> Compiler". There you can disable warnings that you can consider not to be important. Guess you have to increase the "Word range" in the "Systems variables" tab as well (same window). Edit: This is for GX IEC Developer, don't know how to do it in the other programs.

No, you have to re-write the code

The customer decided that we use Modbus RTU communication and the end customer installed an anybus converter RTU<->TCP converter. When commissioning the system the end customer decided to skip the communication part to their DCS. All the HW and the expensive RTU driver dongle for nothing, well they have it installed, but it's not for any use (at the moment).

No worries, I Think I figured it out now. The inputs and the outputs at each ET200S starts at byte 0. First digital input address is 0.0 and first digital output address is also 0.0. In the computer system do we need to specify how many READ and WRITE bytes the telegram shall consist of. So if I send a "1" to PB address 15, telegram byte 3.2, it means that output "2" of the third output module is activated. Just to install the GSD file to the computer system and get going

Hello, We shall from a computer system communicate to a couple of Et200s nodes equipped with only digital inputs and outputs. The Communication is std profibus. I guess each input/output "slice" will take one byte, even if it's a four input or output unit. What is the start address for inputs ? What is the start address for outputs ?

I'm trying to control the speed of a G120C via profibus, but it will trip out when any changes are done to the speed value. The unit was commissioned by another guy, and he doesn't have a clue where to look. We can start and stop the unit, but it will stop at any attempt to change the speed. I was told to look for a parameter allowing it to be controlled remotely, but wich one is it ? As usual when it comes to Siemens, the manual sucks. I'm using a function block for controlling the drives (13), and the older 12 is responding correctly to any change. Anyone here that has a clue what parameter to change ?

You can create it in a DB. Define the "name" and for example the data type select "Array[1..10,1..10] of Int". Best of luck

I once had some issues when using 2 Modbus server blocks in a FX3U Project. Made some Changes to the system at the same time I changed Connection 2 to use port 1025 instead of 502. It's been working for quite some time now, but I really don't know if the port change was the solution to the issues.

Try something like thisExample.bmp

   Sorry, was busy programming.

What software are you using ?

I used the function DEVAL first to convert the ASCII string to REAL value, then REAL_TO_DINT to get it in DINT format when building a communication protocol to an old chiller unit. If you need interger value, use REAL_TO_INT after DEVAL.

Could it be that you need to perform a byte swap ?

I was recently recommended by my Siemens sales contact to use Step 7 classic for anything else than the 1200 or 1500 system instead of the TIA Portal. This is something I have been told: -You can import a taglist to the Portal (V13) and create only the panel in the TIA portal and the PLC program in a better suited software like Step 7 Classic.

For FX system D8013 = Seconds (0-59) D8014 = Minutes (0-59) D8015 = Hours (0-23) D8016 = Day (1-31) D8017 = Month (1-12) D8018 = Year (0-99) D8019 = Weekday (0-6) For Q system SD210 = Year, Month (bit 0-7 = Month, bit 8-15 = Year), 16#9307 = July 1993. SD211 = Day, Hour (bit 0-7 = Hour, bit 8-15 = Day) 16#3110 = Day 31, 10 a clock. SD212 = Minute, Seconds (bit 0-7 = Seconds, bit 8-15 = Minutes) 16#3548 = 35 Min. 48 Seconds.

This Block will calculate it for you, handy to have in the library