Search the Community

Showing results for tags 'accelerometer'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 6 results

  1. Hi With the waveforms tool is it possible using python scripting in the Waveforms platform to do the following ?? Use the Digilent Analogue discovery 2 - Attach a device like a PMOD device eg accelerometer https://store.digilentinc.com/pmod-acl-3-axis-accelerometer/ using the Analogue discovery 2 ability to chat SPI & IC2 - pmod DEVICES SUPPORT 12-pin Pmod connector with SPI interface and 2×4-pin I²C interface - Then using the read information from the PMOD device treat it like an extra oscilloscope channel . Either as a Analog channel or Digital channel depending on the the signal type acquired from the PMOD device. This is possible with Labview but that would also require a lot of code writing. If this is possible this is outstanding feature when considering all the available PMOD devices available from the list https://store.digilentinc.com/by-function/input/ This would be a real product enhancement for Digilent and the Analog Discovery and help sell the AD2 in to many new places . Best wishes Simon
  2. It seems like I have a problem with understanding the values I am getting from the accelerometer and gyroscope. First of all, it is stated that the IMU is using a left-handed coordinate system where Z is directing upwards. (as mentioned here :www.st.com/web/en/resource/technical/document/datasheet/DM00103319.pdf?_ga=2.91175770.1596273909.1572880735-388278844.1572880735) page number 10 However, I get +1 in the Z direction when the board is standing still ? I thought I should get -1 as the accleration is in the negative direction ? I thought that the sensor may be flipped upside down ( so one axis will be flipped while the other stays the same) but both of them are still flipped which does not make sense ? The gyroscope are following the (right hand rule ) even for a left coordinate system ? any help would be appreciated. Thanks !
  3. Hello, I am getting successfully data from an accelerometer and I then I want to calculate the frequency of a vibrating object where the accelerometer is placed at. As you can observe in the attached VI after I obtain the accelerometer measurements I use data queue function in order to collect a certain amount of data(200), in order to have enough samples for my FFT. Then I use build waveform function and at the end filter and spectral measurements vi. But unfortunately I do not thing that I get the frequency I want.And that means not only that the x axis in waveform graph is not correct but in general when I vibrate the object in certain frequencies the spectrum does not show something close to them. Can anyone help me? Thank you FFT_spectrum.vi
  4. Hello, I am trying to get x,y,z axis data from the accelerometer adxl345 using linx in labview. I have managed to do that with I2C protocol, but I want to do it also with SPI protocol in order to achieve greater sampling rate. I have read the adxl345 datasheet but I struggle figuring out to which exact registers I must write so that I can read the datax,y,z registers. I attach my -so far now working- program below, thank you in advance. adxl345spi.vi
  5. Hello. I wish to write assembly code for ADXL362 accelerometer on Nexys4 DDR and compile for use with Picoblaze softcore processor. Are there any assembly routines that I can use to establish communication with the accelerometer please? Any links to code would be appreciated.
  6. Note To Staff There is no need for help here; I just wanted to share this with others, since it was useful to me. As far as I'm concerned (have power to say?), this code, text, graphics, and attachments are all public domain (preferably with attribution). If there is a specific area or protocol for these sorts of things, I haven't seen it. This post and contents could be stickied, moved, and otherwise used as the powers that be see fit. If there is something wrong, something that needs changed, or something the needs clarified, feel free. /Note To Staff Hello all. I have a small gift for anyone that wants it. The following is working javascript for GY-521 breakout boards, which holds the venerable InvenSense MPU-6050 6 axis IMU chips. // -UNOFFICIAL SCRIPT- -AS IS- -NOT ENDORSED BY DIGILENT- -USE AT OWN RISK- // Author: Charles Scoville // // GY-521 breakout board: InvenSense MPU-6050 i2C Gryo + accelerometer // Set clock = 400kHz: Rate up to 400Hz (more may work): Itterations ~1k const adr = 0x68; // 0x69 is an alternate address. function initialize(){ if(Clear()!=true) return "I2C bus error. Check the pull-ups."; if(Write(adr)!=true) return "Device NAK"; //if(Read(adr, 0x75, 1) != 0x68) return "Device ID mismatch"; *FIXME* Read() bug? Does NOT actually return 0x68 if(Write(adr, 0x6B, 0x03)!=0) return "Communication error"; // REG: PWR_MGMT_1 (Z gyro as clock source) if(Write(adr, 0x23, 0x78)!=0) return "Communication error"; // REG: FIFO_EN (FIFO only for Gyros and accelerometer) if(Write(adr, 0x6A, 0x45)!=0) return "Communication error"; // REG: USER_CTRL (Reset FIFO and signal paths for all sensors) if(!FileWriteLine("~/Desktop/default.csv", ["temp", "ACCEL_XOUT", "ACCEL_YOUT", "ACCEL_ZOUT", "GYRO_XOUT", "GYRO_YOUT", "GYRO_ZOUT"])) return "File write failed - init"; return true; } function loop(){ var rg = Read(adr, 0x3B, 14); // DATA var xa = ((rg[0]<<24) | (rg[1]<<16)) /256/256; var ya = ((rg[2]<<24) | (rg[3]<<16)) /256/256; var za = ((rg[4]<<24) | (rg[5]<<16)) /256/256; // NOTE: REG 0x23 must be written as 0xF8 for temp to be buffered var tmp = ((rg[6]<<24) | (rg[7]<<16)) /256/256/340 + 36.53; //temp (deg C) //tmp = tmp * 1.8 + 32; //temp (deg F) var xg = ((rg[8]<<24) | (rg[9]<<16)) /256/256; var yg = ((rg[10]<<24) | (rg[11]<<16)) /256/256; var zg = ((rg[12]<<24) | (rg[13]<<16)) /256/256; if(!FileAppendLine("~/Desktop/default.csv", [tmp, xa, ya, za, xg, yg, zg])) return "File write failed - loop"; return true; } function finish(){ return "done"; } This script is to be used in the "protocol>i2c>sensor" section of the WaveForms application. I have only run this on the Electronics Explorer, I have no idea if it even applies to anything else. The results when run (with a GY-521 attached, of course!) are a CSV file on your desktop, just as with the PMOD gyro or accelerator example code it was based on. For this data capture to make much sense, you will most likely want to graph the columns in the resulting file. I did so for the accelerometer and gyrometer as independent groups, as that provides the most informative and expected form for the data. The following are some graphs of a couple of my more interesting captures, as examples. They were made with LibreOffice 6.0 directly from the CSV files. The ods files are also attached. (Embedded malware is thoroughly unlikely, but you still open at your own risk.) This one was just me picking it up and turning it all around. It's a nice shot because it's pretty obvious when I picked it up, and what exactly I did. This one was of me lifting the board up onto one corner, rapidly twisting it back and forth, then just setting it down. This one clearly has more samples too. Anyway, thanks for reading. I hope this post has value to you. MPU-6050 readout1.ods MPU-6050 readout2.ods