This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Lpc2368 communication

Hello,
I want communicate with my lpc2368 by the Ethernet port using an application whose create with visual basic.
It is possible ?
How ?

Thanks,

Mickael

Parents
  • One thing to think about:

    Buy the Keil stack.

    Take their example code for a web server.

    Combine with your application.

    Create dynamically generated pages to display state information.

    Create input forms to allow input of parameters you want to change.

    Then you can communicate with your unit without the need for a special PC program.

    If you have advanced functions you want to implement, that isn't suitable for normal web pages, then you can still do it with a web server in the heat pump.

    Just create special links that either dumps large amounts of binary data to the PC (and requires a special PC program to accept and extract the data) or create special links where you post large blocks of data or uploads full binary files.

    Yes, I know that you said that you didn't need a web server, but it is an example program that will get you up and running - and it is also quite nice to be able to tell a customer:

    "Use a cross-over cable and connect to 192.168.0.1."

    "Tell us the message you see in your web browser. That message is the total # of running hours, the projected wear level of the internals and any detected errors."

    The nice thing about a web server is that just about any user can connect and extract information. This makes it possible to get info out of the system even if the customer has not arranged an external IP for your equipment. Or a service technician can have a chance to get advance information about a problem before going to the customer.

    Custom applications to communicate with hardware was something everyone used 10-20 years ago. Now, almost everyone tries to make as much actions as possible accessible through a web server. Possibly with a number of different passwords, to specify access levels. One password for the customer. Another for remote access. Another for a technician. A fourth for the factory...

Reply
  • One thing to think about:

    Buy the Keil stack.

    Take their example code for a web server.

    Combine with your application.

    Create dynamically generated pages to display state information.

    Create input forms to allow input of parameters you want to change.

    Then you can communicate with your unit without the need for a special PC program.

    If you have advanced functions you want to implement, that isn't suitable for normal web pages, then you can still do it with a web server in the heat pump.

    Just create special links that either dumps large amounts of binary data to the PC (and requires a special PC program to accept and extract the data) or create special links where you post large blocks of data or uploads full binary files.

    Yes, I know that you said that you didn't need a web server, but it is an example program that will get you up and running - and it is also quite nice to be able to tell a customer:

    "Use a cross-over cable and connect to 192.168.0.1."

    "Tell us the message you see in your web browser. That message is the total # of running hours, the projected wear level of the internals and any detected errors."

    The nice thing about a web server is that just about any user can connect and extract information. This makes it possible to get info out of the system even if the customer has not arranged an external IP for your equipment. Or a service technician can have a chance to get advance information about a problem before going to the customer.

    Custom applications to communicate with hardware was something everyone used 10-20 years ago. Now, almost everyone tries to make as much actions as possible accessible through a web server. Possibly with a number of different passwords, to specify access levels. One password for the customer. Another for remote access. Another for a technician. A fourth for the factory...

Children
  • ... there will be no need for any VB programs!

    What will the OP do then...?!

  • Take an early friday evening, knowing that the solution is economical for his employer, and practical for the technicians and customers and is future-proof since no VB code will break if MS makes any radical design decisions with their platform. And the client side will be available on Mac (without running Windows on it), Linux, FreeBSD, ...

    Quite a number of people with custom 16-bit Windows applications had to swear a lot when their applications didn't work well on Win2k.

    Most developers who have worked with embedded for a while can tell stories about crying technicians who have managed to smash their old Win95/Win98 laptop and suddenly finds themself locked out of the systems they are supposted to work with...

  • Sorry, but we have already studied possbilité to integrate a web server on the lpc2368 but the memory is strong enough to incorporate all the features we need. that is why we have chosen the solution to integrate all this to create an application with VB that will retrieve different variables or write in others.
    Everybody has Windows XP in the factory so its no problem given version of the application used for the technician "after sales service"