User Tools
software:gui-designer:system-manager:system-properties
Differences
This shows you the differences between two versions of the page.
|
software:gui-designer:system-manager:system-properties [2013/04/22 00:38] jarrod [Heartbeat Properties] |
software:gui-designer:system-manager:system-properties [2015/01/29 05:57] (current) jarrod [Ports] |
||
|---|---|---|---|
| Line 21: | Line 21: | ||
| ==== Ports ==== | ==== Ports ==== | ||
| - | There are two port settings available for each system, the destination port (labeled simply 'port') and the origin port.\\ | + | There are two port settings available for each system, the destination port (labeled simply 'port') and the origin port (source port).\\ |
| The destination port is the port number the external system is accepting connections on, whilst the origin port is the port number that iViewer is sending messages from. Some systems require commands to be sent to a specific port, but replies are sent on a different port (common amongst UDP systems mainly).\\ | The destination port is the port number the external system is accepting connections on, whilst the origin port is the port number that iViewer is sending messages from. Some systems require commands to be sent to a specific port, but replies are sent on a different port (common amongst UDP systems mainly).\\ | ||
| You only have to enter the 'Port' setting most of the time (the origin port will use the destination port setting if it is not explicitly set).\\ | You only have to enter the 'Port' setting most of the time (the origin port will use the destination port setting if it is not explicitly set).\\ | ||
| - | The port numbers must be in the range 1 to 65535. See http://www.iana.org/assignments/port-numbers for more details on port number usage in general. | + | The port numbers must be in the range 1 to 65535. See http://www.iana.org/assignments/port-numbers for more details on port number usage in general.\\ |
| + | **Note that you cannot use UDP ports below 1024 on Android platform. This is a limitation of Android.** | ||
| + | === For UDP systems === | ||
| + | If the origin port is set to ''0'', it will use the same port number as the destination port.\\ | ||
| + | If the origin port is set to ''-1'', iViewer will randomly assign an available source port - but //ONLY// if the system is //not// set to accept incoming data (it will use the destination port in this case). | ||
| ==== Accept Broadcast Messages ==== | ==== Accept Broadcast Messages ==== | ||
| When in UDP mode, this allows the system to receive UDP broadcast packets. | When in UDP mode, this allows the system to receive UDP broadcast packets. | ||
| Line 53: | Line 57: | ||
| ==== EOM (End Of Message) ==== | ==== EOM (End Of Message) ==== | ||
| - | Feedback parsing works best when an EOM string is defined for the system. Most systems end each message with a unique character (or string of characters). A common example is a carriage return (x0D).\\ | + | Feedback parsing works best when an EOM string is defined for the system. Most systems end each message with a unique character (or string of characters). A common example is a carriage return (\x0D).\\ |
| By entering the EOM string used by the system, it allows the feedback from the system to correctly split up each message and parse each message through the feedback system (comparing against feedback Regular Expressions, etc).\\ | By entering the EOM string used by the system, it allows the feedback from the system to correctly split up each message and parse each message through the feedback system (comparing against feedback Regular Expressions, etc).\\ | ||
| If no EOM string is used by the system, messages will be declared a single message when they arrive on the ethernet stack. If the system sends lots of messages quickly, this could result in multiple messages being concatenated or split in strange places, causing the feedback parsing system to not work as expected in some cases. So if possible, always enter the EOM string for your specific system.\\ | If no EOM string is used by the system, messages will be declared a single message when they arrive on the ethernet stack. If the system sends lots of messages quickly, this could result in multiple messages being concatenated or split in strange places, causing the feedback parsing system to not work as expected in some cases. So if possible, always enter the EOM string for your specific system.\\ | ||
| Line 59: | Line 63: | ||
| **Note: The EOM string is NOT appended to outgoing commands for the system. It is only used for splitting up messages when feedback arrives.** | **Note: The EOM string is NOT appended to outgoing commands for the system. It is only used for splitting up messages when feedback arrives.** | ||
| - | Hex data must be entered in xFF format, see [[software:gui-designer:hex-data|Entering Hex Data]] for more details. | + | Hex data must be entered in \xFF format, see [[software:gui-designer:hex-data|Entering Hex Data]] for more details. |
| ==== Connection Join ==== | ==== Connection Join ==== | ||
| For systems using TCP/IP, the 'connection join' will be held high as long as the system is currently connected.\\ | For systems using TCP/IP, the 'connection join' will be held high as long as the system is currently connected.\\ | ||
software/gui-designer/system-manager/system-properties.1366591085.txt.gz · Last modified: 2013/04/22 00:38 by jarrod
