SBL2e Eval Kit not able to make outgoing connections

[jprairie]

I have an evaluation kit for the SBL2e (as well as an SB70LC). I have been having problems verifying/confirming that the SBL2e is making outgoing connections.

I have a test application written in LabVIEW where the SB70LC seems to work just great. The application sees the connection request from the the netburner device and properly processes the data that is sent from the netburner device.

The SBL2e, on the other hand, doesnt want to co-operate very well with me. First some background on what I have done:

* I have been able to sucessfully complete the serial (MTTTY) and telnet operations described on page 13-14 of the Quick Start Guide. So, in essence it seems that things are configured properly as far as listening for incoming requests (from the telnet program)

* I can see the boot up messages on the debug serial port upon boot-up. I don't see any strange behavior here.

* Stepping back from the main testbed application, I created a simple LabVIEW program that listens for a incoming connection and once it is established, it simply closes the connection. I have configured the SBL2e to be in client mode and to forward to the IP/port number of the computer that the LabVIEW app is running on. I have, for this example, set the netburner to make an outgoing connection on power-up. At this point I launch the LabVIEW program and it happily sits and listens for a connection. I then power on the netburner and the Labview app continues to listen, as if it has not heard any incoming requests. Replacing the SBL2e with SB70LC (configured similarly for this example) the SB70LC powers up, the LabVIEW apps sees the incoming request, and then, as directed, proceeds to close the just made connection.


I believe I am running the latest firmware as we just bought these a week or so ago. If anyone has any ideas on how to proceed, please let me know.

Thanks,

Jason

[k1mgy]

Are you watching things on a serial console?

The SB70LC has two serial ports. If you can spare one, connect a terminal to UART0. By default you can use iprintf() and printf() to output to the console. Why not put some iprintf() statements in the code you're trying to validate to see what's going on?

[jprairie]

I may not be understanding your post entirely but I am not writing any code for the Netburner device. I think my problem is, perhaps, more fundamental. As advertised, the netburner should make an outgoing connection to a desired IP/port and it appears that with the manufacturer code, that process is not happening.

I have created, through a completely different programming environment, an application that waits and listens for an incoming TCP/IP connection and then does something in response to a succesfull connection. Right now, that very simple program I wrote is working just fine with the SB70LC in place but the same application simply sits and waits and waits when the SBL2e is in place. The implication of the waiting and waiting being that an outgoing request is never happening. Having said that, if there is a way to debug, outside of modifying the default code on SBL2e, that is what I am interested in. Assuming the device is still functional, which I believe it is since we have tried 2 different SBL2e devices with the same results on each, the problem is so fundamental, with respect to the advertised functionality, that it seems as if it is a configuration issue that I have missed somehow.

[k1mgy]

I understand. Now.

Well, the default application that ships with the SB2LE may be quite different from that which runs on the SB70LC. I don't know. My experience is with the SB70LC and I can say so far it has been excellent.

As these devices are, AFAIK, shipped for purposes of software/hardware development, not primarily for the application that runs on these by default, you may run the risk that the default application may change as things evolve.

I think you'll have to open the hood of both to see what's going on to be certain. Plus, you'll need to have control over it to support it.

Someone familiar with the SB2LE should chime in here, too..

[rnixon]

One way to test what is going on is to run the wireshark utility (free) and capture the tcp packets. Look for the outgoing connection from the SBL2e. You should see a TCP SYN packet from the SBL2e to the controller. Is your labview running on a pc that you can install wireshark on to capture the packets?

[jprairie]

rnixon,

I'll take a look into this wireshark utility tommorow. Thanks for the input.

[jprairie]

Via Netburner support, there has been a confirmation of this issue using v1.57 of the factory code. I have obtained v1.58 beta that someone has confirmed solves the issue referenced in this thread. I will be targeting v1.58 beta on my SBL2e today using the AutoUpdate tool. I'll report back what I find. Thanks for the help thus far and thanks to the NetBurner support for discovering this.

Jason

[jprairie]

the beta v1.58 seems to have fixed the issue with making outgoing connections