Hello and thanks for your fast reply.
For the first 5 seconds (read more on this here
https://digistump.com/board/index.php?topic=1675.0)
VID = 0x16D0
PID = 0x
0753
then
VID = 0x16C0
PID = 0x05DF
also I found the following interesting scheme
PID dec (hex) | VID dec (hex) | Description of use
==============+===============+===================
1500 (0x05dc) | 5824 (0x16c0) | For Vendor Class devices with libusb
-------------------+-------------------+--------------------------------------------
1503 (0x05df) | 5824 (0x16c0) | For generic HID class devices (which are NOT mice, keyboards or joysticks)
------------------+-------------------+--------------------------------------------
1505 (0x05e1) | 5824 (0x16c0) | For CDC-ACM class devices (modems)
-------------------+-------------------+--------------------------------------------
1508 (0x05e4) | 5824 (0x16c0) | For MIDI class devices
-------------------+-------------------+--------------------------------------------
As per my understanding of this , attiny85 doesn't come with hardware usb support (UART?) . To workaround this issue digispark got a library you must include in arduino projects
#
include <DigiCDC.h>void setup() {
SerialUSB.begin();
}
so VID / PID is a matter of software (libusb?) according to the following readings:
https://digistump.com/board/index.php?topic=988.0https://digistump.com/board/index.php/topic,1458.15.htmlA small relief: there is a couple of projects interfacing digispark with apache cordova, so, I really think it should be possible to make it work with droidscript too!
(example of arduino code)
https://github.com/digistump/Digispark_Cordova_CDCLED/blob/master/ArduinoCode/CDC_LED/CDC_LED.ino