uci-i2c-bus/examples/bus.mjs

/*
* i2c bus with both unix and tcp socket using defaults.  For TCP that is host OS name and port 8080
*
*/
import Bus from  '../src/bus-packet'
// const PATH = ''

  ;
(async () => {

  let i2cbus  = new Bus({id:'i2c-bus'})

  await i2cbus.init()

})().catch(err => {
  console.error('FATAL: UNABLE TO START SYSTEM!\n',err)
})
FIRST commit of socket/packet based i2cbus with separate class bus-packet It is functional and working with example bus to run (on rpi) and various clients 2018-01-31 18:42:11 -08:00			`/*`
			`* i2c bus with both unix and tcp socket using defaults. For TCP that is host OS name and port 8080`
			`*`
			`*/`
			`import Bus from '../src/bus-packet'`
added arguments checking on incoming package 2018-02-10 12:34:42 -08:00			`// const PATH = ''`
FIRST commit of socket/packet based i2cbus with separate class bus-packet It is functional and working with example bus to run (on rpi) and various clients 2018-01-31 18:42:11 -08:00
refactored for changes to uci-base e5059368a9b8e655a7332b032330ff47aa0acbf0 2018-02-04 14:19:44 -08:00			`;`
FIRST commit of socket/packet based i2cbus with separate class bus-packet It is functional and working with example bus to run (on rpi) and various clients 2018-01-31 18:42:11 -08:00			`(async () => {`

better socket default port (1776) and path (using SOCKETS_DIR environment variable added logger 2018-02-07 10:41:56 -08:00			`let i2cbus = new Bus({id:'i2c-bus'})`
FIRST commit of socket/packet based i2cbus with separate class bus-packet It is functional and working with example bus to run (on rpi) and various clients 2018-01-31 18:42:11 -08:00
			`await i2cbus.init()`

			`})().catch(err => {`
			`console.error('FATAL: UNABLE TO START SYSTEM!\n',err)`
			`})`