Atlato Developer
DocsUse CasesCommunitySupport
DocsUse CasesCommunitySupport
Facebook
Linkedin
Instagram
  1. Device API
  • Overview
    • Developer Platform
  • Getting Started
    • Register Account
    • Manage Apps
    • Manage a Company
    • App Access
    • Store App Access
    • Mode
  • App Store
    • Authentication
    • Access Rights
    • Event Log
    • Company Settings
    • Manage Account
  • Device Integration
    • Design
    • Installation
    • Device List
  • Device API
    • Protocols
    • New Integration
    • Data Output
    • Device Input Names
  • Deployment
    • Custom Client App
  • API Request
    • REST API
    • Request Structure
    • Metadata
    • Pagination
    • Errors
    • Troubleshooting
  • Support
    • Developer Request Types
  • Guides
    • Best practices
    • Timezones
    • Libraries
    • Key Concepts
    • Terms of Use
    • Rate limits
  • Feedback Center
    • Feedback
    • Community
    • FAQ
  • Api Integration
    • Use token in your app
    • Event Logging API
    • Meta Data API
    • Lastest Device Data API
    • Past Device Data API
    • Devices API
    • Country City Currency API
  • App Integration APIs
    • Meta Data
    • Meta Data API
    • Lastest Device Data API
    • Past Device Data API
    • Event Logging API
    • Devices API
    • Country City Currency API
  • Developer Platform
    • Access
    • User
    • Device
    • Manage Account
    • Company
  1. Device API

New Integration

This section explains how to integrate a new device model with Atlato, how to add new inputId for device packet objects, and how to add new calibration types for device packets. Each task involves creating a Jira ticket for tracking and collaboration.

Integrating a New Device Model#

To integrate a new device model with Atlato, follow these steps:
1.
Upload Device Model Protocol
Prepare a detailed protocol document that explains how to decode the device data from the raw packet.
Include the communication method used by the device (e.g., socket.io, TCP).
Submit the protocol document via the designated upload section on our platform or attach it to a Jira ticket.
2.
Define Device Data Structure
Outline the structure of the data packets, specifying each field and its data type.
Include any error messages that might be generated by the device.

Adding a New Input Id for Device Packets#

To add a new Input Id for a device packet object:
1.
Specify the Data Type
Clearly define the data type for the new Input Id (e.g., integer, float, string).
Include an example of the data format.
2.
Define Error Messages
If applicable, list any error messages that might be associated with the new Input Id.
3.
Submit Changes via Jira
Create a Jira ticket detailing the new Input Id, its data type, and any associated error messages.
Attach any relevant documentation or examples to the ticket.

Adding a New Calibration Type#

To add a new calibration type for raw data packets:
1.
Define the Calibration Function
Provide a detailed description of the calibration function.
Include the mathematical formula or algorithm used for calibration.
Specify any parameters required for the function.
2.
Error Handling
Clearly define any error messages that might be generated during calibration.
Provide examples of possible errors and how to handle them.
3.
Submit Calibration Details via Jira
Create a Jira ticket with the details of the new calibration type, including the function, parameters, and error handling information.
Attach any relevant documentation or code snippets to the ticket.

Establishing a Jira Ticket#

1.
Log in to Jira
Use your company credentials to access Jira.
2.
Create a New Ticket
Click on the "Create" button to start a new ticket.
Select the appropriate project for your task.
3.
Fill in Ticket Details
Provide a summary and detailed description of the task.
Attach any necessary files or documentation.
Assign the ticket to the relevant team or individual.
4.
Submit the Ticket
Review the information and submit the ticket for processing.
Modified at 2024-07-18 08:32:35
Previous
Protocols
Next
Data Output
Built with