Cloud Console

Cloud Console: a live web console

Cloud Console lets you view and operate a running Serial Port Utility from the browser: watch the port list and live TX/RX traffic, send data to a specific port, and open, close or reconfigure ports remotely.

Enable and use

Enable it on the desktop (all three switches are off by default):

1. Sign in inside the application (Cloud menu → Sign In); the device is bound to your account.
2. Check Cloud → Cloud Console. The device keeps a heartbeat with the cloud and shows as online in the web device list.
3. Check Allow Remote Send only if you want to send data from the web; without it the console is view-only.
4. Check Allow Remote Port Control only if you want to open/close ports or change parameters from the web; it is independent of Allow Remote Send.

Use it on the web:

1. Sign in at alithon.com, open "Cloud Sync" in the top navigation and pick "Cloud Console" in the sidebar.
2. The device list shows each bound device and its online state; click "Open Console" to enter the device page.
3. The "Ports" panel on the right lists the device's ports under the same names as the desktop, for example COM3 or TCP Client 192.168.1.10:5000. Select one to watch its live RX log on the left.
4. Open and close the port from the buttons under that list; expand "Serial Parameters" in the same panel to change the baud rate and framing.
5. In the send area on the left choose Text or HEX (for example AA55010203) plus a line-ending suffix, then send to the selected port.
6. The "Commands" panel on the right shows each remote command's state and failure reason.

Good to know

• A live window, not a recorder: nothing is uploaded while nobody is watching, the page only shows traffic from the moment you open it, and the cloud keeps no history. Use desktop log files for complete records.
• Waking up can take up to about 30 seconds after you open the page: the device learns about the viewer on its next heartbeat, then starts uploading the port list and events.
• The live buffer is small: under heavy traffic the oldest lines are dropped and the log shows a "some log lines were dropped" notice.
• A succeeded command only means the desktop wrote every byte to the port. It does not mean the target device received, understood or answered — judge that from the RX log that follows.
• Common failure reasons: permission_denied (the matching desktop switch is off), port_closed (the target port is not open), commands are rejected while the device is offline, and unanswered commands are marked timeout.
• No error pop-ups: account and cloud-sync network or server errors surface as a brief note on the desktop status bar (hover it for details) instead of a dialog, so they never interrupt local debugging.

Traffic and quota

• Console event uploads (up) and remote commands (down) are metered as cloud traffic. Each direction has a monthly free allowance; overflow draws from your top-up balance, which is shared across both directions and does not expire.
• Usage, ledger and top-ups live on the web "Cloud Traffic" page. With quota enforcement enabled, a direction is refused once the allowance and balance are exhausted, and the desktop switches Cloud Console off with a top-up prompt.

Security and privacy

• Every remote capability is off by default and must be granted on the desktop machine itself; the web console cannot bypass the desktop switches.
• Signing out stops all cloud features. These data flows are fully disclosed in the Privacy Policy — review it before enabling.