I am going to use Tetrix Max to build a robot. And instead of Lego ultrasonic sensor I want to use LIDAR-Lite.
So, I don't have to buy EV3 set to get details or motors/sensors. I need only a brick. But brick costs an insane price — 220 EUR http://www.amazon.de/dp/B00E1P3ACK
. Compare it to Raspberry Pi 2 — A 900MHz quad-core ARM Cortex-A7 CPU and 1GB RAM for the much more reduced price (http://www.dexterindustries.com/shop/br ... indstorms/
I see https://github.com/DexterInd/BrickPiJava
but... leJOS is the main reason why I want to use BrickPi. I am professional java developer and I want to use high-level java library to program my robot (actually, I will use Kotlin language instead of Java). And, indeed, leJOS is impressive.
Could you please explain me why "I think we were mainly put off by the difficulty of developing firmware for the BrickPi"? As far I see here — viewtopic.php?f=18&t=7015
(Device I/O https://wiki.openjdk.java.net/display/dio/Main
) it should be easy for any java developer to support devices. And devices is the only platform-dependent code in the leJOS.
So, it is not a complex (in terms of time) task to reimplement platform-dependent code in the leJOS to support BrickPi. Am I right? (I need a support of Tetrix motors/servos and LIDAR-Lite sensor (as far I understand (https://lejosnews.wordpress.com/2015/05 ... ar-sensor/
) this sensor is not yet supported anyway)).