About error code

Q. What is error code 6095?

A. Error code 6095 is typically triggered when the personal data fields, such as date of birth, contain invalid values.

Please note that the handling of personal data varies depending on the device category.
For detailed specifications, refer to the SDK documentation: “Appendix-DataStructuresOverview iOS.pdf”, section 3. Device Settings Structures.
Sample implementations can be found in " 6. Example Code for Configuration Settings."
We recommend verifying that all personal data values are correctly configured according to the expected format and constraints defined for each device category.

Q. What is error code 9000?

A. The error code 9000 indicates parameter error.

For example, if you set the unsupported device’s information, it causes the parameter error.
Please confirm the parameter.

Q. What is error code 6022/6002?

A. The error code 6022/6002 indicates "Paring failure (in device communication mode)," which happens when the device in in coummunication mode.

This may occur when:

Even through the app sends a device registration request, the user has set the device to communication mode.

To resolve this:

Set the device correctly to paring mode (not communication mode).

About implementation

Q. The method startScanPeripheralsWithCompletionBlock is unable to find any device (M7 Intelli IT AFib), if the device filter was set in setConfiguration method. If the filter is not set, it works.

A. The first matching model is registered in the filter, which prevents other models from being detected.

[ modelName || modelDisplayName] is used as search key for the device list.
This may duplicate to the sales name to the other model.
M7 Intelli IT (our device sales name) matches this case.

Product (Device) Type	Sales (Name) Type
HEM-7322T-E	M7 Intelli IT
HEM-7361T-EBK	M7 Intelli IT

It is possibly, due to the program code, the first model that matches is registered in the filter, which prevents the other from being detected.
Therefore, we have suggestion/workaround which is considered their internal specification limitation.
But we are not sure it is acceptable since there is side effect.

Suggestion (Workaround):
Register both HEM-7322T-E, HEM-7361T-EBK for filter.
Search device list at the very end and register all the same name device as filter.
This may cause the connection for both HEM-7322T-E, HEM-7361T-EBK

Side effect
HEM-7322T-E, HEM-7361T-EBK will both become searchable.
If this works and it can be detected, we can assume the cause.

About supported devices

Q. Can we integrate a OMRON Complete?

A. Our SDK, Connectivity SDK, supports BPM data transfer from OMRON Complete but does NOT support ECG data transfer.

Summary of ECG device support status:

The COMPLETE device itself supports ECG and BPM.
The SDK 3.4.0 supports the COMPLETE device.
The SDK only supports BPM data transfer.
The SDK does not support ECG data transfer due to using the Kardia library which is provided by AliveCor.
The SDK does not support the Kardia Mobile 6L device(only sold in Brazil and Japan).

About SDK

Q. Is it possible to provide us with the open-source code required for the integration of Omron devices with other applications?

A. Our SDK, Connectivity SDK, only provides the library, its sample usage and documents. We have not been disclosing our source code from the first place.