[Bug]: T114 can't send messages longer than 47 chars #4723
Comments
|
Does it forward packets normally or are certain length messages not forwarded? |
|
This issue has been mentioned on Meshtastic. There might be relevant details there: https://meshtastic.discourse.group/t/t114-fails-to-send-messages-above-certain-length/14719/1 |
|
Can you try setting a lower transmit power (e.g. 3 dBm) and see if the issue persists? I'm trying to figure out if it's a hardware issue (e.g. unstable power supply or EMC issues) or something else. |
|
Lowering the transmit power to 3 dbm did the trick! it transmitted for me from one T114 to another (DM), longfast. |
|
exact same behaviour here - ok below 8db |
|
I tried going back to earlier firmware 2.4.xxx, no improvement |
|
I am on 2.5 most recent release. If this issue is hardware based its bad, really bad!! because how I see it now every T114 so far is affected. |
|
My T114 is running 2.4.2 and I just sent a 71 character message to LongFast. Received successfully on my T-Deck (2.4.2). |
|
Also tested to send from my T114 ( stock 27dbm) to my Heltec V3 a much longer message then 71 (150) successfully 3 times out of 4. #longfast DM |
|
Today at 27dBm I can send around 60 character messages, up to 30 characters no problem after that I had to resend a couple of messages. At 3dBm I'm managing to send 200 character messages (stopped there as I wasn't sure what the limit is) and they've been getting through no problem. |
|
can send 144-char (base64 encoded, and 107-char decoded) messages with |
|
Thinking out loud... Given this symptom combined with some of the sporadic BLE issues, I wonder if we're looking at some hardware level issues with the LDO converter not being able to supply enough current to the MCU + peripherals under certain loads. |
|
Would a big enough capacitor at the LDO be able to buffer that? |
Potentially. If someone is willing to sacrifice hardware modifications in the name of science, we can find out. 😅 |
|
Q) Does everyone above have the version with a screen? GPS? |
|
Screen+ GPS and Screen no GPS but lots of other added stuff like vibra, buzzer ( both fired by a mosfet feeded directly from the 3.3volt rail) and a smd LED but that barely falls into weight as that stuff only fires up when receiving a message. |
Screen and GPS. |
|
Screen and GPS for me too.
…On Tue, 17 Sept 2024 at 07:16, DTopp ***@***.***> wrote:
Q) Does everyone above have the version with a screen? GPS?
Screen and GPS.
—
Reply to this email directly, view it on GitHub
<#4723 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIMTLW7DOBYX6PGAGO2P5TZXA2VHAVCNFSM6AAAAABOIBAVMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJVHE3TOMZSHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
neil*martin*
|
I would have suspected the same thing, but I've got it on the scope right now though and I can't measure any significant dip in voltage when transmitting. This was with screen only, powered by USB. I'll connect the GPS and see if it changes. Update: no change with GPS. Drawing ~150mA from 5V supply when transmitting. To my untrained eye, the 3.3V looks pretty solid, at least on my device. Update 2: I'm actually having trouble replicating the issue at all, so my report might not be that helpful. Long DM's seem to be going through fine for me right now. Could be good to get some observations instead from devices which are struggling. This is with tonight's master (a967dd5) |
|
I've managed to reproduce on a T114 no GPS and no screen. So it looks like those are not factors. Current master (2024-09-18). logs: |
|
@fifieldt Can you help break down what your debug logs here demonstrate? I'm a software dev, though new to Meshtastic as of a week. Aiming to run some tests at various dBm levels between a t114 and a control Wisblock node. Would love insight into what logs are indicating that could benefit my analysis outside of just looking at whether the message was received by the control node. Thanks! |
|
Hi @skylerwshaw , the only real interesting messages are the last 5. We got a packet from the phone, plan to send it to lora channel 0, sent a 255 byte payload, then died after cleaning up and adding it to our list of sent packets. The half-printed line where it dies is from code that hasn't been changed in >6 months, so that's probably not the root of the problem. |
|
Hello dear community, it is definitely not a hardware issue. I have fixed it on 3 devices. How? nrf erase multiple times, firmware 2.5, then back to 2.4.2 then back to 2.5, deleted again and back to 2.4.2 and now I can send the full number of characters :) |
Couldn't get your method to work for me unfortunately although it did perform a little better than it has been. |
That sounds wild, there must be a better solution, thats like rolling some dice and hoping to get a pair at some point?? |
Sounds like some sort of timing issue? My Heltec T114 has the same problem. |
|
Seems to be all over the place, I was not able to send larger messages above 7dBm with both of my T114s. Lowering dBm was in direct relation of being able to send bigger messages. The lower the dBm the more successful I was with bigger messages. Once I upped the dBm again step by step, message length decreased ( for a successful delivery) |
|
I emailed them my order numbers on the 10th and got a reply the next day. |
|
Much respect for Heltec. Working with the customers, and being so transparent.❤️ |
contact them directly over the messenger on ali express that includes your order , so did I and had a answer the next day. |
Just looked. Instead of replying to the email they responded on AliExpress for me. |
|
I received my reply via AliExpress chat too. |
|
This issue has been mentioned on Meshtastic. There might be relevant details there: https://meshtastic.discourse.group/t/meshtastic-scotland/11479/248 |
|
Since the hardware is being fixed with a new revision, will the board be added back to the web flasher and OTA update on the app? |
|
@joan7770 yes indeed - developers are just waiting to receive a board to do some final testing before that happens. |
|
Replacement going well on AliExpress chat. Thanks Heltec for not sucking! |
|
I've also bought their new T114 v2. Hope everything goes well. |
|
I can confirm that they replied to an email via AliExpress message, ~14 hours after the email. |
|
The response I received was that they would send it out in sequential order at the end of the month |
|
I contacted them through Aliexpress messaging and they replied same day with "Your order has been registered. We will ship it to you after the new version is put on the shelves. Please wait patiently" |
|
Ordered 3 recieved 4, the store packed in my replacement for the v1 I had ordered previously
|
|
Quick update, Bluetooth is a lot more solid, and long messages are passing through |
|
@guryonblaze, who was replacing your boards? Here's to hoping Muzi and other vendors receive them soon as well! Thanks for the update. |
A store on Aliexpress (Moonmall Store), was really impressed they packed the replacement with my order, but guess it makes sense as it saves shipping. |
|
Just got the T114 v2. Really impressive stuff. |
You mean because it works now? Or what exactly is impressive? Where you able to do some testing? How about the results? |
1 month and 1 week have passed since I've received a confirmation from Heltec Store on AliExpress that my replacement request is accepted and being queued. Every 7-10 I days I request a status update and the Heltec Sales representative always says that the shipment of replacement orders is going on but my particular order is not shipped out yet - "please, wait patiently..." |
|
they send them out in the same order they received the orders, I got confirmation and a tracking code 4 days ago. They do the best they can, you will get your replacement dont worry. yeah it takes some time but at least you get it fully replaced. Its gonna be alright. |
|
I got my tracking details a few days ago as well. |
|
I had mine delivered a few days ago. Battery life is crazy good! |
Once you go NRF52 its almost impossible to go back to esp32 when it comes to mobile or solar nodes ;) |
|
Has anyone had any luck with the RMA process for these through Amazon? I have a board that is outside of the normal return window apparently, but I would like to replace it (and have a low confidence in Amazon for these sorts of things). If this doesn't work, will Heltec allow contacting them directly (the posted directions say they will only directly service those purchased through their normal storefront and aliexpress (which is unfortunate when so many items are purchased through 3rd party sellers)). |
Get in direct contact with the seller on amazon, or was it directly sold by amazon? |
Not sold directly by Amazon sadly, the two different sellers have both now said they would send me new boards (hopefully they do, but I may not be getting the 20% coupon code unfortunately (I mostly want the board replacements as I need them working to make proper repeaters)). Has anyone identified a way to fix the v1 models? As they currently are, they would likely degrade the mesh network and probably shouldn't be used, but I'd hate to turn them into e-waste. |
|
Sadly there is no 100% working solution, I was having some success by adding capacitors to the SX chip and the 3.3volt rail but it never really solved the issue completely, with some of the boards I was able to send a lot more characters, others stayed exactly the same its just.....meh........you can use them as long you dont send to long messages, and to prevent them from degrading the mesh network, you can set it to "client_mute" that way they wont repeat incoming messages. as the V1 boards receive just fine there surely is some sort of use to them. Maybe make yourself some canned message node just sending out those short messages, they will work no problem. |
|
I'm probably going to take my two v1's and set them as CLIENT_MUTE, use them inside the house at low power because they will only need to reach the attic node with the strong antenna. Or if there is some other Lora non-meshtastic use I could throw at them. I'm with you though, I don't want to just toss them if there's something they could be used for. |
|
I can confirm that I received the replacement sceen-less modules. I assume I will receive the replacement ones with screens later on. So far so good. Will edit this reply as things change. |
and others
Category
Other
Hardware
Heltec Mesh Node T114
Firmware Version
2.4.3.91d6612
Description
Messages above 47 characters cannot be sent. Other are reporting that the message length that causes failure to send is variable https://www.reddit.com/r/meshtastic/comments/1fhc47k/heltec_t114_message_sending_bugfault
Relevant log output
No response
The text was updated successfully, but these errors were encountered: