Hi Doug, thank you for your feedback! The industrial modules are not out yet (16 isolated I/Os, isolated serial ports and 0-10v analog is in the pipeline,. 16 I/O is finished from the driver side). Yes, I2C are accessible separately, but the SPI is used by our kernel driver. You can however plug in ...

We have just presented the RasPiComm+, a modular extension platform for the Raspberry Pi I had a chance to show it to Eben Upton yesterday at the Electronica fair and he really liked it. Here is a link to our indiegogo campain: https://www.indiegogo.com/projects/raspicommplus-all-in-one-raspberry-pi...

this is the smallest of the range, yes, bigger than a fingertip but still quite small with very good resolution. I'll give you more details as soon as I can do that.

You are quite correct regarding the usually required quantities. This display is not yet on the market, we got an early (if not the first) sample. But this one will be available in small quantities too (even in quantities of 1). E-Ink is really a fascinating technology. I love how the image stays if...

You should try 'transmitter idle" instead of "transmitter empty" The field name says "transmitter empty" for bit 5 of the AUX_MU_LSR_REG, but the bit goes high if the transmit FIFO can accept at least one byte. So it is only 0 if the tx buffer is full, in all other cases it ...

Did you disable the debug output and serial port login on /dev/ttyAMA0? As a default, the kernel uses the serial port to post debug messages. You need to disable that, otherwise sending data will fail. you should do two things: • /boot/cmdline.txt: remove both parameters which point at ttyAMA0 • /et...

Hi, yes, I am very familiar with this problem since my first approach of my RasPiComm extension board was the same. The short answer is: There is no easy way (if any) to know when the sending buffers are really empty. You can call API functions which are supposed to tell you that, but they don't. I ...

You could use the MAX3140 as we do in our RasPiComm (raspberry pi piggyback board). The advantage is that we offer the schematics on our website and you have ready-working device-drivers (accessing the RS-485 via /dev/ttyRPC0). Or use a RasPiComm directly which you can get at RS-Components. I chose ...

We offer an RS-485 extension board to the Raspberry Pi - RasPiComm. Have a look at our forums. You can build it yourself and use our drivers (we have the schematics online and also supply open-source tty-device drivers to interface with the RS-485 port) or buy the RasPiComm at RS-Components. Have a ...

Hi, just wanted to share an e-ink display test with you. This is still non-released display technology and a preproduction sample, but still quite impressive. Cannot tell details of the display yet (signed NDA) - it is a small one as you can see but with good resolution. But when it is there I'll po...

Yes, of course! Just go to local RS-Components website and search for RasPiComm (in Germany for example http://de.rs-online.com).

Daniel

We released our RasPiComm board, a tiny Raspberry Pi piggyback board with RTC, RS-232 and RS-485 support, as well as a joystick, 5 inputs and 2 outputs, a I2C and SPI header. We support it on our forum http://www.amescon.com/forum.aspx and provide and open-source API on https://github.com/amescon/ra...

Just a short update: The RasPiComm inputs are now 5V tolerant:
http://amesberger.wordpress.com/2012/08 ... picomm-v3/

Cheers, Daniel

the inputs are still 3v3, the outputs are 5V and can drive 5V relays directly. I did not convert the inputs to 5V, if I'd do that I would rather do wide range inputs (5-24V) but that would need a bigger PCB. The I2C is pulled up to 3.3V but you can still connect 5V devices, I do that too with the DS...

Hi, I developed a Raspberry Pi board featuring a RS-485 and RS-232 connector, 2 outputs, 5 inputs, RTC and I2C connector. Find out more about the board on my blog: http://wp.me/p2gMgK-d This is especially interesting for automation (that's what I do for a living) and robotics. If you like it follow ...