Raspberry Pi with EnOcean Pi and EnOcean USB 300

Question

Good afternoon,

I was wondering if anyone would kindly help me with an issue.

I bought an EnOcean USB 300 and an EnOcean Pi, to try and get either to work with a Raspberry Pi. I have been following the official instructions until it came to these commands for the USB 300 and EnOcean Pi respectively:

hexdump -C < /dev/ttyUSB0

hexdump -C < /dev/ttyAMA0

Once I enter these commands, there is no output or error messages. According to the linked document there should be numbers outputted. I have tried with two different Raspberry Pi 3s with fresh and up to date raspbian OS, plus a Raspberry Pi Zero, and every time there is no output or error message when I enter these commands. I have tried searching google and forums, and I could not find an answer. I tried the USB 300 in a windows PC, and it worked, so it is not broken hardware. I have not got as far as installing fhem server either, so that cannot be affecting anything. I have set the Baud to 57600 as well using

stty -F /dev/ttyUSB0 57600

Does anyone have any suggestions? I might be missing something simple! Or is the fact that there is no output unimportant?

Many thanks in advance

Henry

fvan · Accepted Answer

That is correct: the hexdump command will show the data received by the gateway, sent by the sensors. No sensors = no data.

If you want to play with sensors, this kit contains a switch, a contact and temp sensor: SENSOR KIT-868 ENOCEAN, SENSOR KIT FOR RASPBERRY PI, 868MHZ | Farnell element14

Just be sure to pick the correct frequency to match that of your gateway, otherwise no data either.

fvan · Answer

Have you tried the same command, but with "sudo" ?

electronics8263 · Answer

Thanks Frederick, that was indeed the issue. Thanks again for all your help. You're the man!!

clem57 · Answer

What does the output from "lsusb" show? Are there other USB devices? Are they on a powered hub? If using the Raspberry Pi 3, there are addtional setps need to complete this install. Clem

electronics8263 · Answer

Hi Clem, Thanks very much for the prompt response, it's really appreciated. Below are lsusb outputs for the EnOcean USB 300, with and without the keyboard and mouse attached: pi@raspberrypi:~ $ lsusb Bus 001 Device 006: ID 046d:c077 Logitech, Inc. Bus 001 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT 232 USB-Serial (UART) IC Bus 001 Device 004: ID 413c:2101 Dell Computer Corp. SmartCard Reader Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@raspberrypi:~ $ lsusb Bus 001 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT 232 USB-Serial (UART) IC Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The keyboard and mouse and plugged directly into the Raspberry Pi 3, no powered hub. What are the additional steps Clem? I thought I followed the linked guide exactly, but I might have missed something obvious (I have some linux knowledge, but am new to the Raspberry Pi). As an aside, I SSH'd into the Pi 3 having removed the mouse and keyboard but hexdump -C < /dev/ttyUSB0 still did not output any numbers. Many thanks again Henry

fvan · Answer

Have a look at my post on setting up EnOceanPi on the Pi3, that should work: [Pi IoT] Alarm Clock #05: EnOcean Pi and Sensors It contains all info on setting up UART and EnOceanPi on a Raspberry Pi 3.

clem57 · Answer

I see you have an attached fast ethernet on USB. Why? I am worried that the power of the USB is limited and I know from experience these take quite a bit. If you really need it, a power usb hub will be the answer. Clem

shabaz · Answer

Hi Clem! I believe it is already on the Pi, basically there is a USB port on the Pi's SoC, and it goes to some on-board combined Eth/USB hub, so that lsusb command is showing what is already on the Pi's PCB. (i.e. the Pi doesn't have a direct interface for connecting to Ethernet). I couldn't find a block diagram, so I drew this up a couple of months back, it may have errors since it is partly guesswork in the absence of schematics : ( but if anyone spots mistakes I will correct it). The LAN9514 chip on the right, and from it egresses the multiple USB ports and Ethernet.

electronics8263 · Answer

Hi Clem and Shabaz, Thanks very much for your thoughts and the diagram. I SSH'd into the Pi via wifi (so no USB or ethernet attached), with the same result (no output on hexdump -C < /dev/ttyUSB0). Do either of you have any other ideas about why this might not be working? I'll give Frederick's post a go in any case.

electronics8263 · Answer

Hi Frederick,

No output with sudo either I'm afraid.

When reading through you post though, I think I may have misunderstood what hexdump -C < /dev/ttyUSB0 or hexdump -C < /dev/ttyAMA0 are supposed to show. I thought the hexdump was showing the Pi gateway sending data, hence why I though I had done something wrong. Is it actually the Pi gateway listening for EnOcean nodes' signals, like sensors?

Assuming the answer is yes, I feel very silly!! No wonder I had no outputs showing, I have not even bought any sensors yet, I was just trying to get a gateway working! I think my only defence is that the official instructions said that you should get outputs after typing this command, with no mention of turning on your sensors.

Thanks again for your help guys. If any of your are in the Nottingham UK area, message me and I'll buy a you pint!

Final noob question, would this:

PTM 210 ENOCEAN, MODULE, SWITCH, RADIO TX, 868MHZ | Farnell element14

work well as an introductory sensor?

Thanks again

Henry

electronics8263 · Answer

That makes sense now, thank you so much Frederick. Once the new kit arrives today, I'll let you know how I got on, and mark the thread closed etc. Thanks again Henry

fvan · Answer

Cool, glad you got it working!