The iBurst terminal program doesn't serve much of a purpose in day to day usage of iBurst, so ethernet may be a preferred option for many users (eg connecting to a Linux machine). To actually check status and to do manual firmware upgrades one do however require the terminal program.
I can't see any reason why the same can't be achieved over ethernet using SNMP / tftp and / or a custom protocol incorporated in the firmware, perhaps with initial configuration via the USB interface, but even this can be circumvented.
I can't see any reason why the same can't be achieved over ethernet using SNMP / tftp and / or a custom protocol incorporated in the firmware, perhaps with initial configuration via the USB interface, but even this can be circumvented.