Author Topic: No joy from SBC65EC Serial-UDP bus linkage  (Read 1176 times)

rhenthorn

  • Newbie
  • *
  • Posts: 2
    • View Profile
No joy from SBC65EC Serial-UDP bus linkage
« on: March 10, 2015, 03:06:09 PM »
Hi,

Total newb here.

We are, amongst other things, using a SBC65EC to obtain serial data from an instrument via the Serial-UDP linking feature. So far, getting and setting outputs and whatnot from a C++ application using UDP packets has gone really well without having to modify onboard software. However, we haven't had much success using the UDP/Serial bus linking feature to read data originating from, say, a RS232 port on a PC through to the RS232 serial port on the Modtronix board.

The web interface to configure the serial ports and serial bus seems simple enough, and we're not trying anything fancy. Here's our configuration on the xbus.htm page:

== Buses Configuration Tab ==
* UDP Bus 1  =>   Serial Port1
* Serial Port1 TX Buffer   =>  200
* Serial Port1 RX Buffer   =>  50

== Serial Bus Settings Tab ==
* Enable USART1 is checked.
* Baud Rate    =>  9600

== UDP Bus Settings Tab ==
* Enable UDP Port 1  is checked
* UDP Port  =>  54125


A custom 3-wire cable connects the serial lines on the board to a DB9 on a PC running hyperterminal at 9600-8N1. Finally, I have a C++ application running on the PC that opens a UDP socket to the board port 54125 and simply blocks on a recv() call. The idea is that when someone enters "Hello, World!" on the hyperterminal, the application receives "Hello World!" through the UDP socket via the SBC65EC, all handled by the UDP/Serial linking on the board.

My questions are pretty basic:

(1) Is that "Hello World!" test supported by the UDP bus linking feature of the SBC65EC?

(2) If so, is there a configuration setting that needs tweaking or some other failure point to examine?

(3) If not, suggestions?

Regards,

-Rich

rhenthorn

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: No joy from SBC65EC Serial-UDP bus linkage
« Reply #1 on: March 17, 2015, 04:34:34 PM »
Turned out it was a cabling issue.

All systems go, now.