• Content count

  • Joined

  • Last visited

  • Days Won


B@tto last won the day on April 12

B@tto had the most liked content!

About B@tto

  • Rank
    Level 2

Recent Profile Visitors

123 profile views
  1. Be carreful, I recently noticed some differences between TivaC pinout diagram and reality. I did not take the time to push this issue on Github but I will do it as soon as possible.
  2. In addition, I succesfully used this one : http://cactus.io/hookups/sensors/barometric/bme280/hookup-arduino-to-bme280-barometric-pressure-sensor I just made some modifications to get sensor working in low power mode.
  3. There is a dedicated channel on ADC with VCC/2. You have to select 2,5v analog ref and select internal channel : analogRead(128 + 11) (if I remember well) 128 + X force energia to select the specific hardware channel X on analog multiplexer without mapping.
  4. Hi, How do you know that the SIM900 send anything ? Apparently you are using the same port for SIM900 and debug so ...
  5. The "normal" process is to make a push on Energia's github, what I did not do (I was having hard times when this troubles came to me, and I'm not a good user of github at all, so I clearly didn't have the time to push this mods).
  6. Hi, Last year I add a lot of troubles with i2c in Energia. I solved them but I don't know if Energia team included my corrections :
  7. Sorry but you have to see something in your serial monitor as you use the function ShowSerialData(), so after each command you should see the module response in the serial monitor.
  8. Hi, What do you get in your serial monitor ?
  9. 32 seconds ? Or exactly 32.768 s ? I understand you're frustration about Wire.h in Energia : I posted several topic about problems with it, and not little ones sometimes ... setModule() just select the i2c port to use. The main reason is that shield pinout was modified since the launchpad creation and TI decided to standardise i2c position. But as for example on MSPG2553 there is only one i2c hardware port, they emulated one on the right pins to be able to use new launchpads shields. In Energia the main problem is that pinout diagram are not clear, or updated, or false. For example, G2 launchpad are not good : i2c module #1 is simply not mentionned, but in stellaris it's ok : http://energia.nu/Guide_StellarisLaunchPad.html but there is an error on Serial4 ... The best way to answer all this questions is to look at the pins_energia.h file of the board used. If I take the one of G2 I found : static const uint8_t SS = 8; /* P2.0 */ static const uint8_t SCK = 7; /* P1.5 */ static const uint8_t MOSI = 15; /* P1.7 */ static const uint8_t MISO = 14; /* P1.6 */ static const uint8_t TWISCL1 = 9; /* P2.1 SW I2C */ static const uint8_t TWISDA1 = 10; /* P2.2 SW I2C */ static const uint8_t TWISDA0 = 15; /* P1.7 */ static const uint8_t TWISCL0 = 14; /* P1.6 */ static const uint8_t DEBUG_UARTRXD = 3; /* Receive Data (RXD) at P1.1 */ static const uint8_t DEBUG_UARTTXD = 4; /* Transmit Data (TXD) at P1.2 */ and later : #define DEFAULT_I2C -1 /* indicates SW I2C on pseudo module 1 */ So if you want to use HW i2c (so use pin 1.6 and 1.7), you have to use Wire.setModule(0) before calling Wire.begin(). Largelly speaking, in Energia I always use this command to be sure that i'm using the expected port. And in my library I always put this command with a preprocessor command to check if I'm working in Energia environnement and get my library compatible with Arduino
  10. I know but as he's reinventing the wheel ...
  11. Hi, Most of MSP430 cannot do open collector mode. The reason is simple : they use push-pull IN/OUT circuit, so the same signal can generate high powered output (sourcing and sinking). In open collector mode, you just need a transistor to pull down the data line, the high state is generated by a pull up resistor, but it's not possible as I explained, there are two transistor (push-pull) drived by the same signal. So the pull up resistor is completely useless as high state will be generated by the high state of the output. Open drain is very useful because every ic which is able to pull low the data line is able to speak. But everything is not lost : if you play between output and input modes it's possible, and it's already used by energia (it depends on the Wire.setModule() you called), look here : https://github.com/energia/msp430-lg-core/blob/master/libraries/Wire/utility/twi_sw.c
  12. Hi, You can get Fona module with SIM808 : the GNSS is integrated so you only need one UART to manage GSM and GNSS.
  13. Ok so, I updated core to 3.7 and I saw that EasyLink was updated too. It's clearly better, maybe 200m with a building between LPs. Notice that I check the RSSI nothing seems strange (-20 dbm distance = 1 m, ~-110 dbm distance = 200m)
  14. As I understand, TX power is managed in the config. But as I had a doubt about this, I implemented setTxPwr() in energia Easylink library and set it to 12 dbm. It changed nothing
  15. Hi, I received my CC1310 LPs and started to play with them. After a correction (https://github.com/energia/cc13xx-core/issues/2) it was OK and I wanted to see the maximal distance I can let between the two LPs. But I am pretty disapointed : of course I'm in a urban zone (but not dense at all, I let a LP in front of a windows and walked throught the parking in front of it) and CC1310 LP antenna are PCB type so I'm conscious that the environnement and the hardware are not optimal at all, but max range I got was ~100m. I used easylink long range mode of course. Considering that in optimal conditions, TI announced 20 km range, the gap seems heavy. Is it normal ? Regards