Bot Bench I'd Rather Be Building Robots
There’s a new instalment of the Driver Suite. It’s still a bit of a work in progress at the moment, with regards to the RS485 stuff. I’m busy overhauling the RS485 code in the Dexter Industries dWifi and NXTBees, so for now, I would advise you to use temporary ones that John posted here: [LINK].
IMPORTANT NOTICE(S)!
- The NXT2WIFI driver is still a bit funky. Like I said before, I am working on it!
- The Dexter Industries dWifi and NXTBee drivers are also being worked on.
- You can’t change the range in the Mindsensors Absolute Gyro yet.
- This suite will not work with anything less than ROBOTC 3.54, make sure you update your IDE.
What’s new?
- Added a driver and test program for the Mindsensors GlideWheel-AS sensor
- Added a driver and test program for the Dexter Industries NXTChuck
- Various fixes for stuff they changed since ROBOTC 3.51
Coming soon
- A proper driver for the NXT2WIFI, dWifi and NXTBee
How can you help?
Send me your bug reports, tell me what’s not working for you. Alternatively, leave words of encouragement, kudos and/or compliments via email or in a comment. If you want to know how else you can help me, click here: [LINK].
Where can I download it?
You can get it at the usual place: [LINK].
Where do I find RobotC 3.54? The latest version I can find is RobotC 3.51. thanks…
Is there a newer released version of RobotC since v3.51? I checked the website and only see version 3.51 currently.
Must be coming soon.
Hey there,
3.54 will be released later today. Release was delayed because there’s a competition going on this weekend and they didn’t want teams upgrading before a match. I will put up a post when it’s available 🙂
My complements on your driver suite! It will be very useful to me and many others. Fantastic job!
Thank you for the kind words!
hey Xander,
can you give me an eta for the final nxt2wifi driver?
I need it for my Bachelor thesis 🙂
or is the tcp communication already working fine?
regards
Lukas
Lukas,
Drop me a mail (just look for the address in the header files) and I can send you what I have now, so you can start with it. The TCP stuff should work fine. I will probably release something once I am back from Prague.
= Xander
I just installed Robot C 3.54. When I go in to the motor/sensor setup many f the HT sensors are there but not the MUX (only the touch MUX). Should I install this driver pack to have the most up to date drivers or are they already in 3.54?
Thank you
They’re actually in the samples directory. However, there is a bug in 3.54 that prevents the SMUX (and many other drivers) from working properly. I would recommend you upgrade ROBOTC to 3.55 beta 2, which you can download here: http://www.robotc.net/forums/viewtopic.php?f=52&t=5122 , it fixes quite a few bugs 🙂
Also, I’ll be releasing a new driver suite version very shortly (actually working on getting ready to release as I type this). So stay tuned 🙂
Thank you for the heads up on the bugs. If I understand your e-mail correctly, instead of using what is in the samples directory with my RobotC download, I should download the driver suite into a directory and setup RobotC to look at it? I am setting up on a bunch of laptops for a systems engineering course I teach next semester so I want to make sure I get it right before I do it on all of them.
Bill
I just installed Robot C 3.54. When I go in to the motor/sensor setup many f the HT sensors are there but not the MUX (only the touch MUX). Should I install this driver pack to have the most up to date drivers or are they already in 3.54? Thank you
They’re actually in the samples directory. However, there is a bug in 3.54 that prevents the SMUX (and many other drivers) from working properly. I would recommend you upgrade ROBOTC to 3.55 beta 2, which you can download here: http://www.robotc.net/forums/viewtopic.php?f=52&t=5122 , it fixes quite a few bugs 🙂
Also, I’ll be releasing a new driver suite version very shortly (actually working on getting ready to release as I type this). So stay tuned 🙂
Bill,
You are correct. My release cycle is different from that of ROBOTC. The ROBOTC devs always include the latest driver suite at the time of their release, but there’s always a chance I release something new in between those releases. We are working on a partial installer that will update the Samples directory with the latest driver suite, but that’s still work in progress 🙂 In the mean time, just subscribe to the blog’s RSS feed.
= Xander
I purschased a Hitechnic SMUX for use in FTC. My team is using RobotC v. 3.54, installed Driver Suite v 3.1 and used the sample code to help us in our programming. In our autonomous code, we are using a SMUX port for a Lego ultrasonic sensor and two NXT ports for IRv.2 sensors. As a result, the IR sensors and ultrasonic sensors are not as accurate as they were when using them without the SMUX. In our TeleOp code, we are using two SMUX ports for Lego Touch Sensors. The sensors are always active, no matter if the sensors are pressed or not. Any help would be greatly appreciated.
Hi Romeo,
Could you explain to me how you’re finding the measurements to be less accurate? Both the US sensor and IR Seeker V2 are digital sensors, so there should be absolutely no loss of accuracy. As for using ROBOTC, you should be switching to 3.55B2 if you want to use my driver suite. There are serious casting issues with 3.54, which really mess with the data coming from the sensors. You can download 3.55B2 from here: http://www.robotc.net/forums/viewtopic.php?f=52&t=5122