Hi

Having no luck with either the HiTechnic Accel or HiTechnic Infrared Seeker V2.
Using v4.26 with latest kernel and firmware (*1.06X), and latest posting of
robotcdriversuite-master.zip (from today).

Both example programs hitechnic-accelerometer-test1.c and hitechnic-irseeker-v2-test1.c from the
driver suite compile and download fine but in both cases the first readSensor() call produces the Debug Stream
message "ERROR, You have not setup the sensor port correctly.
Please refer to one of the examples."

I have the sensor connected to S1 in both cases, and have tried changing S1 in the test programs (and sensor plugin) to S2,
and still get the same error. Have also tried this on two separate EV3 bricks (hardware v0.60). Other non-I2C sensors are working fine
so I know the EV3 brick ports are good, and the HiTechnic sensors are also known good (they work on my older NXT brick)

|Have tried the Robot menu Test I2C Sensors Utility dialog (with both sensorI2CCustom, and the specific HiTechnic sensor type), and output messages 0x02 0x42 and 0x10 0x42, respectively, for the accel and IR sensors and I always get I2C Bus errors ( I tried lots of other combos like asking for 0 or 1 or 6 bytes of reply , registers 0x08, 0x10 etc with same bus error)

Anyone had any success with either sensor?

Thanks

There is an issue currently with the EV3 and SensorType[]. We're very busy working on it. The sensor is basically not being configured properly. It is my #1 priority to fix this week.

= Xander

Xander:

Great to see you guys are already on top of this. I found the new AutoID and SensorType[ ] behaviour strange as SensorType[ ] was always returning a zero sensorNone value.

Thanks!

Auto-id for non-EV3 sensors is not as functional as we'd like. Unfortunately, it's what LEGO implemented, so we're a little stuck with it. The extended firmware does have facilities do disable a LOT of the idiosyncrasies of the underlying LEGO VM.

= Xander

I am trying to use a MindSensors Ir-Dist Long range and it always outputs 3. Just wondering if this is a related issue?

If you're using an EV3 then the answer is yes.

= Xander

mightor, I had the robotcdriversuite-master.zip and as mentioned, it is compiling correctly. I had some issues while downloading it initially but it turned out to be a simple grounding issue.However, I’m still not being able to read the sensor status. Have you guys patched this small issue with the EV3 yet? I’m making a small project using V4.26. I’m posting in this thread since I’m using the exact same firmware.

Sorry to be a bug Xander, how are you progressing with bringing 3rd party sensors online for EV3? I'm really looking forward to completing programming my EV3 project and starting on my target bot!
Take a look!
http://i.imgur.com/1Dwl83o.jpg

I heard that you will soon be working for Robomatter. I hope they treat you well this community is blessed by your knowledge & experience.

Bump, any progress with 3rd Party sensors with EV3?

Yes, there is! I now have the EV3 I2C stuff working and will restart the development of the 3rd party driver suite for the EV3.

= Xander