Help with 2010 Accelerometer & I2C

[wt200999]

Yeah the address given in the Sensor Guide says 0x3A, and I figure its all in 8bit for the WPI Function, so the 0x1D wouldn't work with that but 0x3A would?? I really don't know I2C or WPI's implementation of it, so I don't really know. I'm going to keep playing with it tonight.

I also just found the register map, didn't see it in the datasheet when I worked on it last, don' know how I missed it.

The biggest issue I am having now is whenever I call the read or write function the robot freezes up, and my console output shows nothing. This is both when I try to perform a read or a write....

[slavik262]

Any luck so far? It would be awesome if you got this working.

[jhersh]

Originally Posted by wt200999

The biggest issue I am having now is whenever I call the read or write function the robot freezes up, and my console output shows nothing. This is both when I try to perform a read or a write....

I did find an issue with the initial release of the I2C for this year. The bug was introduced since last year. See details here: http://firstforge.wpi.edu/sf/go/artf1144

This bug would prevent the accelerometer from working.

Yippeee!! everything is finally working....We re imaged the Crio, made sure 'ALL' the updates were applied to the driver station and the development laptop, compiled then downloaded the BuiltinDefaultCode.out file.

Then we added Joe's accelerometer code and fixed the I2C.cpp file. and all still worked.

We had some problems with the IterativeDemo but I we'll revisit that later. The BuiltinDefaultcode is what we will base our robot code on.

Thanks to all especially Joe Hersh for all the info and his patience..They don't pay you enough...Every one should send Joe a starbucks gift card so he can buy enough coffee to keep him awake when he sending those responses at 3 AM..

Brian C

[JDM]

Originally Posted by bcieslak

Yippeee!! everything is finally working....We re imaged the Crio, made sure 'ALL' the updates were applied to the driver station and the development laptop, compiled then downloaded the BuiltinDefaultCode.out file.

Then we added Joe's accelerometer code and fixed the I2C.cpp file. and all still worked.

Would you mind posting all the code that got it working for you? Hopefully that should speed it up for everyone.

Thanks

[jhersh]

Originally Posted by JDM

Would you mind posting all the code that got it working for you? Hopefully that should speed it up for everyone.

Here's the discussion where I posted the initial support: http://decibel.ni.com/content/thread/5634

It will be officially included and supported in the next C++ update.

[nabioullinr]

For some reason I keep receiving 0.0 from GetAcceleration(); am I instantiating the accelerometer correctly?:
ADXL345_I2C(4, ADXL345::kRange_2G)

(assuming the digital sidecar is connected to slot 4)

[nabioullinr]

We attached an oscilloscope to the bus and noticed that the data returned from the slave accelerometer is 0 for all three transactions (x, y, z); could it be attributed to some sort of a power saving feature which is not disabled?

[jhersh]

Originally Posted by nabioullinr

We attached an oscilloscope to the bus and noticed that the data returned from the slave accelerometer is 0 for all three transactions (x, y, z); could it be attributed to some sort of a power saving feature which is not disabled?

I'm guessing you didn't fix WPILib... http://www.chiefdelphi.com/forums/sh...5&postcount=12

If you fix the I2C library it should start working for you.

[nabioullinr]

How would I patch wpilib? I could not find anything useful (besides the description of the bug).

[jhersh]

Originally Posted by nabioullinr

How would I patch wpilib? I could not find anything useful (besides the description of the bug).

Download the source code, change the logical OR to a bitwise OR, build the library, run the Scripts/updateBuiltInLibrary.cmd file to install the compiled library, rebuild your project.

-Joe

[Shinigami2057]

Will this patch be in a team update soon? It's not good that teams already have gone this long with broken support for something in the KoP...

[jhersh]

Originally Posted by Shinigami2057

Will this patch be in a team update soon?

I'm not sure... I have no control over release schedules.

Originally Posted by Shinigami2057

It's not good that teams already have gone this long with broken support for something in the KoP...

I know... that's why I've tried to provide timely workarounds, fixes, problem notifications, feature implementation examples, and support the best I can so that teams will not be held up by the release schedules. It's not ideal to need to patch these things manually, but it's also not good to force every team to install and keep track of 10+ updates in various languages that would all be released independently and out of phase with each other. Many teams can't keep up with the one update released at kickoff.

-Joe

[tdidi]

Originally Posted by jhersh

Download the source code, change the logical OR to a bitwise OR, build the library, run the Scripts/updateBuiltInLibrary.cmd file to install the compiled library, rebuild your project.

-Joe

I don't get it. I follow those instructions exactly, and it removes the WPILib from Windriver completely when I run the updateBuiltInLibrary.cmd.

I get the "no such file or directory" error.

[jhersh]

Originally Posted by tdidi

I don't get it. I follow those instructions exactly, and it removes the WPILib from Windriver completely when I run the updateBuiltInLibrary.cmd.

I get the "no such file or directory" error.

That probably means you didn't build the library successfully. Make sure you build the debug version, since that's what the script copies.

What file or directory exactly does it fail on?

-Joe