Closed slavino closed 4 years ago
With
the position sharing works just not sure if the GPS is obtained from T-Beams. Gut feeling is that paired phone shared own location (form Android sensors GPS/AGPS/WiFi or whatever) and ublox NEO-6M is not working as it should.
I have tried to enable the platformio.ini part
but to get rid of AXP202X power management requires to dive bit deeper into the code not to break any other part of the code.
However to get the battery state I believe I used the approach from https://github.com/tekk/TTGO-T-Beam-Car-Tracker/blob/master/TTGO-T-Beam-Car-Tracker.ino
#define BATTERY_PIN 35 // battery level measurement pin, here is the voltage divider connected
float vBat; // battery voltage
void getBatteryVoltage() {
// we've set 10-bit ADC resolution 2^10=1024 and voltage divider makes it half of maximum readable value (which is 3.3V)
vBat = analogRead(BATTERY_PIN) * 2.0 * (3.3 / 1024.0);
Serial.print("Battery voltage: ");
Serial.print(vBat);
Serial.println("V");
}
hmm - can you try capturing a serial log at a baud rate of 921600? (It looks like you are using 115200, which is not correct) That should make it possible to see the message.
@slavino if you want to check in the change to platformio.ini that would be great. I only disabled it until someone could make it work, which you just did ;-)
@geeksville ok, so first finding
#define GPS_RX_PIN 12
#define GPS_TX_PIN 15
I had to check that with code that worked before on the same ver. 0.7 boards and can confirm now.
The following setting worked fine for build and upload procedure (beforehand needed to modify the configuration.h).
and of course lack of platformio knowledge made me use this "workaround" to save some time build.log runtimeLogFromPuttySerialCOM10.log runtimeLogFromPuttySerialCOM14.log upload.log
Does v07 work as expected now, after merging in these PRs?
For me those worked just fine with local build. I'd give a chance to get a production build from GITHUB asap and start testing.
I do also have a spare GPS module that I could attach to TTOGO Lora32 v2.1, by that my mesh network would consist of 2x T-Beam-0.7 and 1xLora32-v2.1 all equipped with GPS.
I think we should list TBEAM 0.7 as supported (if you build your own rom) in the readme, but given the small number of units out there I'm kinda inclined to not add it as a prebuilt bin for now. ... remaining comment moved to a new bug:
Well, the T-Beam v0.7 device is still being sold so I'd suggest to go for a poll showing global interest on support of boards. Or do you gather that feedback via some analytic feedback from Android App?
(Anonymous data about Android OS version vs. Board type might be an interesting graph. What do you think? Knowing your "customer" needs might move or adjust the future focus.) Polls on feature requests might be an interesting agenda as well :)
ooh - I didn't realize it was still being sold! In that case we should probably add it back to bin/build-all.sh.
We already report radio model to the analytics. Which is a good point. I'll look right now and do a post so people can know approximate usage!
please share your .bin file for tbeam 07v
please share your .bin file for tbeam 07v I believe that waiting for "production level release" is a better option than giving try to any bleeding edge build. I hope @geeksville or anybody else performing the next FW release will include this into the release itself.
PS: If the only frustration point/blocker to build your own FW is Platformio then there is some set of scripts that will execute build and flash your device via USB :)
done - it will be in the next build - in a couple of days. thanks @slavino
TTGO TBeam EU 433
Board version: T22_V07 20180711
GPS : ublox NEO-6M
Last time after flasind 0.7.9 I had to open Arduino IDE and flash some base sketch to make it work and had to rollback to some older release (I think 0.7.8 was last non-crashing for this board).