@ellfire, not exactly, I’ll explain better below.
Makeblock offers their libraries to interact with their hardware, while this makes it easier, it actually becomes a pain when you want to use another library.
The bottom line is none of the me devices are unique. They’re adapted versions of commonly found parts. The main thing is the pinout is changed from standard headers or pads to an RJ25 connector.
So, if we take the ultrasonic sensor as an example, but we want to use the NewPing library, we have to tell the NewPing library which pins the meSensor is using. Using the pinnout image below, you can sort of figure out which pins that RJ25 connector is connecting to.
In the case of the meSensor, it has 3 pins GND, 5V, and SIG
This identical to the Paralx Ping(( module https://www.parallax.com/product/28015:
And differs from the more common HC-SR04 and SR05 modules that have a Trigger and Echo Pin
In summary, the MeRangeSensor and ParalaxPing(( are nearly identical and both use the SIG pin for trigger and Echo.
If use the NewPing library, you will need to supply the same pin for the trigger and echo depending on which RJ25 port you connect it to on the Orion board.
See lines 7 & 8 in https://github.com/PaulStoffregen/NewPing/blob/master/examples/NewPingExample/NewPingExample.ino.
So if you plugged the RJ25 into port 4, you’d change those lines to pin 2. If that doesn’t work, try pin 8. One of the two will work.
If you used port 3, you’d try pin 13, then 12.
Hope that helps, and feel free to post pictures or your code if you need more help!