I am working on SUMO-0.25.0, OMNeT++ 5.0, Veins-4.4 framework for vehicular simulation. I am interested on cross layer routing protocol for vehicular communication. Can anyone able to suggest me how I can retrieve PHY /MAC layer information such as SNIR and RSSI value from the application layer. For example, Veins demo application or my own AppLayer model?
A vector record of the SINR values calculated during frame reception using omnet++ signal mechanism as mention on the post. But i am unable to get SINR or RSSI value into the veins demo application such as TraCIDemo or my own AppLayer model.
It will be great if anyone could give me some idea how i can do it. Thanks in advance.
The easiest way I can think of is to change the Veins code to include the values you need in the messages that are passed from the PHY/MAC layers up to the application.
Related
I am working on making a custom controller for an aquarium light. I was able to figure out how to adjust the light's internal clock, and I was able to capture some of the communication, and I found this timecode 545f0d31574d52565951607631 which translated to ascii from hex becomes T_ 1WMRVYQ`v1. I know for sure it's the timecode, because it works as expected.
Anyone know what it is? Is it BLE specific? anyone know how to alter it?
I'm pretty sure the first 4 numbers are not part of the code, but a indicator for the device.
Edit:
It is BLE. I should have been more clear. It does most of the transmission on UUID 1000, with the characteristic uuid being 1001. The device doesn't have a built-in clock that I can see. It turn's on and off at the times I specify in the developer’s app. After a power failure, it "resets" to midnight. I know that value is the timecode, because when I input it using gatter tools, I can see the light reacts accordingly. I added a photo of it updating. –
You hint that that this is a Bluetooth Low Energy (BLE) device.
If it is BLE, then the UUID of the characteristic might be in the 16-bit UUID Numbers document. If it is a custom characteristic, then it will not. Official characteristics have the base address of 0000xxxx-0000-1000-8000-00805F9B34FB and only the four missing values are documented.
The specification for how time can be shared over BLE is documented in the GATT Specification Supplement if it is a Bluetooth SIG adopted characteristic.
It might be helpful if you update the question with what this values gives as the value on the light's internal clock.
Hi I am developing an application where an ATSAMB11 device has to send pressure data (from 0 to 6 bar with 5mbar steps) through BLE. I was just wondering if I should implement a custom service and characteristics or I can use the blood pressure service that is already implemented for atsamb11. I am asking because if I use the blood pressure service, it would be much easier as it is furnished with examples and I could write my program over it. Whereas if I have to create my custom service, I don't know where to start and what I need to write. (I precise that it's the first time that I'm working on BLE)
Another option would be to send the data through the custom serial chat service(which is also implemented and have an exemple), but I think that doing so is not the right way to use BLE. Indeed, why would everyone bother about different services and profiles if they could send anything through custom serial chat.
If you can use the standard blood pressure service, do that. Custom services are only used if there is no matching standard profile or the standard profile lacks some functionality one wants.
I want to develop a software and in the next month hardware for receive Microsoft Band data, specifically from GPS, but I need the datasheet or fabricant of Band's GPS
You might be able to find some of that information in a teardown or fix guide.
eg This one or this one
You'll have to be more specific about the information you want when you say "datasheet or fabricant of Band's GPS" but, in any case, the current Band SDK (v1.3.10702) does not expose a means of streaming GPS sensor data from the Band.
I want to simulate vehicle tracking in wireless sensor network using OMNeT++.
I have created WSN. But i don't know how to add vehicle object and move that object in that network. I need some ideas or source code.
Although this can be achieved using Veins, you might find some functionality missing that is relevant to sensor networks (e.g., battery consumption).
Recent versions of the INET Framework contain parts of Veins that allow you to move nodes according to vehicles' movement. See the documentation of the TraCIMobility class for more information.
You can use SUMO for vehicle mobility simulation, and connect it with OMNeT through Veins framework.
I have to configure my video camera display resolution before capturing and processing the data. Initially I did it as follows.
Created all necessary interfaces.
Added camera and renderer filters
Did RenderStream with Capture and Preview PIN Categories.
Then did the looping through AM_MEDIA_TYPE structures and setting the params.
This worked for a lot of cameras, but a few cameras failed. Then I changed the order of 3 and 4 given above. That is, I did the setting of params before the RenderStream. This time, the error cases went through, but a few On board cameras in SONY VAIO laptop etc seem to fail.
Now, my questions are
Which is the optimal and correct method of getting and setting AM_MEDIA_TYPE parameters and running the graph?
If there are different cameras, if I get an indication of which order is the best for a particular camera by going through the camera's DirectShow interfaces, that will also serve my purpose.
Please help me in this at the earliest,
Thanks and regards,
Shiju
IAMStreamConfig::SetFormat needs to be used to set capture format before the pin is connected and rendered. This way the downstream subchain of filters is built with proper media types.