On friday we will program that gauge together, via Skype and maybe Teamviewer.
Stefan
Printable View
On friday we will program that gauge together, via Skype and maybe Teamviewer.
Stefan
Thanks for the help guys, I am sure that once I get one running, it will be much easier to get the others. I now have the idea that for every object made you need to have a .cpp and a .h file to get it to work. Am I supposed to have windows.h somewhere? I do not seem to have it. Probably have to download the windows sdk for Vista? Little by little I will get this going. But not on my own.
Milt
That isnīt necessary, but it is a good way to cut the project in different parts. Sample: A Pedastel part contains a pedastal.cpp and .h file and so on.Quote:
I now have the idea that for every object made you need to have a .cpp and a .h file to get it to work.
In your actual case i would prefer a gauge.cpp and .h file, that would contains all the different analog gauges, that you like to build.
That is a part of VisualStudio, you have that installed.Quote:
Am I supposed to have windows.h somewhere?
Stefan
I am moving along slowly. I am now working on my attitude qauge. I am wondering what does 'FLT64' mean in the FSUIPC var. type? I have the gauge responding, but only to the point that on the pitch, it moves all the way up when it passes the center line going up and all of the way down when it passes the centerline going down. I see nothing in the FSBUSDLL manual about FLT64. So, yes, I am one again confused. Any help please.
Milt
It is called TP_I64 in FsBus.
I put TP_I64 in the proper place and it is still doing the same thing, full travel up, or full travel down, depending an whether I am ascending or descending. Obviously, this servo gauge can not be programmed the same way as my oil pressure gauge is.
Milt
Can you show us, the make of the FSObject and the case?
This is the FSBUS object as I have built it;
MkFsbusObject(BTP_A_OUT, S_ATTITUDEPITCH, "",EventHandler, 27, 86);
MkFsObject(FS_ATTITUDEPITCH, "", EventHandler, 0x2f70, 8, TP_I64, FS_normal);
This is the case;
switch(oid)
{
case FS_ATTITUDEPITCH:
static CALTAB ATTITUDEPITCH[] = {{0,106},{16384,164}};
FsbusWrite (S_ATTITUDEPITCH, Calibrate (val, ATTITUDEPITCH,2));
I know that I am doing something wrong, but am unable to figure it out.
Do you look to the offset with FSInterrogate2std for the min, max, and Zero position value?
Also do one more data to the calltap for the Zero(middel) Position.
Stefan
Got the offset from FSInterrogate and the min-max. Still did not work. I then used TP_DBL in place of the TP_I64 and it is now working. Took a few hours to figure out.
Milt