npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@westh/serial-commander

v1.2.2

Published

Send commands via a serial port, e.g. AT commands to a modem

Downloads

29

Readme

@westh/serial-commander

Send commands to a serial port, e.g. AT commands to a modem, with predefined success criteria such as response message and delay. It also provides an easy way to log correspondence to the console.

This has been done before, but here's yet another way to do it.

Installation

npm install @westh/serial-commander

Usage

const SerialCommander = require('@westh/serial-commander') // or use import ... from ...

const serialCommander = new SerialCommander({
  port: '/dev/ttySOMETHINGCOOL', // defaults to /dev/modem
  baudrate: 9600, // defaults to 115200
  readDelimiter = '\r', // defaults to '/n'
  writeDelimiter = '\n', // defaults to '/r/n'
  disableLog: false, // defaults to false
  defaultDelay: 50, // delay [ms] before the command is issued defaults to 100
  log: string => console.log(`[${new Date().toISOString()}] ${string}`) // default logging function
})

async function main () {
  const options = {
    expectedResponses: ['OK', 'YEAH'], // defaults to ['OK']
    timeout: 500,  // defaults to 1000
    delay: 100 // defaults to defaultDelay set in the constructor
  }
  const response = await serialCommander.send('AT', options)
  console.log(response)
  serialCommander.close()
}

main()

Something like this will appear in the terminal if you are connected to a modem:

[2021-03-14T12:05:25.555Z] >> AT
[2021-03-14T12:05:25.561Z] AT
[2021-03-14T12:05:25.562Z] << OK
{
  command: 'AT',
  startTime: 2021-03-14T12:05:25.555Z,
  endTime: 2021-03-14T12:05:25.562Z,
  executionTime: 7,
  response: 'AT\r\rOK\r'
}

The message starting with >> is what your machine has sent to the serial port, everything else is what is received on the connection, and the message starting with << is the line which contains the expected response.

Testing

Running yarn test will first run yarn build and then test both the CommonJS and ESM version. You have to specify which port you wish to test before running the test(s), this is done by setting the environment variable TEST_PORT, e.g.:

export TEST_PORT=/dev/ttyUSB0

The tests sends AT to the TEST_PORT, so if that port is a cellular modem of some sorts it should respond OK.

License

MIT