Re: TNC-PI Checksum error
toggle quoted messageShow quoted text
Yes will test in morning.
Have been out and about today.
Thanks for the efforts.
On Saturday, April 7, 2018 02:12:43 PM PDT, John Wiseman <john.wiseman@...> wrote:
I think this will fix it.
Could you test and let me know?
On 07/04/2018 18:34, John Wiseman wrote:
I think it is a bug in pitnc_get/set when the checksum (or in fact any other character) is 0E. That character is used in i2c polling to indicate nothing available, but is being being incorrectly ignored in get/set. I'll looking into a fix.
On 07/04/2018 17:45, ka2dew Tadd wrote:
I thought I saw a 1 in his PIC firmware version. Could that be the deal?
Tadd --- Sent from Planet X
On Apr 7, 2018, at 12:43 PM, John Wiseman <john.wiseman@...> wrote:
Something odd going on..
TNC Software Version 3
01 TXDelay - Zero means use ADC 50
02 Persistance 64
03 Slottime (in 10 mS) 10
04 TXTail 3
05 Full Duplex - Not used 0
06 Our Channel (Hex) 00
07 I2C Address (0 = async) Hex 00
ADC Value 34
8 3 32 40 a 3 0 0 0 22 52 c0 sum 0
As you can see, there is one more byte, the checksum, before the c0. For some reason your TNC isn't sending the checksum, so the final sum is non-zero.
I suppose as it seems be working perhaps it isn't worth worrying about, but it would be nice to know what is happening. Do you get the same problem if you change some of the registers?
On 07/04/2018 14:35, Steve Jones via Groups.Io wrote:
Sorry if this is a double post - but my previous reply appears to have gone into the ether.