Replies: 2 comments
-
Small update, I now have data coming in to the CalTopo console - this seems to work from the LilyGo T-Echo hardware, but not from the Heltec V3. I'm not sure if it is a baud rate issue, or something else, as Chome seems to work to connect to the console, but screen and CalTopo does not. However, regardless of the serial port settings in the Mestastic app I can't seem to get Mestastic local to parse the data. I have tried NEMA, and serial.mode.caltopo. I am seeing the output, but not sure if there's a way to get the software to plot it as a "locator" in their terms. Example:
|
Beta Was this translation helpful? Give feedback.
-
Hi You're using the Console debug output. Try using a UART, by configuring the RX TX pins from the Meshtastic Radio Configuration app. For Heltec v3 I use Pins RX 47 and TX 48 and BAUD of 9600. To read off these pins I use an MKR 1010 wifi, or ESP32. Any board with Serial and Serial1 is super easy.... Below is the code I use to read from the Heltec v3... Heltec - MKR 1010
I hope that makes sense. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I'm trying to get real-time data from a Heltec V3 in to CalTopo. I have downloaded and installed the local version of CalTopo.
I have edited the topo.config file:
sarsoft.location.aprs.local.enabled=true
sarsoft.location.serial.tty.usbserial-0001=9600,8,1,0
log4i.logger.aprsengine.name=org.sarsoft.location.service.APRSLocalEngine
log4i.logger.aprsengine.level=INFO
This is on Mac OS X Sequoia 15.1.1.
I don't see anything in the CalTopo console/debug window, except when I unplug the Heltec:
I have tried viewing the serial port in Chrome, and I see regular logs/debugging, but I don't seem to see anything specific to locations from other devices, notably a LilyGo T-Echo:
Beta Was this translation helpful? Give feedback.
All reactions