Jump to content
43oh

nemetila

Members
  • Content Count

    45
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by nemetila

  1. I discovered a very strange behaviour of my BMP180 module. When it gets direct sunlight it immediately (within 1sec) reports higher altitude, and the reported temperature is also continuously increasing (the device becomes hot in reality, too). When I put it in the shadow(indirect sunlight) or cover it with a paper, it immediately sends the correct altitude, and the temperature starts decreasing. In the house (artificial light) or in darkness it works correctly.

    Example:

    altitude in shadow: 106m / temp: 18

  2. There are 3.3V and 5V type LCDs.

    If you use 5V type LCD, the LCD LED forward voltage might be higher than 4V (for example 4.1V).

    This is higher than your LaunchPad Vcc voltage (3.4V). I think It wont work unless you get 5V from the LauncPad or from an external supply.

     

     

    Backlight on/off (with 3.3V LCD)

    an example:

    • connect: LCD_VLED  --> Vcc
    • connect: LCD_VLSS ---> current limiter resistor pin(1)
    • connect: current limiter resistor pin(2) --> N_MOSFET(logic level type) drain
    • connect: N_MOSFET(logic level type) source --> Gnd
    • connect: N_MOSFET(logic level type) gate --> any MSP430 I/O pin

    This solution might be improved with additional resistors.

  3. post-30759-0-51672400-1401227405_thumb.jpg

     

    There is a promotion on the new Elecrow website.

    There are 3 ways ($6) to join in this activity for new members of Elecrow website and

    2 ways ($4) for customers who already have Elecrow account.

     

    • register as a new customer in Elecrow; (+$2)
    • share their blog to one of the social media such as facebook, twitter, or google+; (+$2)
    • share their blog to a discuss platform such as the forum; (+$2)

    Here are the details: link.

     

     

    The above promotion is limited in time (31 May 2014), but they have a not time limited promotion too:

    • write a review ($0.2) or/and upload images ($0.3) or/and videos ($0.5) of your order (if you do all of them, they will give the highest one, for example: if you write a review and upload an image in the same time, you will get 30 points instead of 20+30 points).

    post-30759-0-05195200-1401227407_thumb.jpg

  4. The micro USB's ID pin has no electronic function, check which pin was ripped off. 

    The other four pins (VG, D-,D+, G) are required and there are two big GND pins for keeping the connector mechanically.

     

    I have teared off twice my Stellaris LP debug USB connector, fortunately without any pad being damaged. I could resolder it carefully with

    a soldering iron, some desoldering copper and some flux, despite I'm not really good with hands. I took photos using my camera with macro zoom for positioning the connector well and for checking my soldering before i connected the repaired board to the PC.

  5. I have ported a readRegister() function from ENERGIA.

     

    At 16MHz SPI clock it gives incorrent results, altough RobG's wrinting functions work corretly at this speed (LCD displays as it should).

    At 8MHz reading works correcty too.

    unsigned char readRegister(unsigned char Addr, unsigned char xParameter)
    {
    	//ENERGIA
        //INT8U data=0;
        //sendCMD(0xd9);                                                      // ext command
        //WRITE_DATA(0x10+xParameter);                                        // 0x11 is the first Parameter
        //TFT_DC_LOW;
        //TFT_CS_LOW;
        //SPI.transfer(Addr);
        //TFT_DC_HIGH;
        //data = SPI.transfer(0);
        //TFT_CS_HIGH;
        //return data;
    
    	unsigned char data = 0;
    	writeCommand(0xd9);
    	writeData(0x10+xParameter);
    	LCD_DC_LO;
    	LCD_SELECT;
    	UCB0TXBUF = Addr;
    	while (UCB0STAT & UCBUSY);
    	LCD_DC_HI;
    	UCB0TXBUF = 0;
    	while (UCBxSTAT & UCBUSY);
    	data = UCB0RXBUF;
    	LCD_DESELECT;
    
    	return data;
    }
    

    Reading ILI9341's register 0xD3 ("Read ID4") must be the value of "0x09341"

        for( i=0; i<3; i++ )
        {
            rx_data[i]=readRegister(0xd3,i+1);
    
        }
    
  6. I'm testing your code on Tiva C LaunchPad using the same type of LCD module.

    It displays perfectly with text.ino example, but it sends incorrect LCD_ID to my PC via UART/USB.

     

    The result i get:

    Read TFT ID failed, ID should be 0x09341, but read ID = 0x000

    or 


    Read TFT ID failed, ID should be 0x09341, but read ID = 0xFFFFFF

     

    I use the same pin fonfig as you used.

    Did your module send the correct ID?

     

     

    Thanks in advance.

  7. Probably it's a noob question:

     

    Why is not necessary to use current limiting resistors(R2..R5) to limit the LEDs' currents?

    (Your circuit uses shorts by default)

    I know it works, because i have test it, but the TM022HDH26 datasheet shows the maximum forward current is 25mA@3.4V for each LED,

    and the MSP-EXP430G2 LaunchPad's Vcc can be slightly above 3.4V

     

    Thanks in advance

  8. Hi guys. Here are my first experiences with MSP-EXP430F5529LP:

     

    1.

    I tested it only as an external programmer to program an MSP430G2553 (located in  MSP-EXP430G2 launchpad) with  CCS5.5.

     

    I connected the two boards with: GND, VCC(3V3), SBW_RST, SBW_TST wires. 

     

    At the beginnig CCS warned me that the eZ-FET lite emulator firmware was outdated and need to be updated. I pressed the update button. The update took less than one minute. After the update CCS programmed the MSPG2553 with the eZ-FET lite emulator. It seemed that the uploading was faster than with the emulator of the MSP-EXP430G2 launchpad.

     

     

    2.

    I tried to use FET-Pro430 Lite (latest verison I found: 3.10) to read the memory content of the MSP430G2553 with the eZ-FET lite emulator. It didn't work me with default settings. (I think the msp430.dll comes with the FET-Pro430 Lite software was too old). In the "Setup->Connection/Device Reset" menu I browsed path of a fresh (3.3.1.4) msp430.dll. (the eZ-FET lite requires 3.3.0.6 or higher). Then everything was OK. Reading the memory content took 1.9 sec.

     

    I did the same with the emulator of the MSP-EXP430G2 launchpad: reading took 5.9 sec.

  9. Just a simple question which pop into my mind. Since we are using the internal temperature sensor here, wouldn't that display the core temperature. Then most probably it will show a higher value right? 

     You are right. The core temperature is higher than the ambient temperature because of the power consumption of the chip. That's why I used the hibernation module: in most of time the MCU is in hibernation.

  10. It was new to me.

     

    More info on ti.com :http://www.ti.com/tool/MSP-EXP430F5529LP

    and on wiki.ti: http://processors.wiki.ti.com/index.php/MSP430F5529_LaunchPad

     

    Price: $12.99(US$) 

     

    post-30759-0-58606300-1378912210_thumb.png

     

    Features

    • USB 2.0-enabled MSP430F5529 16-bit MCU
    • Up to 25 MHz
    • 128KB Flash and 8KB RAM
    • 12 Bit SAR ADC
    • Various USB device class examples and libraries available (CDC, HID, MSC)
    • eZ-FET lite: Open source onboard debugger with application UART
    • One USB connection for emulator and target via the use of an onboard USB hub
    • USB as power source: 5V and 3.3V through a high efficiency DC/DC converter
    • 40 pin LaunchPad standard leveraging the BoosterPack ecosystem 
  11.  

     
    #20 identifier "GPIO_PA0_U0RX" is undefined main.c /I2C line 120 C/C++ Problem
     
    #20 identifier "GPIO_PA1_U0TX" is undefined main.c /I2C line 121 C/C++ Problem
     
    i m getting this error in ccs compiler pleas help

     

    You need to add or link the following  files to your project. You can find them in the utils folder of Stellarisware. Right click on your project and click add files.

    - Uartstdio.c

     

    Or use this methode:

    Install CCS 5 and StellarisWare.

    Download and extract the Stellaris_v01.zip file, then start CCS and use "Project"->"Import existing CCS Eclipse Project".

    Browse the extracted "Stellaris_v01" directory and click "Finish". Build Project then debug.

  12. Thank you Spirilis your awesome work.  :thumbup:

     

    I tested your code (msprf24) with my MSP430 Launchpad (MSP430G2553) and my Stellaris LaunchPad (Enrf24). It works great.

    I have a MSP-EXP430FR5739 too, so I added support for it (msprf24). Only RF24_SPI_DRIVER_USCI_B is supported now.

    I used MSP-EXP430FR5739@8MHz as PTX and MSP430G2553@16MHz as PRX. It works. Here is my modified msprf24.c file.

     

    I read somewhere that Auto ACK doesn't work at 250kBs air data rate. I tested your code at 250kBs and 1MBs and in both cases the auto ACK worked well (ch = 0, max TX power). I have this cheap modules from eBay: http://www.ebay.com/itm/2PCS-Arduino-NRF24L01-2-4GHz-Wireless-Transceiver-Module-New-/170819064718?pt=LH_DefaultDomain_0&hash=item27c59c138e

     

    At 1MBs the distance limit is about 40feet with 1-2 walls.

    I will test the limit at 250kBs too.

     

    -------------------------------------------------------------------------------------------------------------------------------------------

    Update1:

    I have done the distance limit test at 250 kBs. The limit is exactly the same as it was at 1MBs. I dont know why.

     

    ------------------------------------------------------------------------------------------------------------------------------------------

    Update2:

    I used TA0 on PTX to measure T_ESB(Time Enhanced Shock-Burst

  13. Hi!

     

    post-30759-0-34009800-1370306200_thumb.png

     

    I am developing a simple accelerometer with the MSP-EXP430FR5739. This board is populated with a 3-axis accelerometer: ADXL330. No additional HW is needed.

     

    The MCU program does:

    • ADC:
      • Samples data from CH_0 to CH_14 in Repeat-Sequence-of-Channels Mode
      • Sample Rate: ~ 20 Hz/Channel
      • DMA
    • UART:
      • HW UART (TX only) with 9600 baud. This 9600 baud is limited by the emulator circuit.
      • UART TX data1 = ADC_CH_12 = ACC_X;   sample "622-X"
      • UART TX data2 = ADC_CH_13 = ACC_Y;   sample "509-Y"
      • UART TX data3 = ADC_CH_14 = ACC_Z;   sample "511-Z"
    • LEDs: LED_TX and LED_ADC

     

    The PC application does:

    • Calculate the 3 acceleration components (g_x, g_y, g_z) from the ADC data and the CALIBRATION data
    • Calculate the magnitude of G; |G| = sqrt(g_x^2 + g_y^2 + g_z^2);
    • Displays data

    CALIBRATION data must be enter by the user once at the beginning. The user has to rotate slowly the board in every 3 direction (and opposite) to find the maximum (+1g) and the minimum (-1g) ADC values of the 3 axis. Enter this 3*2=6 ADC data to the 6 white textboxes. If the CALIBRATION data are correct then |G| must be 1.00 (static acceleration of gravity).

    .

     

    The TX data can be viewed with putty too:

    post-30759-0-63157800-1370308750_thumb.png

     

     

    Requirements:

     

    The CPU usage may be high when PC application receives data. I will try to reduce this in the next version.

×
×
  • Create New...