Page 1 of 1

SBL2E TCP Encoding

Posted: Tue Dec 22, 2020 3:34 am
by elie.n
Hi,

I have a microcontroller, which sends data through a FTDI UART to USB cable, but we wanted to change the USB to ethernet, so we bought a SBL2E-100IR.
The data we used to receive via USB was i nthis format (via Putty) : >>2504,4,14,24,34,44,54,64,74,84,94,104,4
But when I change the USB cable to the SBL2E (Connecting TX and RX from the microcontroller to the UART0 of the SBL2E), I receive random garbage chars in my data like this : >>17▒b▒▒b▒4,54,64,▒ ▒b▒▒,104,114,▒&)▒▒b▒

I updated the SBL2E with the latest firmware available from the NetBurner website.

Any ideas why I cannot receive correct data ?

Thanks in advance !

Re: SBL2E TCP Encoding

Posted: Tue Dec 22, 2020 9:01 am
by pbreed
Did you change the Baud Rate to match your serial device?

Re: SBL2E TCP Encoding

Posted: Sun Jan 03, 2021 11:53 pm
by elie.n
Yes, baud rate, data bits, stop bits and parity are set correctly with the microcontroller !

Re: SBL2E TCP Encoding

Posted: Mon Jan 04, 2021 11:59 am
by TomNB
Are you running with RS-232 level shifters, or are you just using 3.3V signals? How long is the cable?

Re: SBL2E TCP Encoding

Posted: Tue Jan 12, 2021 10:39 pm
by elie.n
I only have 3.3V signals, no level shifters. The cable is about 30cm long.

Re: SBL2E TCP Encoding

Posted: Wed Jan 13, 2021 8:41 am
by TomNB
I can think of a few possibilities:
1. Somehow the usb to uart cable had shielding or twisted pair wiring so it was less susceptible to noise
2. The cable you are using is not wired properly, and may be missing a ground connection. Are you wired with rx, tx and ground?
3. Many usb to uart cables are designed for 5V. Just a check to verify your device is 3.3V

Can you send a photo and/or a description of what your cabling looks like?