Lpc2368 communication

If you are going to use the ethernet connection similar to a serial connection, where the technician connects his laptop to the heat pump, then it is likely that the technician initiates the connect, i.e. the PC is the client.

If the heat pump is the client, then it would have to constantly try to connect (and fail) until a PC finally gets connected.

Not only that - if you want to be able to control/reconfigure multiple heat pumps that have fixed IP on the internet from "any" computer, then the heat pump will be unable to know the IP number of that "any" computer. Hence, the heat pump must be server and given a fixed IP.

The alternative is that you don't have technicians who connect to individual heat pumps. You may have a central server that monitors multiple heat pumps (where each heat pump must be connected on Internet). Then each heat pump should be a client and be configured to know the IP number of this central server.

But the person who hands out the money for the project must have a document that describes what the expected result should be of this project. From the requirements in that document, it should be obvious which side is client, and which side is server. Figuring out which side is client or server is one of the smallest decisions in this kind of projects. Most people make this decision in their heads before even starting to put down the actual requirements of the system.

It may be worth it to consider a consultant for this job - someone who have ample knowledge would be able to implement a well-working solution in much shorter time. Getting a working product in a shorter time will offset the higher hourly charge for the consultant. Since the consultant is likely to consume less hours, even the work cost may be lower if a consultant is used. Just make sure that you have a copy of the tools needed to build the project, so you know that you can update the system even five years from now.

If you are going to use the ethernet connection similar to a serial connection, where the technician connects his laptop to the heat pump, then it is likely that the technician initiates the connect, i.e. the PC is the client.

If the heat pump is the client, then it would have to constantly try to connect (and fail) until a PC finally gets connected.

Not only that - if you want to be able to control/reconfigure multiple heat pumps that have fixed IP on the internet from "any" computer, then the heat pump will be unable to know the IP number of that "any" computer. Hence, the heat pump must be server and given a fixed IP.

The alternative is that you don't have technicians who connect to individual heat pumps. You may have a central server that monitors multiple heat pumps (where each heat pump must be connected on Internet). Then each heat pump should be a client and be configured to know the IP number of this central server.

But the person who hands out the money for the project must have a document that describes what the expected result should be of this project. From the requirements in that document, it should be obvious which side is client, and which side is server. Figuring out which side is client or server is one of the smallest decisions in this kind of projects. Most people make this decision in their heads before even starting to put down the actual requirements of the system.

It may be worth it to consider a consultant for this job - someone who have ample knowledge would be able to implement a well-working solution in much shorter time. Getting a working product in a shorter time will offset the higher hourly charge for the consultant. Since the consultant is likely to consume less hours, even the work cost may be lower if a consultant is used. Just make sure that you have a copy of the tools needed to build the project, so you know that you can update the system even five years from now.

My provider is getting a TCP / IP stack. I will look at the documentation when I provide it.

In fact I find it hard to understand how the TCP / IP stack ...

But it is now clear to me that the heat pump must be server. Because it does not know the IP of each different computer that will be connected to it.

the person who hands out the money for the project do not know if I should configure the server or client because it has no knowledge of TCP / IP or VB.

In any case I thank you for your help I have been very beneficial.

Thank you,
Mickael CHAPUIS

"the person who hands out the money for the project do not know if I should configure the server or client"

This is a design decision; It's not his (or her) job to do the design - that is your job (presumably?)

But it is his job to specify the requirements for this system; then you, as designer, decide how to meet those requirements - and one of those design decisions is whether to make it a client or server.

" because it has no knowledge of TCP / IP"

Neither, it seems, do you.

You really should be considering a consultant for this job!

"You really should be considering a consultant for this job!"

Sorry i am french and i don't understand what is a consultant ?

Sorry.

A Consultant is a person who is skilled & experienced in the field, and will assist you - or do the job for you - on a contract basis.

Keil has a list here: http://www.keil.com/condb/

NXP also has a list.

Your stack supplier may well also have a list.

No doubt there will be local trade directories that you can consult...

Thank you, but I think I'll always get there alone.
A test of strength and perseverance I will succeed.
I know the VB language and I already made ethernet communications with a machine so I will be successful with the lpc2368.
In any case thank you for your help I did well on my subject.
First I know that my project feasible and Second and I know he must be my PC client and the server lpc2368.
I already find codes c tcp its server will operate ... I have to be tested.

Thanks,
Mickael

VB knowledge may not mean too much when it comes to the LPC2368 side. A normal PC has about 10,000 times more RAM than the LPC2368 (yes - ten thousand times!), so a networked application in the LPC2368 must take this into consideration.

"A test of strength and perseverance I will succeed."

But is it worth it? If you spend 3-5 times as much time as the consultant, the total project cost will be affected, and the delivery time. It also affects the quality of the program, i.e. future maintainance costs.

This isn't a decision for you as developer, but a business decision for the company. Is it worth it to invest in your schooling, or is it better to get a well working application within a limited time frame.

Do not worry about the company everything will be done in the details. I do not know too much but my tutors c projects know very well. verrz you what he has already done with the lpc2368 you would be surprised.
But he did not know too many TCP / IP and no knowledge of VB.
That's why they call me.
So we should get there. In addition our subcontractor is development expert and he will set the TCP / IP stack so it will surely help us in the party lpc.
For the PC party I have very great knowledge in VB I will be able to make a nice application.

Best regards,
Mickael

If by chance someone has already done a similar project to mine I am on your listening if you have any tips or leads.

Thank you,
Mickael

Is what someone can explain what really has the TCP / IP stack ?

Thanks

I don't think anyone understand what you mean by:

"Is what someone can explain what really has the TCP / IP stack ?"

Is there a particular reason why you want to use ethernet rather than USB or plain, old RS232?

I certainly didn't!

But I thought you said your subcontractor was an "expert" - and they would sort your stack for you...?!

What really do the tcp/ip stack ?

I want to use Ethernet because there is no need for the module as serial port for example.
in addition everyone has a ethernet cable and I was not on my USB lpc ...

Yes were experts and they will schedule me my stack but I understand its operation after power to put my code in C inside