0.6.2

• Added several different pin aliases for BeagleBone Blue and PocketBeagle.
  • P1_x and P2_x for PocketBeagle where x is the connector pin number
  • ADC_x, BAT25/50/75/100, DSM2_x, Ey_x, GPy_x, GPS_x, GREEN/RED/WIFI/MODE/PAUSE, S1_y_x, UTy_x for BeagleBone Blue where x is the connector pin number and y is the port number or chip select as specified by the connector where it applies
  • P9_15B, P9_41B, and P9_42B have been added for BeagleBone Black
  • GPIO_x for all boards, where x is the GPIO number, not done as bank+offset, ie. GPIO_63 not GPIO1_31
  • Raw numbers will be mapped to GPIO_x, where x is the raw number provided
  • Ax for all boards, where x is the analog input (AIN)
  • Case is now ignored, though uppercase is the definitive approach
  • Separators can now be '_', '.', '-', or ' ', but '_' is the definitive approach
  • Leading 0s in numbers are now ignored, but no leading 0s is the definitive approach, ie. P2_09 will map to P2_9
  • Pins can also be specified using MUX_0Xnnn, where nnn is the hexadecimal offset in the multiplexing control registers
• Support for PWM access and pin mode reading on newer 4.4, 4.9 and 4.14 kernels has been added.
• Dependency on npm ffi module was removed.
• Support for versions of nodejs earlier than 4.x was removed.
• PocketBeagle and BeagleBone Blue identifiers were added for b.getPlatform().
• Kernel allocated LEDs for BeagleBone Blue are handled by b.pinMode()/b.digitalWrite().

Known issues:

• When doing running non-root and doing PWM enables with b.pinMode(..., b.ANALOG_OUTPUT, ...) or b.analogWrite(), it may take several milliseconds for the udev rules to fix the permissions on the relevant sysfs interface. The result is your PWM accesses may fail on your first try and then run on subsequent re-runs of the program.
• Requests to clean-up the API to be more consistent haven't yet been handled.