Take a look at the driver suite in my signature. It has drivers for about 78 different sensors and covers pretty much everything that's been on the market for the last 4 year and now. Be sure to read the documentation and examples that ship with it.

Make sure you check the version of ROBOTC, should be in help->about. The IRSeeker should be attached to S1. The -1 indicates there is no connection with the sensor. Which exact program are you trying to use? There are a couple of IRSeeker programs.

Xander, is there any technical reason why I have to choose sensorI2Ccustom for a sensor type instead of the built in types for magnet or compass or any other hitechnic sensor? Unless I disable sensor type checking your drivers throw errors at me. It's not a problem-I'm just curious.

It's quite simple. Using my drivers and the built-in ones would be like having two people simultaneously shouting commands at you. Your responses would be garbled and neither shouters would know which response belonged to which request

Just stick with the sensor type, as used in the examples. The analogue and i2custom sensors are really barebones sensor types that allow me to decide what is being communicated to the sensor, not the firmware.

So, don't disable the sensor checking, just make sure you use the proper sensor types.

Who is online

Users browsing this forum: No registered users and 2 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum