I want to design a carrier board for NI sbRIO9607 mainboard, which has a gigabit ethernet port pinouts. However, I want to enlarge my system by SFP modules. Hence, I added a SFP Cage and SFP Connector into my carrier board design. However, I could not find a reference schematic design for SFP Connector.
You may find a SFP Module's related SFP Host Connect Electrical Interface and Pins Descriptions by clicking the link. And you might find the GBE Reference Schematic by clicking this link.
Now, the question is, how can I put SFP instead of the GBE? Is there any reference schematic design for SFP connection or SFP to GBE conversion?
Thanks in advance.
Kind Regards.
SFP is a form of GbE, just without the PMD.
You can find all about SFP at snia.org, specifically in INF-8074i. There's a schematic on page 23.
Note that the SFP interface uses single unidirectional lanes while 1000BASE-T, the "GbE" you're referring to, uses four bidirectional lanes. You'll need to access the GbE interface before -T PMD encoding.
Related
Question background:
My MFC CAsyncSocket-based socket code has worked fine in the lab for a long time, until it didn't (see how to determine socket interface type). It's design was based on the Microsoft Docs sample code which sequentially walks through a linked-list of socket interfaces keyed on socket family (like, AF_INET, AF_INET6, etc). With Remy Lebeau's answer to my question, I am now able to list the details of any interface my users might encounter. But as Remy points out there are MANY MANY interfaces out there. "Out there" is quite broad for me since my architecture is that of a dApp (aka, no servers), meaning I won't know my user's precise interface environment in advance. That leaves me with an interface selection design problem.
My question:
How do I select an interface when I don't know the interface environment of virtually all my potential users? There are potential indicators like an interface's Description or Friendly Name I could use to narrow down my selection resolving code. There is an interface structure member called IfType defined in ipifcons.h which contains 281 types. I could perhaps choose a subset from these. There is also a GetBestInterface function, but I don't know if that would work all the time or what its intention is.
I am looking for some guidance on this issue.
Basically, I would like to creat my own piece of software something a la communication protocl between PC and PLC.
I would like to read real time values from PLC and display them in a table for example Data Base, OPC table, Excel and write to PLC from PC in real time mode as well.
The whole point is I would like to access this data via ethernet port. How I can do it ? I do not want to use 3rd party software. I want to create something my own.
Choose any programming languages like C#,VB.NET and use opcdaauto.dll ,it is free dll for OPC Foundation members
You can easily get the live data from the OPC
or use dll provided by the OPC Server which you are using
As already mentioned, OPC-UA is probably more preferable, otherwise, there are commercial libraries such as InGear and open projects on GitHub.
If you actually want to implement your own low level drivers, they will depend on the PLC manufacturer. For example:
If you are working with Allen-Bradley, you will have to implement Common Industrial Protocol (CIP).
If you are working with Siemens, you will have to implement S7 Communication (S7comm or S7 for short).
If you search GitHub for various search terms related to Allen Bradley CIP and Siemens S7, you will find many starting points for communicating directly with these controllers.
I have opnet 14.5 I am trying to find a Mobile Node with dual interfaces one for 802.11e (WLAN) and the other for 802.16e (Wimax) but it seems it is not there do opnet 14.5 has this node if no do I need special License ?.
thanks,
I would build a custom mode using OPNET Modeler with both interfaces in the model. You will have to design the connections and rules. Is it supposed to be a crossbanding relay or bridge or is it supposed to be a single endpoint node (like a computer) that acts as a source and sink only? Those are the questions you need to consider. If the latter case and you have a wired+wireless model, you might try replacing the wired interface with a WiMax interface, resulting in two transmitter/receiver pairs (WiMAX vs. WLAN). I'm not sure about the licensing (you will probably need Modeler + their wireless license among their plethora of license types), but I'm sure Riverbed/OPNET customer service will be happy to assist.
I'm trying to implement the wireless m-bus protocol on an STM32/CC1120 system, but I can't find any useful documentation about the wmbus working principles or any implementation examples.
Can anybody, please, help me find some tutorials/docs/specs ?
Thanks :)
The wireless M-Bus protocol is a part of the european norm EN 13757.
There is a whole series of documents describing the different aspects of M-Bus. Part 4 is for wireless M-Bus.
You can buy the documents at beuth. You'll certainly need part 4 for wireless m-bus and part 3 for detailed decoding of the contained m-bus records:
EN 13757-4 (W-Mbus)
EN 13757-3 (Application Layer)
If you don't want to directly invest money, but learn about the basics, you may also want to have a look at the OMS (open metering system) specification which is for free and based on the wireless-m-bus protocol. Keep in mind that not every wireless m-bus meter is necessarily a OMS meter but it could still help getting you started into the subject.
http://en.wikipedia.org/wiki/Meter-Bus
I also found the description of M-Bus proto in docs for ODIN OD4110 energy meter. But the sources are hard to find. I also need one just to communicate and log the consumption.
There are several libraries available:
jMBus: supports wireless and is based in Java
Mbus4J: based on Java
libmbus: don't support wireless, only wires, based on C
Using one of these helps coming around knowing the full M-Bus communication protocol or buying the documents.
Having a hard time understanding the MSDN documentation on the IP Helper Functions. Whats the difference between an adapter and a network interface?
An "Adapter" is a piece of hardware.
A "network interface" is a software construct.
Usually, there is one network interface per adapter.
But there may be network interfaces which are not from an adapter.
And there may be multiple interfaces per adapter.
The MSDN docs are quite large. Here is a quote from the Managing Interfaces section that might help clear things up:
There is a one-to-one correspondence
between the interfaces and adapters on
a given computer. An interface is an
IP-level abstraction, whereas an
adapter is a datalink-level
abstraction.