Serial port communication not working via .net 5 for Marlin board

I am trying to get a simple Serial Port connection between dotnet 5 and a Marlin based printer board which is running some variant of a micro controller (LPC1768FBD100

I can open a connection to the board using other tools, send a "M503\n" command and receive a response, the tools I've used successfully are

  • Pronterface (Windows)
  • Arduino Serial Monitor (Windows)
  • miniterm (Linux)
  • putty (Windows)

So I know the board to be functioning correct in both Linux and Windows, but when attempting from .net, I am yet to succeed in getting any response back from the board. I have uploaded a simple tool in .net 5 that connects to a serial port and allows you to TX / RX strings,

I have tested this code in Windows and Linux, same port settings, no response back. I have also tested this exact code against a simple echo program running on an Arduino Uno board and it all works as expected, but for the life of me I can't get anything back from the other board.

I'm wondering if there's something about serial comms that these other apps are doing that I just don't know about. I'm using the same port settings which are shown in device manager across the board when testing in Windows, and also the same settings when testing in Linux.

In Linux the board comes up as ttyACM0, which is how my Arduino Uno is also mounted.

Any suggestions? I'm sure this isn't a "Marlin" issue, as only one of the other tools I've tested with is specific for Marlin and the Arduino serial monitor is about as basic as you can get. There's something I'm not doing in the .net code I think...

I've also tried someone elses old .net code and it also doesn't get a response back from this board, but does from my Arduino Uno running the echo program.



I'm currently looking to see if it's just .net and the underlying mechanisms that is effected here and have found this page,

I've modified my tester code to access to base stream for sending / receiving data just in-case, but this has not fixed the issue.

Read more here:

Content Attribution

This content was originally published by Nick at Recent Questions - Stack Overflow, and is syndicated here via their RSS feed. You can read the original post over there.

%d bloggers like this: