I will add support for Adis16490

[messplay]

I will add support for Adis16490

[7675t]

Hi, Could you clarify your point? I believe ADIS16490 is also similar to ADIS16470, while I'm not sure they are identical. Anyway it is not so difficult to adapt the package to ADIS16490. If you have the device, please try to make it work by yourself and send a PR. When you have concrete question or problem, we can support you as possible. Thank you 😄

[messplay]

Yes code appear very similar, just a "little" diferencie my usb-spi interface is https://www.mikroe.com/usb-spi-click, based in mp22210 microchip also.

[7675t]

Hey, it is a big difference 🤓 Our code depends on the USB-IIS module which use PIC and has original command system as an ACM device. I didn't know MCP2210. It looks also good to use, but I don't have the one. If you want to use that module, you need to rewrite almost all the communication methods.

I know current package should be organized not to depend on the communication device, but is takes some time and currently we recommend to use USB-IIS. It is handy because no device driver needed.

[messplay]

Well just now(19:41 GMT-5) I am rewriting src/16xxx.cpp file to setup with new module, appear be very similar just changing SPI config commands (however I will buy IIS, just in case =)

[7675t]

Great, please send PR if you ready!

[messplay]

Well I have one question why in code always you use 0x61 in buff[0] = 0x61; is custom?. I read in 16470 datasheet but I did not have an answer.

[7675t]

No, it is not the spec of ADIS16470, it is spec of USB-IIS. USB-IIS need a command byte on the top. Please consult USB-ISS datasheet.

[7675t]

Please reopen if you have further questions.