Become a leader in the IoT community!

Join our community of embedded and IoT practitioners to contribute experience, learn new skills and collaborate with other developers with complementary skillsets.

Step 1 of 5

CREATE YOUR PROFILE *Required

OR
Step 2 of 5

WHAT BRINGS YOU TO DEVHEADS? *Choose 1 or more

Connect & collaborate 🀝with other tech professionals
Learn & Grow πŸ“š
Contribute Experience & Expertise πŸ”§
Step 3 of 5

WHAT'S YOUR INTEREST OR EXPERTISE? *Choose 1 or more

Hardware Design πŸ’‘
Embedded Software πŸ’»
Edge Networking ⚑
Step 4 of 5

Personalize your profile

Step 5 of 5

Read & agree to our COMMUNITY RULES

  1. We want this server to be a welcoming space! Treat everyone with respect. Absolutely no harassment, witch hunting, sexism, racism, or hate speech will be tolerated.
  2. If you see something against the rules or something that makes you feel unsafe, let staff know by messaging @admin in the "support-tickets" tab in the Live DevChat menu.
  3. No age-restricted, obscene or NSFW content. This includes text, images, or links featuring nudity, sex, hard violence, or other graphically disturbing content.
  4. No spam. This includes DMing fellow members.
  5. You must be over the age of 18 years old to participate in our community.
  6. You agree to our Terms of Service (https://www.devheads.io/terms-of-service/) and Privacy Policy (https://www.devheads.io/privacy-policy)
By clicking "Finish", you have read and agreed to the our Terms of Service and Privacy Policy.

How to Fix CR/LF Transmission Issues Between MS Excel VBA and STM32 via Serial?

I am trying to exchange data between MS Excel (using VBA) and my STM32 Nucleo board via a serial line (virtual COM port). I am using the Microsoft Datastream add-in, which I believe is designed for this purpose. However, I encountered an issue where the add-in doesn’t append CR (0x0D) or LF (0x0A) characters correctly. According to my serial port monitoring software, the add-in always sends 0x0A (LF) at the end, even if it’s not in the message. But if I manually include 0x0D (CR) or 0x0A (LF) in the message, they get omitted. Interestingly, other control characters like 0x09, 0x0B, etc., transmit fine.

Additionally, I’m using Excel version 365 with the Datastream add-in version 1.2. The STM32 device needs these CR/LF characters to process the messages correctly.
Have you encountered this issue or found a way to force the add-in to send CR/LF characters as expected?
Are there any workarounds in VBA to ensure this functionality?

  1. Dark AI#0000

    yeh, sure..you can try this. Instead of relying on the Datastream add-in, use VBA to manually append `Chr(13)` (CR) or `Chr(10)` (LF) to your message:
    “`Dim msg As String
    msg = “YourMessage” & Chr(13) & Chr(10)
    SerialPort.Write msg“`

  2. Dark AI#0000

    Also, On the STM32 side, handle LF (`0x0A`) by detecting it as an end-of-line marker, even if CR (`0x0D`) isn’t always included. This adds robustness to your data handling.

  3. Sterling#0000

    Thanks for the suggestion @darkai042 I’ll try using VBA to manually append the CR and LF characters
    I’ll let you know if I need further assistance.

CONTRIBUTE TO THIS THREAD

Browse other questions tagged 

Leaderboard

RANKED BY XP

All time
  • 1.
    Avatar
    @Nayel115
    1620 XP
  • 2.
    Avatar
    @UcGee
    650 XP
  • 3.
    Avatar
    @melta101
    600 XP
  • 4.
    Avatar
    @chitour
    600 XP
  • 5.
    Avatar
    @lifegochi
    250 XP
  • 6.
    Avatar
    @Youuce
    180 XP