AOSX and 383L+ looking through the keyhole
Well it's cloudy.. and what do we do when it's cloudy? That's right - we probe USB devices..
The 383L+ seems to be:
a) using a non-standard USB vendorId
b) doesn't seem to support VCPs (virtual serial ports)
c) doesn't have the same USB-bus chatter as a FTDI et al..
d) transfer speed well over serial.. indicating block speed.
So they're using a USB block device to give them high speed communications.. bets on the very popular Cypress chips (just so happens that Apple give a USB block example using a cypress chip in their dev sample code for USB development..).
Now on windows, nebulosity uses the ATIK DLLs to interact with the atikhub driver which then interacts with the standard windows USB hub drivers.. well that's what the USB sniffer seems to think.
It also shows a close similarity to the ye-olde protocol of the 16ic. Now the 16ic uses an FTDI serial and so it seems to be in 8bit hell (I'm assuming the PIC controller is 8bit too).
Now usually as the PC has more cpu power it attempts to communicate in a more friendly form for the poor low power onboard processors.. it seems the 383 is no exception.. with the messages appearing in 16bit numbers - including the numbers that had appeared in 8bit previously.
So given this... with a little jiggery pokery we should have some very basic control of the 383 soon..
0 Comments
Recommended Comments
There are no comments to display.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now