There are maven targets for the libraries. Please refer to the wiki and or example apps. Can you please test the precompiled apps before proceeding to you own built ones? On Jun 16, 2016 15:58, "Daniel Buchanan" <[email protected]> wrote:
> Hi Ytai, > > It does show up as /dev/IOIO0, regardless of which board it is using. > I'm not sure what the undefined version is, it's always done that. > This software is a tad old (a couple of years), and as such at the time I > wrote it there was no pre-compiled version of the ioiolib that I could use, > so I compiled my own. > > They are using the exact same jar file on both the laptop and the > Raspberry Pi. > > Is there somewhere that I can download a pre-compiled ioiolib from? such > that I could drop it onto the classpath? > > Kind Regards, > Daniel. > > On Friday, June 17, 2016 at 10:54:03 AM UTC+12, Ytai wrote: >> >> Is the new board appearing as a /dev/IOIOx device? Are you using the >> exact same jar with both versions? What's the deal with the undefined >> IOIOLib version? >> There have been some changes in the library that may have caused this >> problem, but I cannot see how the firmware version is related. >> On Jun 16, 2016 15:46, "Daniel Buchanan" <[email protected]> wrote: >> >>> Hi There, >>> >>> We have just started getting new IOIO boards, and at present they will >>> not connect to our software running on Linux (Raspberry Pi). >>> >>> I can connect to both the old and new IOIO-OTG boards using my Windows >>> 10 laptop, but the Raspberry Pi will only connect to the old board. >>> >>> The only difference I can see between the old and new boards is the >>> versions of the bootloader and firmware: >>> Old: >>> >>> - Bootloader ID - IOIO0401 >>> - Firmware ID - IOIO0500 >>> >>> New: >>> >>> - Bootloader ID - IOIO0402 >>> - Firmware ID - IOIO0506 >>> >>> Aside from this, both the Raspberry Pi and my Windows 10 laptop are >>> using the same version of java, the same version of the ioiolib and >>> associated libraries, so I'm a bit stumped as to what could be causing >>> this, the Raspberry Pi just sits there and waits for a connection from the >>> IOIO (new board) whereas with the old board it just connects and goes on >>> its merry way. My laptop works correctly with both boards, I thought maybe >>> it was a difference in the udev rules or something, but I couldn't see any >>> major differences in the Windows driver that would affect the udev rules >>> for the Raspberry Pi. >>> >>> I've included screen shots from the run of both the old board and new >>> board, on my laptop as well as the Raspberry Pi (photos from my phone, >>> sorry about that). >>> >>> Any suggestions would be very much appreciated. >>> >>> Kind Regards, >>> Daniel. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "ioio-users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at https://groups.google.com/group/ioio-users. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > You received this message because you are subscribed to the Google Groups > "ioio-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/ioio-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/d/optout.
