pdmarsh

Eurobricks New Members
  • Content Count

    3
  • Joined

  • Last visited

1 Follower

About pdmarsh

Spam Prevention

  • What is favorite LEGO theme? (we need this info to prevent spam)
    Mindstorms
  • Which LEGO set did you recently purchase or build?
    Mindstorms EV3 31313

Profile Information

  • Gender
    Male
  • Interests
    Robotics

Extra

  • Country
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The Dexter Industries dGPS sensor manual has a reference to use I2C commands to turn on and turn off extended firmware functions that provide HDOP, altitude and number-of-satellites data. The manual also states that these extended functions can slow down dGPS processing. I am seeing some long delays in updating distance-to-waypoint data from the navigation block used with the sensor. I would like to turn off the extended firmware functions temporarily to see if the distance data gets updated quicker. However, I don’t know how to send I2C commands to the dGPS via the NXT-G configuration software, or if it’s even possible. I would appreciate any guidance I can get on how to send I2C register change commands to the dGPS sensor. Thanks, Paul
  2. pdmarsh

    Odd NXT Servo Behavior

    Hi David, Thanks for the response. A problem with feedback does appear to be the issue. I'll be able to deal with this through programming, but I was curious about it nonetheless. Thanks again, Paul
  3. One of my NXT servos is exhibiting some odd behavior. I had to replace a servo for a different reason and this might be the replacement, but I'm not entirely sure as I didn't mark it as such. In any case, I'm curious if anyone else has seen this and knows the cause. With two servos that act as expected, I can place a single Move block in the program and use any of the duration settings and both servos will run and stop when programmed or run continuously if "Unlimited" is selected. However, when one servo is replaced with the misbehaving one, regardless of the duration setting, the latter servo will run continuously and the good servo will twitch as if it's about to run, but stops immediately. I have to end the program to get the "bad" servo to stop. If I place the Move block inside a Loop set to "Forever," the above behavior will be identical except for one scenario. If I set the Move block duration to "Unlimited," both servos will run and can be controlled by the Loop's "Control" setting, i.e. they will either run continuously or run and stop as set by the loop control setting. Simply using individual "Motor" blocks to control the servos does not solve the problem. There are good and bad programming scenarios with those as well with regard to the bad servo. The best guess I can come up with is that the bad servo is either not sending or not receiving a feedback signal, maybe both. I did wonder, though, if these servos have any firmware in them that might behave differently depending on when they were made. This isn't a fatal flaw as I can use the servo, but I am curious what might be going on. Thanks, Paul