Profibus Master Simulator Software Free Download |TOP|
Terresa Beckley
when connecting to a device with Output data the simulator constantly writes data to the target, to all of the defined outputs. Is this simulating the way a real Profibus DP master will act? Or is this just the simulator?
The PROFIBUS master simulator is a simple universal tool for the data exchange with PROFIBUS-slaves via PROFIBUS-DP. The PROFIBUS master simulator can exchange data with many PROFIBUS-slaves, even without a type file and without PROFIBUS master data. In addition to the master simulator, we also provide software for operation with the Deutschmann Gateways.
Has anyone ever found a DeviceNET Master simulator they like or have used? I have a need to test several DeviceNET slaves. I would also like to toggle some of the I/O using the simulator in the DeviceNET slave. I see a couple online, but I am wondering if anyone has tried any of these.
The starter kit comes with a PROFIBUS master simulator to allow you a simple way for you to test your module. It is a simple universal tool for testing the data exchange with PROFIBUS-slaves via PROFIBUS-DP. The PROFIBUS master simulator can exchange data with many PROFIBUS-slaves. The tool includes both software and a PROFIBUS Dongle for connecting your PC to the Starter Kit on it's PROFIBUS connector. This master simulator supports the PROFIBUS DP V1 standard. A version that only supports PROFIBUS DP V0 is also available - select from the drop-down list above.
If, on the contrary, you are indeed referring to Profibus I'm afraid there is nothing on the open-source front that you could use as a Profibus slave stack for the RPi. As you say, there is a master stack (PyProfibus) that works well.
If the target is to build a Profibus network for educational purposes or in-house use you can use the BeagleBone Black or BBB SBC, which is more or less the same cost as the RPi. Unfortunately, the Profibus stack software (both master and slave) does not run on Linux but on TI RTOS (a lightweight OS for several Texas Instruments processors). To comply with the hard real-time requirements of Profibus, this software takes advantage of TI's Sitara PRU-ICSS (Programmable Real-Time Unit Industrial Communication Subsystem), which is, oversimplifying a bit, a couple of microcontrollers integrated together with Sitara's SoC. This means, obviously, this software won't be portable to any other hardware (other than TI's Sitara family).
Are you interested in the product Mts Sensor 401 727 Profibus master simulator from manufacturer Mts Sensor with code 401 727? Contact us now and get offer. Imtek Engineering, the fastest and most reliable industrial equipment supplier in the world, will offer you the best offer!
You mentioned tools. You cant go wrong learning gcc and binutils, learn how to cross compile, at least for the supported platforms (usually involves --target=msp430 --prefix=/something for example). Supported platforms for the mainline gcc and binutils is a moving target so avrgcc and mspgcc and the like are basically done for you. You need to learn to write linker scripts, how to write your C code so that for example fixed tables show up in the rom not the ram. Also get a feel for disassembling the binaries, you need to insure that the tables are in the right place, insure that code is where you think it is, that the vector tables and boot/startup code are where the processor needs it to be to boot. Also doesnt hurt to find out what the compiler optimizations do and what C code looks like when compiled to assembler/machine code. if possible dont limit yourself to gcc/gnu. llvm is a strong player, it has the potential for passing gcc by as a better tool. You may have already used sdcc. try the eval versions of kiel, iar, etc. You will find quickly that there is a lot of grey area in the C/C++ standards and each compiler interprets those differently, also dramatic differences in the quality of the code produced from the same high level source. If you stick with this profession there will be times when you are forced to use a not so great compiler and have to work around its warts and weaknesses. In the desktop business you can often get away with refusing to use non-standards compliant tools. In the microcontroller world, sometimes you get what you get and that is it. Sometimes you get vendors that modify/enhance the C language to meet their hardware features or supposedly make your life easier (rabbit semi and xmos come to mind). (xmos is a very attractive platform for many reasons, I consider it advanced, but from the sounds of your experience you are likely ready, the tools are a free download, really good simulator, important to learn to study .vcd/waveforms of your code executing).
maybe get a formerly dallas semi, now maxim I think, one wire device. Like their temperature sensors. Even more painful than i2c and mdio with their bidirectional data bus, this one wire thing, is one wire (and ground). Power, master to dependent and dependent to master all on one wire.
One nice thing about the Microchip line is that a single programmer/debugger works accross the whole lot. If you're serious about doing this professionally, get the Real Ice. To save a little money, you can get the ICD3, which is just a slightly stripped down Real Ice. The one thing it's not is a ICE (dumb marketing strikes again), but it is a good in-circuit debugger. MPLAB, their IDE debugger and simulator, also works accross the whole product line.
In the hardware configuration of the propulsion simulation system, five dSPACE real-time simulators are used to form a multi-processor system to implement the functional simulation and hardware interface simulation of the 5-segment propulsion power devices. The corresponding relationship between the subsystems of the 5-segment propulsion simulation subsystems and the dSPACE real-time simulators is shown in Fig. 3.
Five dSPACE simulators communicate with each other through fiber optics to form a multi-processor system that enables real-time information exchange. The propulsion simulation management subsystem can be connected to any dSPACE simulator through an Ethernet network cable, enabling information exchange with 5 dSPACE simulators. The five dSPACE simulators receive instructions from the converter control units and converter peripheral control units through conditioning modules, and feedback voltage and current information. The conditioning modules are used to transform the actual interfaces of the propulsion control system into the signals that the dSPACE simulator can receive. The five dSPACE simulators receive the commands of trackside switch stations from the motor control units via the Profibus network and feed back the status information. The dSPACE simulator 2\4\5 feeds back the position information of the maglev vehicle to the corresponding motor control units through UDP interface respectively, in order to realize the position closed-loop control.
dSPACE real-time simulators use CPU + FPGA architecture, configured hardware boards includes DS1007 processor board, FPGA board and its piggyback module, Profibus board and D/A board. The DS1007 is connected to other boards via PHS bus and to the propulsion simulation management subsystem via Ethernet interface.
The FPGA board has 100 MHz clock period. It can be configured with 32 digital input/output channels and 12 analog input/output channels. The use of FPGA's high-speed computing capability can achieve the computational tasks of mathematical models with high real-time requirements, such as converters and long stator linear motor mathematical models. Because each FPGA board has a limited number of digital I/O channels and analog I/O channels, each dSPACE simulator requires the configuration of four FPGA boards to implement the mathematical models of two sets of converters and a set of long stator linear motor.
dafc88bca6