Q: Why do you sometimes call it RasPiComm+ and sometimes PiloT?
A: RasPiComm+ was the project codename for the PiloT, but we're now calling it PiloT. If you see some old reference, we haven't gotten to updating it yet.
Q: When will the PiloT be released?
A: Very soon! We've just fulfilled our indiegogo batch.
Q: How many different modules will the PiloT+ support?
Q: What type of modules are planned for the PiloT Launch?
A: The following list shows the different modules we want to have ready for the launch:
- Debug Header
- input (8-ports)
- output (8-ports)
- rs485 (1-port)
- rs485_2p (2-port)
- rs485_4w 4-wire
- rs232 (1-port)
- rs232_2p (2-port)
Q: Is that all? Do you have more planned?
Of course we do!
We're currently testing:
Q: What kind of software support will you provide?
A: We will provide drivers in the form of kernel modules, firmware for the PiloT, a setup script to configure your PiloT and example programs that make use of the modules.
Q: Where can I buy it?
A: We will keep you posted as soon as it's available. If you want, you can signup at our newsletter:http://www.amescon.com/newsletter/subscribe
" onclick="window.open(this.href);return false;
and we will send you an e-Mail when it's available.
Q: How do I get the driver?
A: We will provide the driver as a kernel module:
1) pre-compiled for the rasbpian kernel and packaged as a debian package (.deb)
2) and in source code form hosted on our github page,
just like we did with the RasPiComm.
Q: What can I do with it?
A: Well, the possibilities are nearly endless. I'd recommend taking a look at the tutorials here to get some ideas.http://www.amescon.com/tutorials
I will update this thread as necessary.