elvis-epx / loramador Goto Github PK

Elvis,
Hello, Thank you for all your work. I came across this the other day.
I know it's pretty new, so you may not have gotten a lot of feedback on it yet.
Let me start I've been testing this limited all day today. And for the most part it works as expected, I do have a few notes that I have noticed so far.

1st: move the "information" display to a 2nd page, and use the button on the LoRa32 board to switch between pages, or give an option to turn this information on and off from display. I think in most cases you will want to see it, at least at the testing phases,
2st: if the message being sent is long the message received is truncated. This could related to my 1st note, if the display was split into two screens you would/could have more room for longer messages

These two aren't really bugs, more notes on possible improvements.
My last note maybe a bug, but I'll let you decide.

Stations shall have 4 to 7 octets, shall not start with "Q", and may be suffixed by an SSID. Special or pseudo-callsigns are: QB (beacon) for automatic broadcast sent every 10 minutes, QC (think "CQ") for human broadcasting, and QL ("loopback") for debugging/testing.

I've noticed that an invalid call can send a message, IE: anything at least 4 characters long can send a message, IE: 1234, or aaaa, bbbb, cccc, ect.
I am not sure how if I have an idea to correct that, at 1st I thought maybe just a simple check for a number being included. I don't think that will fix the issue, but it might be something to think about.
Now I'm thinking that maybe a conditional check for each prefix maybe the only way to make it more valid, it's quite a large list of prefixes, but I think some of these are duplicated https://en.wikipedia.org/wiki/ITU_prefix

I am more of a novice to intermediate programmers, but I have been looking at the code to try and learn something, I understand parts of it, and other parts I need to learn more. Once I learn a little more, I'd be happy to try to contribute.

Thank you for your work, 73
KD8BXP, LeRoy

would it be possible to use lora E32-DTU modules which have an output directly to RS232 and RS485 to use this chat system with Arduino, Nodemcu esp8266 or Raspberry pi and/or simply Android by OTG cable and an RS232 to USB converter ? Alternatively connect the Lora E32-DTU modules to an Ebyte NB114 module to convert the RS232 ports to IP for use one way or another? I can use the E32-DTU modules with OTG cable on Android and an RS232 converter on usb port and a terminal on Android to Android or Android to linux or windows with terminal, but the terminals are not chat friendly! If you have an idea with the material I have, I'm interested I've been looking for a chat solution with it's E32-DTU modules for several months! Thanks

Hello,
I wonder if it is possible for you to program it like a 90's TNC2S and use also the software like Paxon to communicate with the TTGO. There is a !TNC function, but I don't understand the function of the cmd. But for example is the next example possible ?

For example I (AA1AAA) connects BB1BBB
AA1AAA sends "Hello world" to BB1BBB
If BB1BBB does not respond that he did receive "Hello world", the AA1AAA resends "Hello world".
If BB1BBB finaly does receive "Hello World", he conforms. and new packet can be send by AA1AAA

Like Packet Radio of the 90's ;-)

Peter