RS232 Pins & Console

[Bachman]

Hello!

Flowcode show wrong pins, but the HW uses the correct ones.

RS232_Pins.jpg (95.8 KiB) Viewed 6270 times

Sending 0 (zero) via RS232, the information not shown in the console.

RS232_2.jpg (63.25 KiB) Viewed 6264 times

[dazz]

Hi Bachman
Ive attached an fcdx for that chip, rename the one in your fcd folder and paste the attached one in, i cant test it as i don't have that chip on hand.
Can you then post back here if it's ok

Regards
Dazz


PLEASE FIND NEW ATTACHMENT FURTHER DOWN

[Bachman]

Thank you!
The properties window is ok, only the chip name is too long. The console problem must be in the Flowcode, i think.

Shot_178.jpg (74.74 KiB) Viewed 6245 times

[medelec35]

Hi Bachman,

Sending 0 (zero) via RS232, the information not shown in the console.

When you use SendChar you need to look on the ASCII Table for the char being sent e.g 1 then look at the Dec number and send that value.
In the case of 1 you need to

Code: Select all

SendChar(49)

If you want to send 0 then you use

Code: Select all

SendChar(48)

:

SendChar1.png

(36.1 KiB) Downloaded 3295 times

An easier way to send a number is to send it as a string e.g SendString "0"
If you want to send a variable value e.g if VariableValue = 128
Then you could create a string then convert variable to a string then send the string:

SendChar2.png

(31.81 KiB) Downloaded 3295 times

Martin

[Bachman]

Yes, it's a solution for the bug. If i convert the numbers into ASCII, i need extra steps on the RX side to convert it back to numbers. Sending zero via UART works fine in the HW, the bug "visible" only in the simulation.

[dazz]

HI Bachman
Sorry about the name i used it for checking and forgot to remove the extra numbers (doh).
I have corrected and reattached to this post


Regards
Dazz

18F1320.fcdx

(21.38 KiB) Downloaded 276 times

[medelec35]

Yes, it's a solution for the bug. If i convert the numbers into ASCII, i need extra steps on the RX side to convert it back to numbers. Sending zero via UART works fine in the HW, the bug "visible" only in the simulation.

You don't need the extra steps to just send a 0.
Either sendChar(48)
or

SendString"0"

If you use SendChar(0) then that's a null character, not a 0.
So its just the termination of the string

The extra steps are only If sending a byte variable.

[Bachman]

The extra steps are only If sending a byte variable.

This is why i send 0, not "0".