Jump to content

LiviuM

Members
  • Content Count

    91
  • Joined

  • Last visited

  • Days Won

    13

Everything posted by LiviuM

  1. LE I've read the examples coming with PetitFS and they aren't using the mode specifier neither. No idea why it doesn't work for you.
  2. Hi, nice to see that making the connection properly bring it to work. Carefully reading the replies you receive may even accelerate the success. For your last problem - writing without writing - maybe you should open the file in the correct mode. In this case the mode should be FA_WRITE. Try to replace with rc = FatFs.open("T_WRITE.TXT", FA_WRITE); or rc = FatFs.open("T_WRITE.TXT", FA_WRITE | FA_READ); for read & write access.
  3. MISO should be connected with MISO, MOSI with MOSI, not crossed. MISO means Master In Slave Out, and MOSI means Master Out Slave In. Master & slave are always the same, no crossing is needed.
  4. Have you tried with the last version of the library, mentioned on the https://hmario.home.xs4all.nl/arduino/LiquidCrystal_I2C/?
  5. Have you read this post and the following ones (with a possible solution)?
  6. As long you receive "can't open port" messages, I see two possibilities: - wrong port - bad hardware.
  7. Wrong com-port choose?
  8. From the description of the error codes (pff.h), pff.h /* File function return code (FRESULT) */ typedef enum { FR_OK = 0, /* 0 */ FR_DISK_ERR, /* 1 */ FR_NOT_READY, /* 2 */ FR_NO_FILE, /* 3 */ FR_NOT_OPENED, /* 4 */ FR_NOT_ENABLED, /* 5 */ FR_NO_FILESYSTEM /* 6 */ } FRESULT; I understand that rc=3 means the file you are trying to open doesn't exist and that rc=6 means bad connection. In the same time, reading one of the original posts: I understand that the files should exist before trying to access them. With these considerations, I suppose your first set-up (the one with rc=3) is correct and the file you try to access doesn't exist. Cheers, Liviu PS I'll PM you my bank data.
  9. Hi, for the projects I need to access from multiple places (and needing some privacy) I've configured a small git server and put gogit/gogs *) on top of it. Because the core is git, I can use it from command line and gogit gives me the possibility to use it in a way similar to github and (the reason I use it) allows me to define "virtual users" - I can allow other people to access the private repositories without sharing my (main) credentials. I have luck with a good hosting offering all needed tools. Cheers, Liviu *) I suppose any "interface" will do the same, I've used gogs because I found a tutorial (in German) about the installation on my server.
  10. In the post I've linked above the solution was to replace the twi.c & twi_sw.c with new ones, found in the e2e forum. Have you also replaced them?
  11. The if-else construct in your loop is at least strange: if(!flag) { Serial.println("Failed to read from DHT"); else{ Serial.print("RH% \t");
  12. Hi, have you searched the forum for similar topics with i2c problems? I know at least one proposing a solution by changing the twi.c & twi.h files.
  13. Hi @@brelliott18, There are some known problems with i2c on 2553 Launchpads, mentioned in various posts over this forum. One of them is mentioned in http://forum.43oh.com/topic/2641-i2c-lcd/page-2#entry75927; in this post is also a link to a solution http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/529036/1924562#1924562 Have you already seen this posts? Have you tried the solutions presented in them? Regards, Liviu
  14. Hello, these days I was trying to use an array of servos, something like: #include <Servo.h> #define IOS_NR 5 byte myIos[IOS_NR] = {1,2,3,4,5}; Servo myServos[IOS_NR]; boolean bServoOut[] = {true false, false, true, false}; void setup(){ for(i=0; i < IOS_NR; i++){ if(bServoOut[i]){ myServos[i].atatch(myIos[i]); } } } void loop(){ // do some things if(bServoOut[k]){ myServos[k].write(servoValue); } // do other things } but the servos behaved totally other than expected. Digging through the Servo library, I've found some (in my opinion) wrong used indexes and (again, in my opinion) fixed them. After the fix my two servos behave as expected. I'm attaching the changed files (actually only the .cpp file is changed), maybe someone can test them thoroughly than I, or even use them. Best regards, Liviu PS I've renamed the files after the project I'm using them in. RNServo.zip
  15. It is the reason I'm always using brackets around while blocks. My code looks maybe ugly, but I avoid such "surprises".
  16. LE Found it, the pins default to inputs:
  17. Where are you defining the input (counter) pin?
  18. I've used some (4) WS2812B powered at 3.3 V and they worked OK. Never used TM1809, though.
  19. Hi, have you seen the @@Fmilburn's topic about controlling WS2812B LEDs using MSP430G2553 LP and SPI?
  20. Hi Curtis, tried your code with a Launchpad alone (and SCL & SDA made inputs + PULLUP) and the result is (as expected): Starting... SDA pin - 15 - 1 SCL pin - 14 - 1 The two J5 jumpers are OFF.
  21. Hi Curtis, Try without the sensor and see how the lines are staying.
  22. Hi Curtis, yes, exactly in this way I was thinking it should work. I'll would just say: instead of Best regards, Liviu
×
×
  • Create New...