With the beta version 1.17, I have problems with the I2C bus,
For the status query nStatus = nI2CStatus [kSensorMuxPort]; "
I get the error constant ERR_COMM_CHAN_NOT_READY
Reported. I use the engine for NXT multiplexer (MTRMX-Nx) by Mind sensor.
Even with the Senso Kit for NXT with PCF8574 of IC Sensors will Mind
Produced the same error!

You will get far better and faster replies if you remove the "snarkiness" from your posts and remain on a polite level. Unfortunately, we don't all read German.

I had no problems with my Mindsensors motor MUX and version 1.17. I have just pumped 20K messages to it without error. One tricky thing about the motor MUX is that it can be programmed to have a different I2C which can cause it to not respond. My motor MUX is set to the default I2C address of hex B4.

What I suggest you do is use ROBOTC's "NXT I2C Test Utility" to verify that your I2C devices are working. You can get at it from the command "Robot -> NXT Device -> Test I2C". Use the "Help" button to figure out how to work it.

FIrst test the Lego Ultrasound sensor to verify that it is working and that you've figured out how to use the diagnostic screen. The best bet is to set the "Output Message" field to "2 10" and "Reply Len" to '8". When you poll "Once" the "Reply field should be "SONAR..". Use "Send Continuous" to verify a couple of 100 messages.

Now you want to try the MotorMux. Set it up on a different sensor port. Change "Output Message" field for it to "B4 10". The reply you get back should be "MTRMUX..". If so, then everything is working OK. If not, it's either broken or set to a different address. Read the MindSensors web page on changing the address. You might want to try "2 10" in case it has been set to the more standard address "2".

If above doesn't work and it does work with NXT-G then post again with details on what is not working, what is working, etc and I'll try to give you next diagnostic steps.

Tue Mar 04, 2008 5:18 pm

Legorentner

Rookie

Joined: Fri Feb 15, 2008 5:53 amPosts: 6Location: Germany

The test with the NXT I2C test utility "has worked,
Only in the program met this error constant!

sorry, if you don't speak German, but i purchased your software in Germany from a German dealer, I payed in German currancy, and so I expected to get help in German (not only in this forum, but also in the help files of the software).

If you sell your programs in foreign countries (Germany, Austria, Switzerland, France, Spain, Italy, Portugal, Poland, even Japan), it is really recommendable that you are able to give support even in these foreign languages. Not every hobby user in Europe (or Asia) speaks English! (Actually in Europe more people are speaking German as a native speaker than English, and similar it is to French - not everybody in the world is an English speaking U.S. American!)

This is not like support I expect to freeware such like NXC, but I have payed for your software!

Maybe we both try to understand the other one's posting as good as possible (by babelfish), but complicated relations and problems often can not be explained by me in a foreign language. This is even hard enough in German, for I am no IT expert or professional programmer but only a Lego Mindstorms layman (do you say: "layman"? I just mean: non-professional, hobby user (??) - get what I mean?). So in these cases I will have to write in German.

My respoonse on Mar 4 suggested some ares to investigate to confirm that your configuration was working OK and that the MUX address had not been inadvertently changed. I asked for feedback on whether this fixed your problems with an offer of furthur assistance if you were still having problems.

Are you still having problems with your Motor MUX?

For a description of C functionality in ROBOTC see recent post in another thread.

Wed Mar 12, 2008 3:59 am

Dick Swan

Creator

Joined: Fri Feb 09, 2007 9:21 amPosts: 616

Legorentner wrote:

The test with the NXT I2C test utility "has worked,Only in the program met this error constant!

I can't tell from the code snippet you posted whether you have configured the sensor type. You have to set the sensor type to an "I2C custom sensor". Otherwise the firmware will give an error indicating that the sensor is not configured for I2C messaging.

Wed Mar 12, 2008 4:05 am

Legorentner

Rookie

Joined: Fri Feb 15, 2008 5:53 amPosts: 6Location: Germany

Now I use again the version 1.10 and will On the official release of version 1.17 wait.
They write:

Quote:

You have to set the sensor type to an "I2C custom Sensor". Otherwise the firmware will give an error indicating that the sensor is not configured for I2C messaging.

I run the engine at the port Mux-4 and had him as Sensor type [kSensorMuxPort] = sensorI2CCustomFast9V;
Declared! In version 1.10, I have no problems Problems!

Best ever thanks for your efforts, I should Further problems, I will sign.

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