Support Seeed Tracker-T1000-E

[Dylanliacc]

Support for T1000-E Board and Sensor Integration

Summary

This PR introduces support for the T1000-E board, integrating the T1000xSensor and incorporating various customizations and adaptations specific to the board's features. Below are the detailed changes and additions:

Board Support: T1000-E

• Added support for the T1000-E board: The new configuration files and settings tailored to the T1000-E board have been included, ensuring compatibility and proper functioning with the Meshtastic system.

Sensor Integration: T1000xSensor

• Integrated T1000xSensor: The T1000xSensor has been added to the project, providing enhanced sensor capabilities and ensuring it works seamlessly with the T1000-E board.

ButtonThread Customization

• Macro Definitions for T1000-E: Specific macro definitions have been introduced within the ButtonThread to leverage the unique features of the T1000-E board. These definitions optimize button handling and ensure smooth operation tailored to the T1000-E's hardware.

Customization for LR1110 in LR11x0Interface.cpp

• DIO Pin Configuration: The LR11x0Interface.cpp file has been customized based on the DIO pin configuration of the T1000-E's LORALR1110. These modifications ensure proper communication and functionality of the LR1110 module on the T1000-E board.

GPS Adaptation: AG3335 Sensor

• Adaptation for AG3335 Sensor: The GPS component has been adapted to support the AG3335 sensor, ensuring accurate and reliable GPS data acquisition. This integration improves the overall GPS functionality of the T1000-E board within the Meshtastic system.

Future Plans and Improvements

• Class-based GPS Implementation: In future updates, I plan to implement a dedicated class for the GPS functionality instead of using macro definitions. This will enhance code modularity, readability, and maintainability.

Draft PR and Request for Assistance

This is my first contribution to the Meshtastic project, and I am submitting this as a draft PR. There may be areas that need improvement, and I kindly ask for your patience and understanding as I navigate through this process. Any assistance or feedback from the community would be greatly appreciated to help refine and enhance this implementation.

Thank you for considering this PR and for any help or guidance you can provide.

Best regards,

[CLAassistant]

All committers have signed the CLA.

[lyusupov]

@Dylanliacc

QMA6100P connected via I2C but still under development

Thanks!
Your code contains this:

#define HAS_WIRE 1

#define WIRE_INTERFACES_COUNT 1

// unused pins
#define PIN_WIRE_SDA (0 + 9)  // P0.26
#define PIN_WIRE_SCL (0 + 10) // P0.27

Which one SDA/SCL pair is a true I2C bus for the QMA6100P sensor ?

1. P0.9 and P0.10, or
2. P0.26 and P0.27 ?

[Dylanliacc]

@Dylanliacc

QMA6100P通过 I2C 连接，但仍在开发中

谢谢！您的代码包含以下内容：

#define HAS_WIRE 1

#define WIRE_INTERFACES_COUNT 1

// unused pins
#define PIN_WIRE_SDA (0 + 9)  // P0.26
#define PIN_WIRE_SCL (0 + 10) // P0.27

哪一对 SDA/SCL 是 QMA6100P 传感器的真正 I2C 总线？

1. P0.9 和 P0.10，或
2. P0.26 和 P0.27 ？
   
   
   

Sch here
pins are P0.26 和 P0.27

[fifieldt]

Looks good to me

[geeksville]

Hi @Dylanliacc I received my T1000-E and it looks really great and you've made some great code. bravo. One question (since I won't have time to really work on it until next week): It beeps occasionally (every 10ish minutes?) - do you know why? I haven't yet set the REGION or paired it with a phone.

If you don't happen to know, no worries - I'll put it in a even more acoustically insulated box until I can poke at it.

I assume the SWD signals are accessible somewhere if I want to solder on some wires for debugging?

[Dylanliacc]

Hi @Dylanliacc I received my T1000-E and it looks really great and you've made some great code. bravo. One question (since I won't have time to really work on it until next week): It beeps occasionally (every 10ish minutes?) - do you know why? I haven't yet set the REGION or paired it with a phone.

