I want to know that whether there is any restriction on the use of dji-sdk?
Does the api provided in the SDK have a limit on the number of accesses,
is there a limit on the access time and is there a limit on access traffic?
Are the features provided by SDK completely free?
Can a mobile phone connect to multiple DJI devices?
If you pay the subscription fee, then there are no restrictions. If you don't pay the subscription fee then you are limited to a few devices registering for SDK access.
Yes, a single mobile device can connect to any supported DJI device and should work. Connections to devices are not limited if you don't pay the subscription but you are still limited to the number if devices you can register until the subscription is paid.
Related
I'm programming kiosk application to accept contactless payments via device with NFC reader.
So far I achieved success with a number of Visa and Mastercard cards, and with Apple Pay.
But with Google Pay it fails on sending SELECT PPSE(2PAY.SYS.DDF01) APDU (device API function ExcangeAPDU() returns undocumented error number).
Does Google Pay support this command, or I should use something else to communicate with it? Or may be it requires some tricky initialization?
I'm using clickatell sandbox account, when i try to send sms to iphone using send sms api receiving only blank message.
PS: In Andriod it's working fine
Since no adjustments are required between iOS and Android, and the Android device received your message, the problem is likely with the handset.
Suggestions:
Ensure that network coverage is strong
Ensure that the mobile number(s) is not in roaming mode
Ensure that phone memory capacity is not full
Restart the iPhone to refresh the device on the network (keep the device off for +-10mins)
Check if any phone applications or settings may filter out messages, or consider swapping the sim to another phone to test
After checking all of these, you can try again
Should you still have an issue, I recommend contacting Clickatell support on support#clickatell.com. They would be able to run live coverage tests for you.
There's a way from Codename One to provide access to Near Field Communication (NFC) ?
Anything new, out this post codename-one-nfc-beacon?
NFC is an Android only API and even there the availability in devices is "problematic". In iOS it's restricted to payment so there is no access to the underlying hardware. So there is no point in supporting the API in a framework that is designed for cross platform. I'm sure you can create a cn1lib similar to the fingerprint reader API or the SMS intercept API.
Totally new in Bluetooth Developer Studio. How can I connect to actual physical ibeacon?
Using the HID over GATT profile in a new project, gives Workbench for interacting with a Virual Server. Can I connect directly to an actual ibeacon in range for read/write?
Understand that iBeacon is a transmit only standard, so there is no standard way of establishing a Bluetooth connection. Beacons simply send out a Bluetooth LE advertisement at a periodic rate.
Some beacon manufacturers do have proprietary configuration GATT services which are connectable. But the details of how you do so (if it is even possible) are specific to the manufacturer.
There are many companies which provides sim card hosting services for receiving sms, I wanna how is this possible (at the core level)? do they use any kinda protocol or any custom devices for forwarding text messages to there servers.
This depends on the type of SIM card hosting being offered, if it is Virtual SIM card hosting (VSIM) such as this https://www.world-text.com/services/virtual-sim-hosting/ then this is only achievable were the provider has a direct connection to a mobile network over SS7. This requires very specialist knowledge, software and hardware, but is a very reliable and fast option.
If however they are offering GSM modem based SIM card hosting such as this http://world-text.com/services/sim-hosting/ then this utilises GSM modems which are normally hosted in a data centre and communicated with over IP, with messages returned to the providers SMSC. This method is slower, and is of course reliant on a local cell tower signal to work.