Bench simulation
Validate logging, the local web UI, and CSV output before connecting hardware.
sigless --simulate --ch1 --web 8000 --verbose 1Choice examples
Start with the workflow you need
Dual-channel capture
Record both channels from a networked Siglent device into a dedicated run folder.
sigless --address 192.168.50.148 --port 5025 --ch1 --ch2 --out ./logs --verbose 2Marked experiment
Add event notes and checkpoints from scripts or operator actions while capture continues.
sigmark --ip 127.0.0.1:8000 --msg "Start batch A" --ch1
sigmark --ip 127.0.0.1:8000 --checkpoint --ch1What is Sigless?
Sigless is a laboratory-grade monitoring tool built to improve daily work with Siglent measuring devices in labs and other scientific settings. It captures repeatable readings, keeps measurements organized, and makes it easier to run reliable experiments without manual overhead.
Use it to streamline acquisition across benches, document measurement context automatically, and keep high-frequency readings consistent across long experiments or validation runs.
- Automate your workflows
- Sub-second readings
- Event-based timestamps
- Dual-channel reading mode
- CLI and web interfaces
- Audit-friendly CSV exports
- Simulated device mode
- Checkpointed log files
Quickstart
Run a simulated session first to confirm output, then connect to a real Siglent device.
sigless --simulate --ch1 --web 8000 --verbose 1
sigless --address 192.168.50.148 --port 5025 --ch1 --ch2 --out ./logs
Tip: Use
--verbose 2 for live readings and --web 0 to disable the web server.
Usage examples
Common ways teams run Sigless in labs and during automated testing.
# Simulated device with web UI
sigless --simulate --ch1 --web 8000 --verbose 1
# Dual-channel capture from a Siglent on the network
sigless --address 192.168.50.148 --port 5025 --ch1 --ch2 --out ./logs --verbose 2
# Quiet logging to a dedicated folder
sigless --address 10.0.0.42 --ch1 --out /var/log/sigless --verbose 0
# Run without the web server
sigless --address 192.168.50.148 --ch1 --web 0Installation
Download a binary from the release archive or install directly from a local build.
# macOS / Linux
curl -L https://siglessmonitor.com/build/latest/sigless -o sigless
chmod +x sigless
sudo mv sigless /usr/local/bin/
# Windows (PowerShell)
Invoke-WebRequest -Uri https://siglessmonitor.com/build/latest/sigless.exe -OutFile sigless.exe
Move-Item .\sigless.exe C:\Tools\sigless.exeConfiguration
Sigless is configured with flags at runtime. Enable channels and set device details per session.
sigless --address 192.168.50.148 --port 5025 --ch1 --ch2
sigless --out ./logs --verbose 1 --web 8000
sigless --simulate --ch1 --web 0
Tip: Set
--out to keep logs organized per session or workstation.
Core commands
Sigless is a command-line tool shipped as a single binary. These options cover every supported flag.
--address
Set the Siglent device IP address for TCP connections.
--port
Set the Siglent device TCP port (default is 5025).
--ch1 / --ch2
Enable channel logging. At least one channel is required for live capture.
--simulate
Run without hardware to test logging and the web UI.
--web
Start the web server on localhost. Use --web 0 to disable it.
--verbose
Verbosity level: 0 silent, 1 incoming messages, 2 logged readings.
--out
Output folder for CSV log files (default: current directory).
--dev
Run in development mode and read static web files from disk instead of the embedded bundle.
--help / -h
Show the help message and exit.
--version / -v
Print the build version and exit.
Sigmark events
Sigmark is a sister tool that runs alongside Sigless, posting messages or checkpoints to the Sigless web server.
# Start Sigless with the web server enabled
sigless --simulate --ch1 --web 8000
# Send a message to channel 1
sigmark --ip 127.0.0.1:8000 --msg "Start of batch A" --ch1
# Send a checkpoint to roll the log file
sigmark --ip 127.0.0.1:8000 --checkpoint --ch1
Sigmark requires exactly one channel flag (
--ch1 or --ch2). Use
--checkpoint without --msg to persist current logs.
--ip
Target Sigless web server address. Include a port when needed, for example 127.0.0.1:8000.
--msg
Message text to send to the Sigless log endpoint. Required unless --checkpoint is used.
--ch1 / --ch2
Choose exactly one target channel for the event or checkpoint.
--checkpoint
Save current state and roll a new log file. Cannot be used together with --msg.
Data and exports
Each channel writes a CSV file on shutdown or checkpoint. Files are timestamped per session.
sigless --address 192.168.50.148 --ch1 --out ./logs
# ./logs/sigless.<timestamp>.CH1-0.csvExample: log to a dedicated folder, roll logs with Sigmark, then commit to git.
# Start Sigless and write logs to ./logs
sigless --simulate --ch1 --web 8000 --out ./logs
# Roll log files a few times
sigmark --ip 127.0.0.1:8000 --checkpoint --ch1
sigmark --ip 127.0.0.1:8000 --checkpoint --ch1
sigmark --ip 127.0.0.1:8000 --checkpoint --ch1
# Commit the generated CSV files
git add ./logs
git commit -m "Add Sigless log captures"Data format
Sigless writes compact CSV files that are easy to inspect, archive, import into spreadsheets, or process with scripts. Each row is either a power reading or a structured event message.
timestamp,channel,action,payload
1775620658490,CH1,POWER (Simulated),2.742
1775620663264,CH1,MESSAGE,"{""action"":""start"",""participantid"":""P02"",""runid"":""F2"",""flowid"":""Ca""}"
1775620663490,CH1,POWER (Simulated),3.022
1775620666297,CH1,MESSAGE,"{""action"":""stop"",""participantid"":""P02"",""runid"":""F2"",""flowid"":""Ca""}"timestamp
Unix timestamp in milliseconds, suitable for precise ordering and conversion to local time.
channel
The capture channel that produced the reading or event.
action
Reading type, such as power values or lifecycle messages from Sigmark.
payload
Numeric reading value or JSON event data with run, flow, participant, and action details.
How to get Sigless?
Need help, onboarding guidance, or a lab-specific workflow review? We are happy to help.
Sigless is built to support scientists and lab personnel who rely on trustworthy, automated readings. We make it available on request to research teams and members of the scientific community working on projects that advance science, improve reproducibility, or strengthen lab workflows.
Security notes
Sigless stores data locally by default. Use OS-level disk encryption for sensitive environments.
sigless --out /secure/sigless --verbose 0Privacy
Sigless and Sigmark do not send measurement data, event messages, CSV exports, or generated results to NoveltyGraph or any other external server. The tools can be run in complete isolation on a local machine or private lab network.
Sigless connects only to the instrument address and local web server endpoints that you explicitly
configure. Sigmark sends events only to the Sigless server address passed with --ip.
You retain all rights to measurements, logs, reports, exports, derived analysis, and any other results produced with Sigless or Sigmark.
No telemetry
Sigless and Sigmark send no measurement data to NoveltyGraph.
Explicit sharing only
No external sharing happens unless you explicitly configure it.
Isolated operation
Run fully isolated on local machines or private lab networks.
Your results
You keep all rights to logs, exports, reports, and derived results.
Versions
Use the latest docs for current usage, or open an archived version when you need older behavior.
Version 0.4.8
Latest documentation and current recommended reference.
Version 0.4.3
Archived documentation for older Sigless 0.4.x usage.
Troubleshooting
Check connectivity and confirm channels are enabled.
sigless --address 192.168.50.148 --ch1 --verbose 2
sigless --simulate --ch1 --web 8000
If connection fails, confirm the instrument is on the same subnet and that the SCPI port (default 5025) is
open.
FAQ
Where are logs stored?
By default, Sigless writes CSV files to the current directory unless --out is set.
Can I disable the web UI?
Yes. Use --web 0 to disable the server entirely.
How do I update?
Download the latest binary and replace the existing executable.
Does Sigless require internet access?
No. It runs locally and connects directly to your instruments over TCP.
Can I run it headless?
Yes. Run with --web 0 to disable the web server and log via CLI only.
Where do checkpoints go?
Each checkpoint rolls a new CSV file in the folder set by --out.
Why does macOS/Linux say permission denied?
Make the binary executable first: chmod +x sigless.
Is my data shared with third parties?
No. Sigless runs locally and does not send analytics or telemetry to third-party services.
Is this version free?
Yes. The current version is free to use forever.
About
Built by NoveltyGraph to assist researchers and lab personnel with reliable, automated Sigless readings.