If you don't happen to know, no worries - I'll put it in a even more acoustically insulated box until I can poke at it.

I assume the SWD signals are accessible somewhere if I want to solder on some wires for debugging?

During our two-day testing period, we did not encounter this phenomenon. Have you attempted restarting or restoring to factory settings? I believe the firmware I programmed before shipping is fault-free. This anomaly is quite perplexing. Maybe you can check the log when you start using it, or maybe someone actually sent you a message

[lyusupov]

@Dylanliacc
Is the T1000-E Meshtastic binary code compatible with earlier T1000-S or T1000-A products ?
The S and A versions do not have a proper USB data connector, but is it possible to upload the firmware over Secure BLE DFU method ?

The questions are inspired by this video: https://www.youtube.com/watch?v=P5phiYJlXe8

[geeksville]

During our two-day testing period, we did not encounter this phenomenon. Have you attempted restarting or restoring to factory settings? I believe the firmware I programmed before shipping is fault-free. This anomaly is quite perplexing. Maybe you can check the log when you start using it, or maybe someone actually sent you a message

@Dylanliacc Okay no worries - I'll look into this next week and send you a note with what I find. I wonder if it is related to this in sleep.cpp?

#ifdef BUZZER_EN_PIN
    digitalWrite(BUZZER_EN_PIN, LOW);
#endif

At boot elsewhere it is setting BUZZER_EN_PIN high, but on entry to deep sleep it is setting it low. Possibly every n minutes the board is re-entering deep sleep and this transition is causing the buzzer to briefly beep (until the CPU completely shutsdown and the internal pull-ups pull that line back high)?

[Dylanliacc]

@Dylanliacc Is the T1000-E Meshtastic binary code compatible with earlier T1000-S or T1000-A products ? The S and A versions do not have a proper USB data connector, but is it possible to upload the firmware over Secure BLE DFU method ?

The questions are inspired by this video: https://www.youtube.com/watch?v=P5phiYJlXe8

Sorry, T1000-S cannot be supported for UF2 upgrade .And my suggestion is that you do not do this. Although we have tested it and it is possible(BLE DFU), there have been several machines that have completely damaged the bootloader due to this behavior

[lyusupov]

@geeksville

I assume the SWD signals are accessible somewhere if I want to solder on some wires for debugging?

@Dylanliacc

... there have been several machines that have completely damaged the bootloader due to this behavior

According to this source https://www.disk91.com/2023/news/lorawan/sensecap-t1000-a-tracker/
the SWD debug pads are available on the PCB provided that one can sacrifice IP65 feature.

Earlier T1000 variants may use nRF52840 SoC in QFN48 package that does not expose USB D+ and D- signals - https://infocenter.nordicsemi.com/index.jsp?topic=%2Fps_nrf52840%2Fpin.html&cp=5_0_0_6_0_1&anchor=qfn48

FCC report: https://fcc.report/FCC-ID/Z4T-T1000

[macflyhub]

@Dylanliacc - I see you said the -S is not compatible but is the T1000-A compatible??
I tried to order the -E but got the -A instead.
So now I have 2 units I am scared to try an OTA Meshtastic flash.
Help!

[lyusupov]

@macflyhub
version A uses Goodix GR5515 MCU unlike versions S and E - they use Nordic nRF52840 MCU instead.

[macflyhub]

@lyusupov Thank you - I had a sneaky feeling this was going to be the case. Dammm.
Re-ordering some E's

[lyusupov]

@Dylanliacc
ETA for T1000-E is moving further and further: https://www.seeedstudio.com/SenseCAP-Card-Tracker-T1000-E-for-Meshtastic-p-5913.html

Is there any way for a developer to get the T1000-E device earlier than Sep 15th ?

[Dylanliacc]

@Dylanliacc ETA for T1000-E is moving further and further: https://www.seeedstudio.com/SenseCAP-Card-Tracker-T1000-E-for-Meshtastic-p-5913.html

Is there any way for a developer to get the T1000-E device earlier than Sep 15th ?

maybe you can contact me on discord :dylanaz1503 , and i'll let my marketing team reply you