I wanted to know what mobile devices(Mobile phone and others) are available in the market which supports OMA Lightweight M2M protocol. As its a new protocol released this year but there is no information on the internet about available devices those support this protocol. As i wanted to make Proof of concept therefore i need to have device to do so.
OMA LWM2M is indeed so new that it is not yet an official OMA enabler.
You can find an open source implementation here: liblwm2m. It is not feature complete (bootstrap interface is missing) but you can make proof of concept out of it.
The complete Lightweight M2M spec is now available for free from OMA at http://openmobilealliance.hs-sites.com/lightweight-m2m-specification-from-oma
Currently, OMA try to provide many helps to the developers. You can refer to https://github.com/OpenMobileAlliance
And there are some open sources as refer to
http://www.omaevents.org/?page_id=1626 which is recent event.
Related
We develop applications using ble beacons. One of the beacons providers offering beacons with MiniBeacon firmware. I guess MiniBeacon firmware makes it possible to configure the beacon in iBeacon and Eddystone format simultaneously. Is it correct ?
I searched but could not find much information about MiniBeacon firmware. Does it have any known compatibility issues with Eddystone or iBeacon format or any known performance issues ?
Sorry for asking such a generic question. Thanks a lot.
Reg,
It does not look to me like the firmware supports Eddystone, at least not at the link referenced in the comment below the question. That firmware is 3 or 4 years old by the changelog, dating to before the release of Eddystone.
The README mentions iBeacon compatibility, and if that format is indeed supported, it would be compatible with the Android Beacon Library if the library is configured with the proper BeaconParser for iBeacon.
You may wish to check with the firmware author to see if a newer version is available supporting Eddystone.
I want to know if I can setup altbeacon uuid, major and minor with altbeacon library for any beacon hardware that support altbeacon layout. I haven't seen this information in any place. Because of operational reasons, I need to set them up remotely, with open source software. All of them are proprietary. I am looking for an open source solution for set them up. Any help or information would be apreciate it.This question is related to altbeacon, because I couldn't find a non property solution for ibeacons.
Altbeacon is 'old' and not used so much now. In any case, it sends out a URL, not unique id(s). You should instead look into Eddystone if you really don't want to use iBeacon. All beacons just use 'standard' Bluetooth advertising so there's nothing to stop you designing your own Bluetooth advertising payload. There's an overview of advertising at BeaconZone.
The Android Beacon Library does not provide a SDK for configuring beacon identifiers. Unfortunately this is not possible because every beacon manufacturer has a different way of configuring their beacons, and the mechanisms are often proprietary and does not have a published API.
The open source AltBeacon standard is supported by a wide variety of beacon hardware manufacturers. However, there is simply no standard way of configuring the identifiers. You must follow manufacturer instructions.
I know the midiXxx API, but I saw it is currently listed under 'legacy' in msdn.
http://msdn.microsoft.com/en-us/library/windows/desktop/dd743619(v=vs.85).aspx
Is there some other API i should use to target the newer Windows versions?
Will the old API still work on Windows 7 and 8?
Thanx,
Marc
Last Friday Microsoft released a preview Windows Runtime API for MIDI. Check out the //build/ session here:
http://channel9.msdn.com/Events/Build/2014/3-548
MSDN: http://msdn.microsoft.com/en-us/library/windows/apps/dn643522.aspx
Although a preview, apps can go live and be deployed to the Windows Store. Please let us know what you like or don't like. Happy app building!
For dektop applications (non metro) you can still use the legacy API safely.
Sadly for WinRT/Metro, there is no midi support at all (see this discussion on msdn).
Hope they will change that.
Catflier is correct that there is no direct support (at the API level) for MIDI in WinRT. However, if you are wanting to have MIDI-like capabilities in your app, there are workarounds. A protocol growing in popularity is the network-based OSC (Open Sound Control). Since it is network-based, you can use that.
For example, one can use external hardware like The Missing Link which translates from MIDI to OSC. You hook up your MIDI device to The Missing Link, which then translates to OSC messages that are sent to the computer. Your app can then receive OSC messages and talk to the MIDI device. I don't have any code to show here, but I've seen demos of this working in-action.
You can see OSC in use on iOS as well with popular apps like TouchOSC.
I need to scan Wifi access point on Windows Mobile and connect the one of scanned results.
Currently I am using C# language, Windows Mobile 6.5 device, also to scan I am using the below code.
[DllImport(wlanapi.dll", SetLastError=true)]
I am using wlanapi.dll, but it seems that not possible to use on Mobile.
Does anyone know about the belows.
Could I use the dll in Windows Mobile 6.5 to scan and connect?
If the 1 is not possible, please let me know the different methods..
Please give me the clues.
wlanapi.dll doesn't exist in WinMo/WinCE. You have to use an API that is supported.
Most WinMo WiFi drivers (though probably not all) support the Wireless Zero Config (WZC) set of APIs. The native versions of these APIs, like WZCQueryInterface, are outlined in MSDN.
Microsoft does not provide any managed interface for these APIs, in fact the native documentation for them is pretty bad too. The definitive "example" of it's use is in the NETUI component source of Platform Builder. Gettign the eval version just for the source is very worthwhile if you plan to do much WinCE/WinMo development.
From a managed perspective I wrote an MSDN article back in '06 that talks about using the SDF for getting network info. The SDF has been reworked a lot since then, especially in the WZC area, but it's still pretty similar.
I did an updated blog post in '07 about custom-drawn ListBoxes, and while that's not what you're after, the data being displayed is wireless network info, which is in line with what you're after.
Window's COM allow us to wrap our application function for out-of-process invocation. If the COM interfaces are well defined and design, it is certainly great to consume the services via scripts and any programming platform that support COM/Automation/Active-X.
I am just wondering if there exist any alternate methods to design of what COM does? Or something close or similar methodology?
I am using Delphi in Win32 platform.
I'm not entirely sure, but it seems that you're talking about an alternate to COM for creating plug-ins for your software?
If so, there are myriad options:
TMS Software's Plugin Framework
RemObject's Hydra
Project JEDI's JVCL includes a plugin system
You can also roll your own. I wrote an article many years ago that provides the fundamentals (though the linked source is long since gone to the great bit bucket in the sky).
Corba
or
IBM's SOM
I'm sure there are others as well but those are the 2 others i can think of off the top of my head ...
If you want a TCP/IP (over the internet or over a LAN) interface for your objects, consider SOAP, and REST.
If you want to write plugins for your delphi app and not use COM/OLE-Automation, consider RemObjects SDK.