Integrate teltonika gps tracker with Thingsboard platform - gps

I am wondering if anyone tried or has a clue how to integrate teltonika gps tracker device with Thingsboard IoT platform. So, to get gps data from a tracker device, parse it and store it on platform like any other IoT device. Teltonika has its own communication protocol so I don't know if the integration is possible and how

You need to use a broker in between your GPS device and ThingsBoard, I have used Gurtam Flespi platform before and it worked.

Related

Connect a Teltonika device to Thingsboard

Currently we are evaluating Thingsboard CE. We have a requirement to connect a Teltonika device (GPS enabled devices) to connect to Thingsboard IoT platform and push the data to it.
Any ideas would be of great help.
We have installed Thingsboard CE on a server. We have created or added few devices and assigned them to few sample customers.
Basically we receive data from 'GPS' devices connected to waste collection vehicles like dumper/ tipper, with the help of a Java service which runs as a 'jar' file in the background.
Now we are stuck at a phase on how to use 'HTTP API' to push this data to Thingsboard platform.
Please Suggest us on how to proceed.
Thank you.

Is there any way to use Kinect SDK remotely with network?

The Azure Kinect sensor SDK requires Kinect to connect directly to pc via usb, but it's not appropriate to me. Is it posible to use something like raspberry pi to transfer kinect sensor data and process on a remote server? Do you have any suggestions for this?
I found the Kinect sdk does not support ARM architecture(raspberry pi),what other device can I use?
Processing the depth camera image requires GPU compute, so we don't currently support headless operation. There are some users that have successfully enabled headless operation on Linux, but it is not a straight forward path. See https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/810 for more info.

What is the plug is on the Plugable MXChip AZ3166 IoT DevKit?

I'm looking at prototyping a couple of solutions using the MXChip AZ3166 that require a number of external devices like GPS, Display and Comms hardware.
Does anyone know what connectors can be used with the "Pluggable" MXChip AZ3166 IOT Devkit, or if there are any breakout boards available for it?
In Mxchip AZ3166, there is a edge connector on the board that is compatible with BBC Micro:bit accessories. So you could easily extend it with external devices.
More information of Micro:Bit could be find here: https://www.kitronik.co.uk/microbit/bbc-micro-bit-accessories.html
And you could check this example https://github.com/jimbobbennett/InternetConnectedFan on how to use Micro:Bit to connect to external devices.

How to add a device to MobileFirst Operations Console?

How to add a device to MobileFirst Operations Console ?
I face issue in identifying my device in the MobileFirst Operations Console.
Please let me know how to configure my device to be detected in the console .
The only feature related to "devices" is adding device simulation in the Console's Mobile Browser Simulator as described in the following user documentation topic: http://www-01.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.dev.doc/wl_studio_tools/topics/ttestwl.html?lang=en
The other feature related to devices is Device profiling, as described in the tutorial Getting Started tutorial: https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-7-1/foundation/hello-world/introduction-to-mobilefirst-platform-operations-console/
Device profiling will be made possible after applications that are installed on simulators or devices are used and connect the MobileFirst Server. You can then create device profiling based on... devices.

How do I access a GPS from Windows IoT on Rasperry Pi?

I have done this when running Debian using gpsd. But when running Windows IoT preview...what is a way to get the NMEA sentences off an attached GPS (on the USB port). Is that kind of support around yet?
Currently this support is not yet available but it is being actively developed. Furthermore the Geolocator API is broken. Unfortunately I don't have an ETA for this but its coming.
Mark Radbourne (MSFT)