Jump to content


  • Content Count

  • Joined

  • Last visited

About Yuri

  • Rank
  • Birthday 12/26/1990

Profile Information

  • Gender
  • Location
    Ann Arbor, MI
  1. Yuri

    Master/Slave? GUI?

    Ahahaha I feel so stupid! Thanks! I ended up getting it to work, and I'm now able to understand UART a lot more. I'm definitely feeling more confident with my board thanks to you guys!
  2. Yuri

    Master/Slave? GUI?

    Yessir! I never actually considered that. I assumed if I had the "IM" echo function enabled it would be alright. But I'll alter that in my time here today. Thank you!
  3. Yuri

    Master/Slave? GUI?

    I used the example program you and TI have provided me.
  4. Yuri

    Master/Slave? GUI?

    I'm sorry I don't quite understand why these simple things are so difficult for me! I zipped up the C# program, I tried to make it as straightforward as possible. GUIRound3.zip
  5. Yuri

    Master/Slave? GUI?

    I have been able to get things to run through PuTTY for about a week now. I spent a good deal of time building a crude system in PuTTY to scroll through some options, etc. But to get things to work in a simple GUI seems to be different. I have built a simple GUI in C# with a serial port. It connects and such. I just can't seem to send and receive text. I want to get a simple send/receive text going for now, and go from there. So I have a send box, I type "Hello" and click send, then my receive box will print "Hello" But do I have to modify simple UART code for the MSP430? I a
  6. Hello! I'm back with another sad question. Simple question though. Now that I seem to have a working UART interface, I have been wondering how to connect a launchpad to a GUI. I would like to write this in C#. I have the concept that it would be serial communication, so the launchpad would be the "Master" and the outside program would be considered the "Slave" right? How does one go about something as simple as this? I know how to simply create a serial port program in c#, I just seem to not understand how to set the LaunchPad up as the master. Does that make sense? It seem
  7. Thanks for the information! I will try to figure this out!
  8. I get an echo, I just do not get a vibration. What I mean is. This will work : for(; { __bis_SR_register(GIE); write(character); character = 0x00; Haptics_SendWaveform(erm_rampup); } The board will vibrate continuously because it's a neverending loop. But the erm will rotate. BUT for(; { __bis_SR_register(GIE); write(character); if(character == 'a') { printf(" Successfully pressed 'a'! \r\n"); Haptics_SendWaveform(erm_rampup); } character = 0x00; } Will NOT work. It will output " Su
  9. New issue! This time nothing to do with UART, surprisingly! So I tried to make a switch statement that would switch to certain vibration profiles, the vibration profiles will not engage. But if the haptic feedback is outside of the if or switch statements, they work just fine. I've confirmed that they work in my current main. It also is confirmed to work INSIDE of the while loop. My switch statement works, I had it output a string which would engage just fine. Just the haptic feedback is lost. I put the entire project up on Github if anyone is willing to take a look. I
  10. That was exactly it! Thank you very much! I will now hopefully make some progress on this and report back if I hit any more roadblocks. I appreciate everyone's patience with me!
  11. I just made a gist for my main. https://gist.github.com/CaptainSay/5713849 This is the only bit of code giving me issues, and the one tied to the interrupts.
  12. Thank you for the advice, but when I run those I do not believe the interrupts are working in the same fashion. Maybe it's a loop issue. If I enable interrupts, I now get a continuous stream of the character I type. They rapidly fill the prompt. My code for writing a character is : #pragma vector=USCIAB0RX_VECTOR __interrupt void USCI0RX_ISR(void) { UCA0TXBUF = UCA0RXBUF; character = UCA0RXBUF; __bic_SR_register(GIE); } void write(char ch) { while ((UCA0STAT & UCBUSY)); { UCA0TXBUF = ch; } } I apologize for the inconvenience!
  13. New Question No matter what UART I seem to attempt to use I have an issue shortly after getting a working I/O system: I cannot run the haptic effects in low power mode. Makes sense as the haptics require physically engaging an actuator. BUT LPM seems to be necessary for interrupts, which make the output work. Is there any way to switch back and forth? Or a way to go through hardware UART without the interrupts?
  14. New issue to anyone that can help! I have decided to the Hardware UART route, and looked through the examples that exist for that. I do have a working board now, that can simultaneously accept input. EXCEPT : I don't know how to store and analyze input. I see the example goes outside of the main, and echoes what is typed, but where is it exactly stored? And how can I retrieve it? #include "msp430g2553.h" #include "CapTouchBoard.h" #include "Actuator_Waveforms.h" #include "BinaryModes.h" #define SCROLL 250 extern struct Element* modePtr; // Pointer to current mode button press
  15. Thank you for the advice! I actually just discovered hardware UART, and so far the code for that seems significantly more simple, though there is much less support for it it seems. But I will give your advice a try and report back in a bit. Thank you again! ~Yuri
  • Create New...