SPICE protocol extension - kvm

I am doing a project that extends SPICE. I need to send some custom data between server and client. I beleiev this is done by adding a custom channel to the SPICE protocol
I've got the source code, but it's huge and overwhelming. Can anyone give me a few pointers as to how to start, or direct me to a similar project so I can refer?
Thanks in advance

I suggest to start reading the "SPICE for Newbies" document, then moving to other documentation. It will give you some introduction on the architecture of SPICE, the protocol, standard channels, etc.
Available on spice-space.org/documentation.html

Since spice-gtk 0.15, and qemu 1.4.0, you can set up arbitrary channels by name using the "Spice port", see spicy.c code for an example of usage.

Related

Endianess (Big Endian/Little Endian) support in plc4x library

I want to check if there is support for endianness(little endian/big endian) in plc4x modbus library to process the response based on that . I could not find any documentation or example on how to use if it exists.
So, request to same some links here if available.
Right now we currently don't support this, but we are aware of an option to fix this. Till now we haven't implemented any support for this mainly because none of our core contributors has access to such a Modbus device. If you have one particular device in mind, could you please name the Type an model or if you could provide us with such a device ... perhaps we can come up with an implementation.

Nnanomsg bus routing support?

I have been using NNG (C++) - now I need to write a C# plugin to read the NNG NanoMSG messages. But I am moving from pub/sub to a bus/mesh protocol. e.g.
https://nanomsg.org/gettingstarted/bus.html
Does nnanomsg support that?
What switches on the socket (options do I need) e.g. NN_BUS? NN_SOL_SOCKET?
The last PR merged included a Bus example. That said, I haven't used the Bus protocol.
If you're using nng, there's also a C# wrapper for that called csnng. I believe it doesn't include the nanomsg "compat" API, but it includes the nng bus protocol.
Not that it's a substantial amount of work, but I forked both NNanomsg and csnng to make .Net Standard libraries.
Don't know why the question should be marked negative. Although no one answered, I went implemented it with: https://github.com/mhowlett/NNanomsg
and the answers to the questions are:
Yes NNanomsg works fine with C++ NNG
Yes it has no problem with BUS protocols, and there are examples in the github.

What is the difference in dcm4chee arc light and DCM4CHE?

I want to about the differences of dcm4Chee arc-light and DCM4CHE. I got a download of DCM4CHE from here and DCM4CHEE Arc Light from here, but I don't know which one is better to use and what are the main differences.
I am new to PACS server and DCM4CHE, so please give me some example of blog from where I can find more material/data to understand differences.
DCM4CHE is a DICOM toolkit. Use it for some command-line tools or to write your own Java, DICOM applications.
DCM4CHEE is a PACS archive. It is used, primarily, to store images. I suspect this is the one you want if you're looking for a PACS. See their wiki page for more information (https://github.com/dcm4che/dcm4chee-arc-light/wiki).

Is there any documented example of using a custom sensor say TMP35 with cumulocity using Java

I am having a hard time understanding where exactly do we bind the hardware for example a TMP35 temperature sensor with the software (i.e. in the Java API).
Is there any documented example for this or any custom sensor (where the driver isn't already available)?
Or can anyone outline the approach to accomplish the same?
Do I need to extend the c8y.lx.driver.Driver class?
Any pointers appreciated.
I believe that TMP35 has no means of communication to the cumulocity server. So maybe anyone can please provide a way to make a custom sensor (which has a means for communication as well and is Java-enabled) link with Cumulocity? That is what I am interested in knowing?
I know that there are some certified devices which are being supported out of the box.
There are two steps:
Get the data from your analogue sensor with Java.
Send the data to Cumulocity.
Step 1 is unrelated to Cumulocity. You need an ADC, and Google provides a few examples on how to connect those (like http://www.lediouris.net/RaspberryPI/ADC/readme.html).
Step 2 is then quite simple. Create a subclass of "MeasurementPollingDriver" and implement run(). Inside run(), query the sensor using the method from Step 1 and convert that into a measurement. Send that measurement using super.sendMeasurement(measurement). Here is an example.
If you have a device library with callbacks, you could just copy the code from MeasurementPollingDriver
TemperatureMeasurement measurement = ...;
MeasurementRepresentation measurementRep = new MeasurementRepresentation();
measurementRep.setSource(mo);
measurementRep.set(measurement);
measurementRep.setTime(new Date());
measurements.create(measurementRep);

cmakeable version of protocol buffers

StackOverflow community!
I want to embed protocol buffers into some project that supports cmake.
As I undrestood, google doesn't provide this
Any suggestions? Who tried to create cmakeable protocol buffers library?
Are there lots of not cross-platform places at the source or there is no at all.
Where can I take it if it exists?
What else cmakeable is there instead of protocol buffers?
Pls, don't ask me why I don't install protocol buffers, and just use compiled libraries,
I need to embed it inside the project.
If it is really bad idea, then, please, explain why.
I created a set of CMakeLists.txt for protobufs for embedding into our build systems, and offered to contribute these to protobufs, but the people at Google weren't interested.
If you'd like, I can provide them "as-is". They work for 2.2.0, but you will probably have to do some hacking on your own to tweak them for your specific build system.