StandCloud¶
About StandCloud¶
StandCloud is a cloud management tool for electronics manufacturing. Test data is crucial for evaluating performance. StandCloud allows you to explore data patterns, create visualizations, and gain insights. This helps in identifying potential trends and opportunities. It allows you to identify potential limitations.
For more information, visit the StandCloud website.
StandCloud and HardPy integration¶
HardPy allows test result data to be stored in the StandCloud and read them from the StandCloud. For an example of StandCloud and HardPy integration, see StandCloud example and StandCloud readed example.
To authorize in StandCloud you need to know the address of your StandCloud service. To obtain one, contact info@everypin.io.
Address must be added to hardpy.toml in stand_cloud
section:
[stand_cloud]
address = "demo.standcloud.io"
You need to run the command:
hardpy sc-login <stand_cloud_address>
Accept
button.
To check the StandCloud connection status, run the command:
hardpy sc-login --check <stand_cloud_address>
The StandCloud authentication time is updated each time you interact with StandCloud.
If you do not use StandCloud services, the authentication will be canceled and the
hardpy sc-login
function must be called again.
To clarify and edit your authentication time case, you can contact info@everypin.io.
To logout from StandCloud service run the command:
hardpy sc-logout <stand_cloud_address>
Third party applications can authorize in StandCloud. This process is described in the StandCloud third party authorization example.
HardPy rules¶
General guidelines¶
Some tips for getting the best analytics in StandCloud.
- Use the set_dut_serial_number to store DUT serial number. The serial number allows you to distinguish between units with the same part number. It also allows you to analyze the number of attempts to test a device.
- Use the set_dut_part_number to store DUT part number. The part number is an identifier that allows you to clearly identify the product.
- Use the set_case_artifact, set_module_artifact, and set_run_artifact to store important information, that cannot be accommodated in other structured fields such as set_case_measurement and set_case_chart.
- Use the case_name and module_name markers for human-readable names. They make it easier to analyze the tests.