Hi Following on from above, in FC the chart you posted doesn't constantly transmit. The component itself Waits for key press Gets value Waits for key release The only way it can then branch to actually send the value is if the value is less than 16 (0x10). I don't use Proteus so can't really advise ...

Hi If your clocks are correct you wouldn't really need "debounce" as:- You "test" and obtain a key press value, you send this value and you then wait for one second before "testing" again. If your clock was fast, that 1S delay may only be tens of mS. I always start by creating a one-second flash tes...

Hi Referente al valor FE, parece una actividad constante el el pin TX del Pic emisor That isn't happening in your FC chart / simulation so may be an issue in Proteus. Eso no sucede en su gráfico/simulación FC, por lo que puede ser un problema en Proteus. In Project Options you can set your oscillato...

Hi Sorry for the delay in replying due to travel. In a post above (11:38am) you show Proteus connections as Row on B0 - B3 and Column on B4 - B7 However FC has Row on B4 - B7 and Column on B0 - B3. This would certainly cause issues in reading the keypad. Both FC and Proteus need to have the same con...

Hi I don't use Proteus so I can't help with that. Your latest chart simulates correctly in Flowcode. When a key is pressed and held, the correct value is captured and stored in the array for transmission. Note though that this value only changes when you press a key and whatever is contained in the ...

Hi

I will let you know what I find using Hardware, but that will be later in the week

- - -

Les haré saber lo que encuentro usando Hardware, pero eso será más adelante en la semana.

Regards

Hi Thanks again for the response. Yes, I already see in the debugger and in the console that everything is transmitted fine. The problem is that at the output of the Tx terminal of the pic within Proteus, activity is seen but what the virtual terminal reads does not correspond to the values ​​that F...

Hi In simulation (no access to HW to test) Lat is set at a value and then stored in eeprom. Lat can then be set to zero, then read from eeprom returning the correct value. At this point Long had not been set. When read again in the Decision, Long had been set so perhaps that's the case? I'll test wh...

Hi It simulates fine in Flowcode. If you look at Simulation Debugger and display the variable Key, it will show the array values. If you look at the console data View > Consoles and click on UART1, you will see what is being transmitted by the UART. All good there too. I see you are using Proteus so...

Hi

Hmm.... Using a different machine I'm now getting the same results as you. I may have not noticed it earlier though........

Everything is fine until you read from eeprom in your branch (if Inicio = 1).

I'll see what I get in hardware when I get a chance.

Regards