|
Paxton, IL | I learned a lot more today on my tile plow control issue posted previously here:
https://talk.newagtalk.com/forums/thread-view.asp?tid=1219431&mid=11...
Today when I started the display, everything appeared to be working correctly and my IMD sensor status was being reported as “ok”. I took it out to the field and tried another dry run. This time everything worked very well and the plow maintained grade like it should.
I fine tuned a couple settings for a while to get performance dialed in a little better and then surveyed and started a fresh run. As I was putting the plow in the ground I got an error (pictured below) saying “IMU sensor saturation”. I stopped and pulled up the diagnostics page and saw that now the sensor status was back to “bad 0x38”. I went ahead and tested what it would do when I tried to run in automatic control and the plow started wildly overcorrecting exactly like it did yesterday. So that clearly appears to be my problem. When I shut down and restarted the display, everything went back to working fine.
So the big question is what is causing the IMU sensor saturation error? A google search suggests that a sudden impact and extreme motion could cause this when the sensors experience an event out of their range. There are certainly some bumps and rough ground here and there, but I wouldn’t consider anything to be a large shock that’s big enough to cause an issue? I don’t recall ever having a problem like this before, so guessing it’s something that now throws a fault in newer firmware versions?
 (IMG_5806 (full).jpeg)
Attachments
----------------
 IMG_5806 (full).jpeg (116KB - 2 downloads)
| |
|
Trimble IMU sensor saturation - update to post on tile plow over correcting
