Hi Jesse, thanks for getting back on this issue. Much appreciated!
Good to hear of iConnectivity's willingness to have a stab at this on their end. Would be awesome if you can work something out with them.
Do you think iConnectivity needs to change the firmware on its devices to be able to accept the NDLR on their host ports?
Based on posts in this thread I came under the impression the issue should/could/might be solved on the NDLR's side by altering the USB Descriptor configuration in NDLR's Teensy firmware.
(see posts 6 & 7 by microbug and post 9 by 0xF0):
#6 > https://conductivelabs.com/forum/showthr...63#pid3163
#7 > https://conductivelabs.com/forum/showthr...79#pid3179
#9 > https://conductivelabs.com/forum/showthr...92#pid3192
Earlier you mentioned passing on this data to Steve. Did he ever had a chance to look into the findings as posted by microbug & 0xF0?
Would be great to get some input on this issue from the NDLR dev team, thanks!
-T
Good to hear of iConnectivity's willingness to have a stab at this on their end. Would be awesome if you can work something out with them.
Do you think iConnectivity needs to change the firmware on its devices to be able to accept the NDLR on their host ports?
Based on posts in this thread I came under the impression the issue should/could/might be solved on the NDLR's side by altering the USB Descriptor configuration in NDLR's Teensy firmware.
(see posts 6 & 7 by microbug and post 9 by 0xF0):
#6 > https://conductivelabs.com/forum/showthr...63#pid3163
#7 > https://conductivelabs.com/forum/showthr...79#pid3179
#9 > https://conductivelabs.com/forum/showthr...92#pid3192
Earlier you mentioned passing on this data to Steve. Did he ever had a chance to look into the findings as posted by microbug & 0xF0?
Would be great to get some input on this issue from the NDLR dev team, thanks!
-T