Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -35,16 +35,20 @@
35	35
36	36	=== COM Port ===
37	37
38		-Connection to the servo is done automatically via any properly installed USB to serial interface like the [[LSS Adapter board>>doc:servo-erector-set-system.ses-electronics.ses-modules.lss-adapter-board.WebHome]]. Once the servo is powered and properly connected to the computer, the COM port should appear in the COM port list. Ensure the board is recognized by the computer and if not, install the proper drivers. If you have multiple communication ports active, go to Windows -> Device Manager to determine which is appropriate for the USB to serial adapter you are using. Click CONNECT to connect to the servo. The software automatically scans all standard baud rates using ID254 (broadcast ID) and waits for a reply from the servo connected. Should an incorrect COM port be selected, the software will keep trying to connect. If you wish to change the COM port selected you must disconnect, select the correct COM port and reconnect. If you are not sure which COM port to select, in Windows, go to Device Manager -> Ports (COM & LPT) and select the port associated with the USB to serial device.
	38	+Connection to the servo is done automatically via any properly installed USB to serial interface like the [[LSS Adapter board>>doc:servo-erector-set-system.ses-electronics.ses-modules.lss-adapter-board.WebHome]]. Once the servo is powered and properly connected to the computer, the COM port should appear in the COM port list. Ensure the board is recognized by the computer and if not, install the proper drivers. If you have multiple communication ports active, go to Windows -> Device Manager to determine which is appropriate for the USB to serial adapter you are using. Click CONNECT to connect to the servo. If you wish to change the COM port selected you must disconnect, select the correct COM port and reconnect.
39	39
	40	+If you are not sure which COM port to select, in Windows, go to Device Manager -> Ports (COM & LPT) and select the port associated with the USB to serial device. If it is still not clear which is the proper COM port, simply disconnect and reconnec the USB cable with Device Manager open. The proper COM port will disapear (when disconnecting the USB cable) and reappear (when connecting the USB cable).
	41	+
40	40	=== Scan ===
41	41
42		-[[image:lss-config-scan.jpg||height="500" width="194"]]
	44	+{{lightbox image="lynxmotion-smart-servo.lss-configuration-software.WebHome@lss-config-20.7.14.2-scan-options.png" title="LSS Config - 20.7.14.2 - Scan options" width="124"/}}
43	43
44		-The next step once the COM port has been selected is to scan the port. The software can send commands to (and listen for a reply from) all servo IDs (0 to 250) at all standard baud rates on the selected COM port. In the pop-up, select the baud rates which you would like to scan, and the option of limited the IDs is also available. When in doubt, leave all baud rates selected. Once the scan starts, the command line interface will include messages for all servos found (or not found) at each baud rate, as well as any conflicts discovered.
	46	+The next step once the COM port has been selected is to scan the port. The software can send commands to (and listen for a reply from) all servo IDs (0 to 250) at all standard baud rates on the selected COM port. In the pop-up, select the baud rates which you would like to scan. You may also limit the IDs to scan for. When in doubt, leave all baud rates selected
45	45
46		-This process may take a few seconds and once completed, a list of all available servos with which the software was able to communicate will appear in the list next to "Servo" (in the top orange Connection field of the interface) as a drop-down. All servos correctly identified on the BUS will have their LED turn green (session specific as opposed to configured) to indicate no conflict. If two or more servos have the same ID (regardless of whether or not they have different baud rates), those servo's LEDs will turn red for that session, indicating an issue or overlap in IDs. To resolve this, you will need to change the ID of those servos to be distinct.
	48	+Once you press OK, the scan will start by turning off the LED of all servos on the selected baud rates (#254LED0\r). Then, each selected baud rate is scanned for servos. The command line interface will include messages for all servos found (or not found) at each baud rate, as well as any conflicts discovered (two or more LSS at the same location). In this case, a location is defined as a baud rate and ID pair.
47	47
	50	+This process will take a few seconds and once completed, a list of all available servos with which the software was able to communicate will appear in the list next to "Servo" (in the top orange Connection field of the interface) as a drop-down. All servos correctly identified on the bus will have their LED turn green (session specific as opposed to configured) to indicate no conflict. If two or more servos have the same ID, those servo's LED will turn red for that session, indicating an issue or overlap in IDs. To resolve this, you will need to change the ID of those servos to be distinct (they will need to be connected individually/separately from the other conflicting servos).
	51	+
48	48	**GREEN LED**: No Conflict
49	49
50	50	**RED LED**: Conflict Found
...	...	@@ -53,20 +53,22 @@
53	53
54	54	=== Servo ===
55	55
56		-The scan provides a list of all servos which have been detected on the bus and lists the following choices in the drop-down. Note that the last servo in the list is automatically / arbitrarily selected for convenience.
	60	+The scan provides a list of all servos which have been detected on the bus and lists the following choices in the drop-down. Note that the last servo in the list is automatically selected for convenience.
57	57
58		-LSS-None (???; ~-~--k)
	62	+**LSS-None (???; ~-~--k)**
59	59
60	60	This first option is used only when a servo ("???" to signify "unknown servo") cannot be reached via the LSS Config software and needs to be manually set to bootloader mode via the button menu in order to re-flash the firmware. The telemetry graph and configurations are all greyed out when this is selected. Once the servo has been set manually to bootloader mode, select this option and go through the firmware update procedure. This normally only needs to be done as a "last resort".
61	61
62		-LSS-All (254; ~-~--k)
	66	+Note: You can use this special firmware recovery function with 2 or more servos simultaneously. Just make sure they are all in bootloader mode before stating the firmware update using this option.
63	63
64		-This uses the "broadcast" ID (#254) which all servos are configured to respond to (along with their own ID). Since there is no particular servo being monitored, the telemetry graph and configurations are all greyed out. This is used to send the same firmware update to all servos on the bus, or to send the same action command to all servos on the bus via the Command line interface described below.
	68	+**LSS-All (254; ~-~--k)**
65	65
66		-The drop-down list will be populated with all servos which the software has found on the bus, indicating their ID, servo model and firmware version. Each servo will then be listed in the following format:
	70	+This option allows actions that affect all detected servos in the list after a successful scan. Since there is no particular servo being monitored, the telemetry graph and configurations are all greyed out. This is used to send the same firmware update to all detected servos on the bus or to send the same action command via the terminal interface described below.
67	67
68		-ST1 (0;115.2k [368])
	72	+The drop-down list will be populated with all servos which the software has found on the bus, indicating their servo model, ID and firmware version. Each servo will then be listed in the following format:
69	69
	74	+**ST1 (0;115.2k [368])**
	75	+
70	70	The servo model is displayed first (ST1, HS1, HT1), followed by its ID, the baud rate to which it has been st (ex. 115200, or 115.2k) and its firmware version in rectangular brackets. Selecting a servo from the list will allow the software to communicate with it.
71	71
72	72	== Firmware Update ==