Is there any emulator available for MBus TCP/IP protocol.
Is somebody using this protocol in SCADA-BR or SCADA-LTS?
Please give me any suggestion how can I test this data source.
As far as I understand your question you are seeking for an alternative to buying hardware M-Bus converter. Unfortunately for what I know there is no free software M-Bus emulator available. If you serious about M-Bus you may consider getting into contact with one of many firms offering services for M-Bus customers. However if you prefer Do-It-Yourself approach and are going to write such emulator yourself take a look at libmbus library (open source C library) using of which may greatly simplify such task.
Related
I study on entropy source using the Random number generator.
So I want to see a kernel source code.
However, I don't exactly know this, and i know this is not known.
Would you tell me about this?
Thanks.
Windows Driver Foundation forbids such actions due to obvious malicious stuff that can happen if the source code leaks
If you have access to enough information about the device you're using, you could try writing a skeleton driver. However, some TRNGs have open-source driver code, so if yours is one of them, you could download that. If those aren't options in your case, unfortunately proprietary software companies do not generally share their source code (though Microsoft does share their code with certain CS departments in academia - if you're affiliated with one, you could look into that).
Here is my question:
Is tere any service or technology to run parallel algorythms on more computer without knowing them?
For example: I write a parallel algorythm. My friends install a simple client app, and if they have internet connection, they can help my calculation with their free processor capacity. I would like to see them like an additional core in my CPU.
If there is no technology like that, is there any unsolvable problems with developing one? (I know there must be a lot problems with code trasfering, operation systems, and compatibility)
I believe that you can use BOINC to set up your own volunteer computing project. But I have no experience of this to report.
Are filter drivers intended to extend system drivers?
Is this their main purpose?
Are they basically just an extra layer that sits between the driver and the user?
This seems overly simple an explanation and I am wondering if I am missing something.
Are there good ways to learn more?
The driver topic is a very advanced one.
To get an overview, you can have a closer look on the Windows Driver Kit (WDK) sides.
If you decide to get into this stuff, then you need a lot of time, frustration resistance and fanaticism.
The first thing you should do (befor you touch the WDK!) is, to start reading a good book.
If you want to develop for windows file system, read Rajeev Nagar's book "Windows NT File System Internals : A Developer's Guide". It's published in 1997, but it's something like the "bible" of NTFS.
For common driver developement you can find books like "Developing Drivers with the Windows Driver Foundation", written by Penny Orwick.
These books describes programming kernel mode software, which is done in C language. So, you should have a good base knowlege on C before you start.
Among others there are the OSR side (www.osr.com) and SysInternals on technet (http://technet.microsoft.com/de-DE/sysinternals), which are truely worth to have a closer look on.
More than the halfe time you spend on reading debug outputs and crash dumps, so it's wise to know what these things are meaning and how to get this information, but there are good books for windows debugging too.
I hope, I was able to give a short overview on the question for the ways to learn more.
In a way yes.
For example, if file system filter driver is for file encryption/compression/security, it is enhancing the file system functionality.
The filter driver does not handle talking to actual devices. They rely on lower level drivers to communicate with device. The filter drivers are add-on to the drivers to implement certain functionality. The active drivers which modify data/request are to enhance vanilla drivers while the passive filter drivers are just pass-throughs without any direct enhancements.
So I think your assumptions are correct.
Will like to hear different views though.
I have a tcp-based application and would like to do load testing for it, I have narrowed down on JMeter TCP Sample and Clif, for now i am leaning towards JMeter because it easier to use, Clif seems to be more complicated and less used.
Any thoughts?
Has anyone used some 3rd tool?
Does anyone have an opinion/experience with getting Clif to work?
We would mostly be looking for open source options so any help in that direction would be extremely useful.
Usually in work I use LoadRunner and JMeter. If LoadRunner is able to create test then it's a fast way. JMeter is much more flexible, because you could write your own plugins or simply implementation of JavaSamplerClient interface. I don't know many posibilities of JMeter, but with java language can perform different tasks. LoadRunner has big weight, rare updates and terrible price.
All of the commercial tools support Windows sockets interface support, up to the ability to record the actual conversation (Loadrunner, SilkPerformer, Rational Performance Tester). Winsock has been a part of these large commercial tools since the mid-late 1990's. All of the above tools offer engagement based models as well, for periods as short as a month. I would suggest contacting the sales organizations for HP, Microfocus and Borland to see what they can offer.
Compared to hand constructing sockets code and then having to engineer the reporting side you may save time and labor hours in the rental of one of the big commercial tools which already sports the dedicated sockets interface combined with the system monitoring and reporting that you need.
I'm trying to create a windows driver that allows a standard TCP/IP socket to be used like a COM Port. I am aware of a number of existing products that do just this, but can find no reference material as to how it's actually done! I understand some of the concepts of windows drivers (bus/function/filter drivers, driver stacks, etc), and have tried reading a book on WDF, but I'm still not 100% sure on where I start if there is no actual backing hardware. If anyone has any links/pointers that will help, it would be much appreciated.
Kazar
Take a look at the com0com project. They also offer an com2tcp driver. As it is open source you can go through the sources and get an idea of how it's done.
Actually this is not a driver, but an app, so it might be less helpful in your task to learn something about driver development, but anyway could be a good starter for some technical insight.