home.social

Search

1000 results for “circfruit”

  1. @circfruit Fabulous. A friend made this github.com/varna9000/micropyth work on the Lilygo and he is over the moon. We are dead excited to make these devices run as a complete . Thanks so much! Just fabulous.

  2. @circfruit Fabulous. A friend made this #varna9000 #microreticulum github.com/varna9000/micropyth work on the Lilygo #T3S3 and he is over the moon. We are dead excited to make these devices run as a complete #lora #standalone #mesh #radio . Thanks so much! Just fabulous. #reticulum

  3. @circfruit Fabulous. A friend made this #varna9000 #microreticulum github.com/varna9000/micropyth work on the Lilygo #T3S3 and he is over the moon. We are dead excited to make these devices run as a complete #lora #standalone #mesh #radio . Thanks so much! Just fabulous. #reticulum

  4. @circfruit Fabulous. A friend made this #varna9000 #microreticulum github.com/varna9000/micropyth work on the Lilygo #T3S3 and he is over the moon. We are dead excited to make these devices run as a complete #lora #standalone #mesh #radio . Thanks so much! Just fabulous. #reticulum

  5. @circfruit Fabulous. A friend made this #varna9000 #microreticulum github.com/varna9000/micropyth work on the Lilygo #T3S3 and he is over the moon. We are dead excited to make these devices run as a complete #lora #standalone #mesh #radio . Thanks so much! Just fabulous. #reticulum

  6. @circfruit @abcdw I use my pinkies for Super key( mod key ) and also for mouse keys and trackpad states. My home rows are Shift, Ctrl, Alt and Super on pinky

  7. I've finally made a video about firmware (both plain and t-deck specific ones). I’m now able to demonstrate the image and voice sending and receiving capabilities over LoRa<—>TCP, which shows the real power of reticulum youtu.be/GdOzYJ3gv4k

  8. Whoa success! I managed to send audible voice msg from t-deck to MeshChat. Three days struggle 😭 The culprit was the tight loop of screen refreshing, keyboard poll, LoRa poll and i2s mic capture. It turns out esp32 core was skipping bytes from the mic which caused the codec to encode partial voice, causing inaudible msg. I gave preference to i2s bus and now the msgs are good enough and go over LoRa to meshchat successfully. Now i have voice and image transport on t-deck!

  9. Whoa success! I managed to send audible voice msg from t-deck #reticulum to MeshChat. Three days struggle 😭 The culprit was the tight loop of screen refreshing, keyboard poll, LoRa poll and i2s mic capture. It turns out esp32 core was skipping bytes from the mic which caused the codec to encode partial voice, causing inaudible msg. I gave preference to i2s bus and now the msgs are good enough and go over LoRa to meshchat successfully. Now i have voice and image transport on t-deck!

  10. Whoa success! I managed to send audible voice msg from t-deck #reticulum to MeshChat. Three days struggle 😭 The culprit was the tight loop of screen refreshing, keyboard poll, LoRa poll and i2s mic capture. It turns out esp32 core was skipping bytes from the mic which caused the codec to encode partial voice, causing inaudible msg. I gave preference to i2s bus and now the msgs are good enough and go over LoRa to meshchat successfully. Now i have voice and image transport on t-deck!

  11. Whoa success! I managed to send audible voice msg from t-deck #reticulum to MeshChat. Three days struggle 😭 The culprit was the tight loop of screen refreshing, keyboard poll, LoRa poll and i2s mic capture. It turns out esp32 core was skipping bytes from the mic which caused the codec to encode partial voice, causing inaudible msg. I gave preference to i2s bus and now the msgs are good enough and go over LoRa to meshchat successfully. Now i have voice and image transport on t-deck!

  12. Whoa success! I managed to send audible voice msg from t-deck #reticulum to MeshChat. Three days struggle 😭 The culprit was the tight loop of screen refreshing, keyboard poll, LoRa poll and i2s mic capture. It turns out esp32 core was skipping bytes from the mic which caused the codec to encode partial voice, causing inaudible msg. I gave preference to i2s bus and now the msgs are good enough and go over LoRa to meshchat successfully. Now i have voice and image transport on t-deck!

  13. I spent all day yesterday (I shouldn’t have): 1. Trying to resolve microreticulum transport issue. I can’t test/fix properly unless I reduce the dbm of tree nodes and simulate network and not going up and down the roof all the time; 2. Tried to implement voice msg in t-deck micropython firmware. I got the receiving part ok on codec2 3200, but can’t make it send proper voice. There’s some weird math going on which I can’t fix right now. I suspect the mic capture quality is bad.

  14. I spent all day yesterday (I shouldn’t have): 1. Trying to resolve microreticulum transport issue. I can’t test/fix properly unless I reduce the dbm of tree nodes and simulate network and not going up and down the roof all the time; 2. Tried to implement voice msg in t-deck #reticulum micropython firmware. I got the receiving part ok on codec2 3200, but can’t make it send proper voice. There’s some weird math going on which I can’t fix right now. I suspect the mic capture quality is bad.

  15. I spent all day yesterday (I shouldn’t have): 1. Trying to resolve microreticulum transport issue. I can’t test/fix properly unless I reduce the dbm of tree nodes and simulate network and not going up and down the roof all the time; 2. Tried to implement voice msg in t-deck #reticulum micropython firmware. I got the receiving part ok on codec2 3200, but can’t make it send proper voice. There’s some weird math going on which I can’t fix right now. I suspect the mic capture quality is bad.

  16. I spent all day yesterday (I shouldn’t have): 1. Trying to resolve microreticulum transport issue. I can’t test/fix properly unless I reduce the dbm of tree nodes and simulate network and not going up and down the roof all the time; 2. Tried to implement voice msg in t-deck #reticulum micropython firmware. I got the receiving part ok on codec2 3200, but can’t make it send proper voice. There’s some weird math going on which I can’t fix right now. I suspect the mic capture quality is bad.

  17. I spent all day yesterday (I shouldn’t have): 1. Trying to resolve microreticulum transport issue. I can’t test/fix properly unless I reduce the dbm of tree nodes and simulate network and not going up and down the roof all the time; 2. Tried to implement voice msg in t-deck #reticulum micropython firmware. I got the receiving part ok on codec2 3200, but can’t make it send proper voice. There’s some weird math going on which I can’t fix right now. I suspect the mic capture quality is bad.

  18. Damn, I got kicked in the balls by ’s Mark Qvist himself 😂 I was playing with MeshChatX and it never occurred to me that images send by reticulum chat apps are in Webp format. This means I have to implement decoder for this format for micropython (or C) and to be small enough not to choke the microcontroller. Esp32s3-cam has native jpeg and I already decode this on t-deck ok. So Mark says JPEGs are obsolete and chat app should’t support it (at least for sending)

  19. I guess i need to read a bit more for mode gateway and mode boundary, which apparently can isolate segments of the mesh. What i found is that it’s not good idea to put mode full on LoRa interface and suck all TCP traffic into the Lora mesh.

  20. 2. Afaik there was no guard in microreticulum firmware, so once the flash was filled in, the routes are not saved, announce cache is not saved
    3. This causes ping-pong of own announces between transport nodes, filling up the air, before the dedupe threshold is triggered.
    4. I’ve put a guard to delete old cache files once the the free space reaches 25%

    The joy of experimentation and going up and down the roof few times 😂

  21. When I’ve put up nodes out in the wild and the (LoRa part) network grows, some problems start to surface, mainly due to hardware constrains. It turns out nrf52840 based nodes are good for battery efficiency, but the insufficient flash, is kind of bummer. The problem was
    1. routing is saved on the flash - 1 file per heard node. However LittleFS works with 4kb per block, which means we are wasting precious space as most of the block is empty. So the free 76kb is exhausted really fast

  22. Second try with solar transport node - this time a bit higher on the chimney. Current path: laptop TCP -> RPI with Rnode and TCP (transport enabled) -> solar transport node (modified microreticulum firmware). Good passthrough for announces to a 1km away second solar node, but can’t get msg past that first solar node. The first solar node itself replies with battery status. I guess i need to refresh the second solar node with the last modifications/fixes.

  23. Going beyond the home lab, today i put up 2 more transport nodes with modified firmwares (responding with battery % on msg). I managed to get messages through from about 7km away with 3 hops over LoRa and 1 TCP interface. Obviously the ultimate goal is to send an image at that distance, I but need to fix some bugs on the t-deck firmware because it failed me.

  24. I’ve added jpeg view on the t-deck chat app. Looks so cool 😁 I have to make a video about this. Basically when t-deck sends “image” keyword to the camera node, the former gets back a camera capture and can show it on the screen. I do some centering and resizing to fit it on 320x240 on the deck’s screen. Again, for the sake of speedy jpeg decoding, I compiled a C module with micropython bindings.

  25. @nodestar umm i’d revise this statement “Reticulum to run on hardware that Python never could reach.”. Have a look at my implementation here. It’s a working implementation on esp32s3 and rp2040: github.com/varna9000/micropyth

  26. I fixed the bug! As a result of the efforts 3 major micropython improvements:

    1. Added IFAC support - now node can join password protected interfaces

    2. Implemented the cryptography modules in C with bindings with fallback to native module The result on this is mind blowing: complete decode chain reduced from 3 sec to 75 ms!

    3. Camera works! You can select quality and resolution of the image. I’m still to test over LoRa but on TCP receipt it’s almost instant.

  27. Whoa ! It’s working! Currently testing TCP interface only. Also a bug i need to go around - if MeshChat tries to initiate Link, the confirmation packet from esp32 doesn’t get the confirmation, so MeshChat keeps retrying. However if I send opportunistic msg, esp32 initiates the Link and the image gets sent successfully. Good progress anyway 🥳🎉

  28. Guess what I will be trying with next 😁

  29. I have ported @scummvm to LilyGo t-deck ( esp32s3) And I have no cardreader to put a game to test it right now. Have to wait couple of days. 😭😭#scummvm

  30. I have ported @scummvm to LilyGo t-deck ( esp32s3) And I have no cardreader to put a game to test it right now. Have to wait couple of days. 😭😭