SW used to communicate with all XeThru modules on a host computer
Did you get this kind of error by running examples? or running your own program?
Any update on this?
Christian Rødli Amble updated Module Connector - Raspberry Pi with a new update entry:
ModuleConnector v 1.4.3
Read the rest of this update entry...
It's my own program. The problem fixed when I changed to another X4M300 module, I guess it was hardware problems. Also, I have an another question, if you don't mind, when changing from RUN state to IDLE state, what should I do to let it goes into RUN state again? I always get the error message when I switch from IDLE to RUN and do nothing between them.
There seems to be a firmware bug regarding the idle-mechanism that causes a reinitialization to be attempted following an idle. It will be resolved for a future release.For now, idle should not be used.
Hi, did anyone try 1.4.3 on a raspberry Pi 0 w? I couldn't get it to work, getting the following error when running the example python code:
Traceback (most recent call last):
File "x4m300_presence_simpleoutput.py", line 9, in <module>
from pymoduleconnector import ModuleConnector
File "/usr/local/lib/python2.7/dist-packages/pymoduleconnector-1.4.3-py2.7.egg/pymoduleconnector/__init__.py", line 2, in <module>
File "/usr/local/lib/python2.7/dist-packages/pymoduleconnector-1.4.3-py2.7.egg/pymoduleconnector/moduleconnector.py", line 5, in <module>
File "/usr/local/lib/python2.7/dist-packages/pymoduleconnector-1.4.3-py2.7.egg/pymoduleconnector/moduleconnectorwrapper/__init__.py", line 28, in <module>
File "/usr/local/lib/python2.7/dist-packages/pymoduleconnector-1.4.3-py2.7.egg/pymoduleconnector/moduleconnectorwrapper/__init__.py", line 24, in swig_import_helper
ImportError: /usr/local/lib/python2.7/dist-packages/pymoduleconnector-1.4.3-py2.7.egg/pymoduleconnector/moduleconnectorwrapper/_moduleconnectorwrapper.so: file too short
I figured out this problem, it's because I use 5v IO for UART, if I use 3.3v the problem was gone. The problem only occurs when I use 5v for a long time.
The ModuleConnector doesn't support Raspberry Pi Zero because it uses different SoC chip compared with RPI 2/3, but you can try MCPW in this link https://www.xethru.com/community/resources/module-communication-protocol-wrapper.97/, it is written by C, and also provides full access to the XeThru radar sensor.
I thought in 1.4.3 they Fixed build for Raspberry Pi 1/Zero.
Yes, you are right. Sorry for my fault, the software team just released this version recently, they are faster than I thought.
It seems you forget to specify the device name, the full command looks like "python x4m300_presence_simpleoutput.py -d /dev/ttyACM0". I have tested this version on RPI Zero W, it works fine!
It wasn't the device name. However I fixed the problem, I think it might have something to do with having 1.4.2 installed previously. I had to remove the 1.4.2 folder and re install 1.4.3. But it's now working.
raspberry pi 3 can connect x4m3 through SPI/QSPI? and read the radar data?
X4M03 only support uart and usb connection, but you can connect RPI3 with X4M05 through SPI/QSPI.
Thank you for your subscription!