en:recomendations
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:recomendations [2018/01/25 17:41] ashley |
en:recomendations [2020/03/25 16:28] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | **Recommendations for participants** | + | ====== Recommendations for Users ====== |
| - | **1 Turn on the devices one at a time.** \\ | ||
| - | For each device on the network, make a test program that verifies each device specifically. Connect it with a separate, tested loop directly to the central computer and check its operation. After you make sure that the device works as it should, go to the next device. When connecting new devices to the network, check the old tests. If one of the devices has stopped working, then you have made a problem in the wiring. Double-check recently connected devices. | ||
| + | **1 Power up devices in succession** | ||
| + | |||
| + | Make a test program for every device in the network to check this particular device. Connect the device directly to the central computer using separate tested ribbon cable and check if the device operates properly. After making sure the device is fully operational proceed with the following device. Re-run previous tests as you add new devices to the network. If a device stops working there must be a disruption in wiring. Re-check all recently connected devices. | ||
| - | **2 Check the error codes. ** \\ | ||
| - | The query functions return an error code in case something went wrong. The code in the following form\\ | ||
| + | **2 Monitor error codes** | ||
| + | |||
| + | Request functions will return an error code shall something go wrong. It pays to handle errors with code like that: | ||
| + | |||
| + | <code c> | ||
| if (LSS_OK == transmitter_turn_on(1)) | if (LSS_OK == transmitter_turn_on(1)) | ||
| { | { | ||
| Line 16: | Line 20: | ||
| printf("Error! Failed to turn on transmitter \n"); | printf("Error! Failed to turn on transmitter \n"); | ||
| } | } | ||
| + | </code> | ||
| - | will help you to more quickly identify errors in the program than the code in the form below:\\ | + | This will let you identify bugs in your program faster than if you code this way: |
| + | <code c> | ||
| transmitter_turn_on(1) | transmitter_turn_on(1) | ||
| + | </code> | ||
| + | |||
| + | **3 Wait for devices to complete boot-up** | ||
| + | |||
| + | Once powered up with the xxx_power_on() command, devices will need some time to boot up. After they boot up, they still won’t be able to respond immediately to the first request they receive. If you want to power up a device and operate it, wait for the device to complete booting (no longer than 1 second) and prepare it for receiving data if you can. The latter can be done by either sending the bus_setup() command to the bus or sending any data to this or another device. | ||
| - | **3 Allow the devices to load.**\\ | + | <note important> |
| - | After powering on the device with the xxx_power_on () command, the devices require time for loading. In addition, after they load, they cannot respond to the first message sent to them. If you want to turn on the device and start working with it, wait for the device to load (no more than 1 sec) and prepare it for receiving messages either by sending the bus_setup () command to the bus or by sending any message to this or another device. | + | **//Additionally, make sure that your software is up-to-date. The most recent versions can be found here.//** |
| + | </note> | ||
en/recomendations.1516891290.txt.gz · Last modified: 2020/03/25 16:29 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
