![Rs232 serial interface cable Rs232 serial interface cable](/uploads/1/2/6/6/126610510/905331773.jpg)
The errors seem to go both ways on serial 1 and are a mix of errors, both ways. As your ISP to provide a loop at demarc at both istes and check if the errors still happen. If you're error-free then their line is bad. The second serial (serial 2 to serial 6) shows serial 6 clean and serial 2 abort. XXXXXXXXXsh controllers serial 1/0. Interface Serial1/0. Hardware is DSXPNM GT96K. Idb at 0x70A20B20, driver data structure at 0x675FA45C. GT96K Port Used 2, SCC Num 2. MPSC Registers: MMCRL=0x001B04C0, MMCRH=0x40000000, MPCR=0x00000000. CHR1=0x00FE007E, CHR2=0x00000000, CHR3=0x000011E2, CHR4=0x00000000. Serial WAN Interface Card LEDs Each serial WIC has one LED, labeled CONN for each port, which lights when the serial port is connected. When the port is in DTE mode, the CONN LED indicates that Data Send Ready (DSR), Data Carrier Detect (DCD), and Clear To Send (CTS) have been detected.
All T3 cards I have worked with all show up as serial ports. So after you find your serial port you can do 'int serial 0/0/0' or whatever it ends up being to configure the type as either T3/E3. Hardware is DSXPNM Serial Description: DS3 to Mpls- X0-mn-HFGS/541589/TWQ//-LE C-94/HFGS/ 202473//03 Internet address is 10.252.1.22/30 MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, crc 16, loopback not set Keepalive set (10 sec) Last input never, output never, output hang never.
The “show interface” command on a Cisco IOS router or switch gives you a lot of information. Here’s an example:
There are a number of things we can check with the show interfaces command. Let me describe them:
- FastEthernet/0 is up, line protocol is up: this means that the interface is physically up and that the protocol is operational. When you use Ethernet, the protocol is normally up unless you configured port-security or BPDU guard. When a violation occurs, you might see err-disabled here.
- Hardware is Gt96k FE, address is c201.1d00.0000 (bia c201.1d00.0000): The interface hardware is Gt96k and the current MAC address is c201.1d00.0000. The BIA (Burned-In-Address) is the same. If you would spoof (change) the MAC address then the first MAC address would be the spoofed one, the BIA address never changes. You can change the MAC address with the “mac-address” command on the interface.
- MTU 1500 bytes: The MTU (Maximum Transmission Unit) is 1500 bytes.
- BW 100000 Kbit/sec: The bandwidth is 100000 Kbit/sec (100 Mbit), this information is used by routing protocols like OSPF or EIGRP to calculate the metric.
- DLY 1000 usec: The delay of 1000 usec is the “propagation delay”. This is the amount of time required for the signal to travel from the sender to the receiver. Like the bandwidth, EIGRP uses this to calculate the metric.
- reliability 255/255: When the input and output errors increase, they affect the reliability counter. This indicates how likely it is that a packet can be delivered or received succesfully. Reliability is calculated like this: reliability = number of packets / number of total frames. The value of 255 is the highest value meaning that the interface is very reliable at the moment. The calculation above is done every 5 minutes.
- txload 1/255: This indicates how “busy” the interface is when it comes to transmitting frames. This is calculated every 5 minutes.
- rxload 1/255: The same as above but for receiving frames.
- Encapsulation ARPA: This is the layer 2 protocol that we use, when we use Ethernet it shows up as ARPA (Advanced Research Projects Agency) which is Ethernet version 2 encapsulation. If you use PPP, HDLC or frame-relay on serial links then it will show up here.
- loopback not set: serial interfaces can be “set” in loopback mode, this is used to test the interface. Don’t confuse this one with the loopback interface.
- Keepalive set (10 sec): The router sends keepalive packets as a method to check if there is end-to-end connectivity.
- Full-duplex, 100Mb/s, 100BaseTX/FX: This tells us if we are using half or full-duplex, the bandwidth and the type of interface.
- ARP type: ARPA, ARP Timeout 04:00:00: The ARP type that we use, for Ethernet this is ARPA by default. The timeout is how long entries remain in the ARP cache, by default this is 4 hours.
- Last input never, output 00:00:02, output hang never: This is a router that I just booted, this line will show the last time it received or sent anything.
- Last clearing of “show interface” counters never: All the counters in the output of show interface can be cleared, this shows us when these counters have been cleared.
- Input queue: 0/75/0/0 (size/max/drops/flushes): This tells us how many packets are in the input queue and it’s maximum size (75). Drops is the number of packets that have been dropped. Flushes is used to count SPD (Selective Packet Discard). SPD is a protocol that drops low priority packets when the CPU is too busy so that it can save capacity for higher priority packets (routing protocols and such).
- Total output drops: 0: The number of drops because the output queue is full. When you receive traffic on a 100Mbit interface and forward it on a 10Mbit interface you’ll see congestion which causes packet loss and high delay. Applications that use TCP can use retransmissions but Voice over IP is an application that is very sensitive to packet loss, high delay and a variation in delay which causes jitter. If you see a lot of output queue drops you’ll have to start thinking about implementing QoS (Quality of Service).
- Queueing strategy: fifo: The current queueing strategy is FIFO (First In, First Out). This is the default for interfaces with a bandwidth above 2 Mbps.
- Output queue: 0/40 (size/max): The size of the output queue which shows current packets and the maximum it can handle.
- minute input rate 0 bits/sec, 0 packets/sec: The average rate at which we receive packets.
- minute output rate 0 bits/sec, 0 packets/sec: The average rate at which we transmit packets.
- packets input, 0 bytes: The number of packets that we received and the amount in bytes.
- Received 0 broadcasts: The number of broadcast frames that we have received.
- runts: Runts are ethernet Frames that are less than 64 bytes.
- giants: Giants are Ethernet frames that exceed the IEEE 802.3 frame size (1518 bytes, no Jumbo frames) and have a incorrect FCS (Frame Check Sequence).
- throttles: When the interface fails to buffer the incoming packet then this is considered a throttle.
- input errors: This counter will increase when the interface receives a frame with any kind of error, this includes runts, giants, no buffer available, CRC errors, etc.
- CRC: The number of packets received with CRC (Cyclic Redundancy Checksum) errors. This means that the checksum that was generated by the sender does not match the checksum that the receiver calculated. On a LAN this typically occurs when you have issues with cabling or defective network cards.
- frame: The number of packets that were received with a CRC error and a noninteger number of octets.
- overrun: This is how often the interface was unable to receive traffic in its hardware buffer because the input rate is higher than the interface can handle.
- ignored: The number of packets that the interface ignored since the interface hardware ran low on internal buffers. Broadcast storms and noise can trigger this.
- watchdog: How often the watchdog receive timer has expired. This happens when the interface receives a packet that is larger than 2048 bytes.
- input packets with dribble condition detected: A dribble frame is a frame that is slightly longer than the default. This counter is increased but the interface will accept the frame anyway.
- packets output, 403 bytes: The number of packets that have been sent and the amount in bytes.
- underruns: Number of times that the sender has been running faster than the router can handle.
- output errors: Same as the input errors counter but for sent packets. This counter increases when anything goes wrong with the transmission of the packet.
- collisions: Number of packets that have been retransmitted because of a Ethernet collision, on a full duplex network you shouldn’t see this unless you have issues with network cards, too long cables or repeaters in between your switches.
PLEASE NOTE: This blog was written using features available in TIA Portal V13 SP1 Update 1. Some of the functionality shown was removed in Update 3, specifically the ability to multiplex UDTs. Hopefully the rest of the information will be still be helpful to you! Here at DMC, we spend a lot of time programming PLCs and HMIs.
Crack wincc comfort v13 SP1 Crack TIA Portal v13 License for All Siemens Software Download in Telegram www.Telegram.me/PLC1one +98 911 275 4501.
While we program systems of all types and flavors, I'm personally most experienced with (TIA Portal) and (RSLogix5000/FactoryTalk View). There are a few new features included in that I have found to be incredibly useful in the past few months and have allowed me to be even more efficient in my programming.
Dsxpnm Serial Interface Definition
I'm going to focus today on a series of updates that were added in SP1 that make it even simpler to take advantage of the nested data structures we can create in our Data Blocks - specifically, the ability to share UDTs between a PLC and HMI, link UDTs to Faceplates, multiplex arrays of UDTs, and create simple, powerful pop-ups. Before we get started, let me say that if you're not already taking advantage of PLC data types and Global DBs to build rich data structures in your project, you're missing out. Having come from an object-oriented programming background, I really appreciate what the Function Block/Data Block paradigm will allow you to do in a PLC - it really does push PLC programming towards object-oriented programming. And let's face it, the less time we all spend on repeating tasks and minutiae, the more time we can spend actually programming.
As an exercise, let's pretend we have a project with a large number of simple valves. Of course we like to save time, so we're going to develop a special FB to handle our valves: auto/manual control, alarms, etc. In addition to eliminating the amount of code to be written, this allows us the additional advantage of keeping our future valve logic updates to a single place. Our FB has a few inputs including the feeback signals for open/close, an in-out for our 'valve' data type, and an output for the open/close command.
So, what is in our 'valve' data type? For this simple example, let's create the following PLC data type, udtValve: We've broken our data type into three structures: configuration, status, and control. The configuration group of parameters defines the valve's physical behavior and its unique name. The status group contains all status information about the valve and is used both within the PLC and the HMI. The control group has the open/close and fault reset requests.
I find breaking things up like this makes it much easier to find the right tag you're looking for when programming. For our valve Function Block, fbValve, let's say we have something like this: Now that we've developed a re-usable function block for our valves, let's create a DB to contain all of our valve data. I'm going to create a Global DB and name it dbValves.
Tabit version program full version free. software download windows 10. In it, I am going to create an array of udtValve. Within this data block, I can set configuration values, including valve names, for each of the valves I am going to use. Pink floyd wish you were here full album download zip. Let's imagine we'll be using 10 valves. As you can see below, I've entered configuration values in each valve's data structure. The final step on our PLC is to add our newly written code.
I've created a FB ( fbValves ) to contain all of my valves, instantiated 10 valves (multi-instanced versions of fbValve ) within it, and dropped fBValves into OB1. Now, let's move to the HMI. Let's say we want to put together a simple P&ID of our system showing each of the valves and their status. Let's also imagine we want to allow a user to click on a valve and open a pop-up so that they can get more information as well as control it manually. Let's start with the first task - our simple P&ID. I'm going to grab a simple valve from the toolbox (under 'Elements - Symbol Library') and add an indicator for the valve name.
Under 'Properties - Appearance' for the symbol, I'm going to change the 'Fill Style' to 'Shaded'. This will allow me to add some color animation to the valve: Orange/flashing when the valve state is not known, Grey when the valve is closed, and Green when the valve is open. Additionally, I would like the valve's name to change to Red and flash when the valve is faulted. I could start adding in my animations now, but I don't want to have to redo that process for each valve.
Instead, I'm going to create a faceplate so I can write the logic once and reuse it several times. To do this, select both the valve symbol and the valve name indicator, right-click, choose 'Create Faceplate', and name it 'ValveIndicator'. Inside the faceplate editor, I could create new properties for the fault status, the valve state, and the valve name, then tie each to the appropriate item/animation.
However, this would require linking each of these properties back to the appropriate tag inside of my data structure. With a lot of valves, this could take a lot of work. This is where one of the new TIA Portal V13 SP1 updates will come in handy: the ability to use PLC UDTs (PLC data types) in the HMI. To have access to a PLC data type on the HMI, we will first need to add it to our project library as a type.
To do so, just drag udtValve from the PLC project tree into the 'Project Library - Types' folder: Now, back to our Faceplate. Let's add a new property of type udtValve. Now when we use this Faceplate, we will only need to link a single tag: all of the individual animations and properties will be internally linked, within the Faceplate, to the appropriate tag within our UDT. Below is my Faceplate and the animation for the valve color. Notice in the Properties window that there is only a single property of type udtValve.
When you're finished editing your Faceplate, release the version and let's go back to editing our HMI screen. Select the new Faceplate object and view the Interface tab. Link it back to dbValves.Valve0 by navigating to 'Program Blocks - dbValves'. Now we can add more instances of our Faceplate to the screen and simply link a new valve instance to each - nothing to it!
So, getting back to our original goal - we've succeeded in creating a simple Faceplate that can be linked directly to a single tag (UDT). The second task we set out to accomplish was to create a pop-up that can show more detailed information for any given valve. In this case, we want to create our pop-up so that it is capable of being opened to display any one valve at a time.
To do this, we will need to set up a 'multiplexing' tag to look at different valve instances in our array of udtValve. Autocad 2015 2012 for mac download. If you've tried this before, you may have run into issues. Luckily, there have been a few updates in V13 SP1!
Dsxpnm Serial Interface Serial
Tia V13 Sp1 Download
First, let's set up our 'multiplexing' tag. We'll need to create an 'index' tag locally on the HMI that can be used to choose the active valve. In my default tag table, let's first create a local Index tag (with type of 'UInt'). Next, in your project tree and while still looking at your HMI tag table, select dbValves. From the 'Details View' (see screenshot below), drag Valve1 over to your HMI's default tag table and change the name to IndexedValve: At this point, notice that the HMI Tag is linked to a specific valve within our array of udtValves, dbValves.Valve1.
Now, select your new IndexedValve tag and open up the property pane below. Select the empty drop-down box for 'Address' and choose 'HMI Tag'. Now, navigate to your HMI tags and select 'Index,' the internal tag we created a few moments ago. At this point you will notice that the PLC Tag name shows ' (instead of dbValves.Valve1), and the 'address' now shows you a dynamic link to array. By setting our Index tag, we can now vary where our IndexedValve is pointed. Now, let's create another faceplate to show whatever information you would like. I've created the faceplate below and configured a single 'udtValve' property to link it.
It will give the user the ability to switch control modes, open and close the valve, and see status information. The last piece of our puzzle is the pop-up. This is another great addition to TIA Portal V13 SP1 (for more info, see ). To create a pop-up, navigate in the project tree under your HMI to 'Screen Management/Pop-up Screens'. Add a new pop-up screen and add your new faceplate to it. Select your faceplate and view the 'Interface' tab under Properties.
Now, link your IndexedValve to the faceplate. Finally - our last step. Add an invisible button and place it over one of the valves on your P&ID screen. You can do this by using a button from your HMI toolbox and configuring it to be 'Invisible' from within the properties. On the button's Click Event, add the following: Now, when a user clicks on a valve from the P&ID, the triggered event will first update the index of the valve that is chosen, and then show the pop-up screen. There you have it! We've taken advantage of several really great features that were added in TIA Portal V13 SP1: the ability to use PLC data types (UDTs) on an HMI, the ability to link a faceplate to a single UDT, the ability to multiplex an array of UDTs, and the ability to add a simple pop-up.
As I'm sure you can imagine, there are many potential uses for these new features and this example is just one possible application. Good luck programming and let me know if there are any new features you've found that can help me be more efficient in the future! Learn more about DMC's and solutions. Monday, March 26, 2018 10:09 AM Dear Jason Mayes, Your post is very helpful for my project. I create udtActuator and then database dbActuators. But when i start to write networks in fbActuator (simple actuator) the tags aren't recognized by TIA and appears red underlined.
Siemens Tia Portal V13 Sp1 Download
So its look like a don't link tags from db and fb. I think that this should be done in declaration table. But i don't know how to link them each other. Can you explain me please how to declare db tags with fb addresses so they can work together.
Thank you in advance. If you prefer you can sens me this project to anatoliy dot miev at gmail. Thursday, July 13, 2017 10:07 AM #Greg - It should certainly work for WinCC Professional in V14/V14 SP1. What kind of application are you developing?
I believe the screenshots should be relevant for Comfort Panels or WinCC Advanced applications. If using a Comfort Panel, make sure you're using at least version 14.0.
As for the 'Address' being grayed out. Make sure the HMI tag you are trying to 'multiplex' is only an element of the array on the PLC - not the array itself. You can do this by expanding the array on the PLC and dragging a single element to the HMI tag list. Then select the Address dropdown and change the 'Index tag' selection to be 'HMITag' - now you should be able to browse to and select the index tag you want.