Hi Guys,
I've been playing with the new version for a couple of days now before committing to installing it on my pit. Love the changes you 've made especially the trees and water.

I tried the exporting cockpit data last night and it seems to be broken again.

I was using the UDPspeed Comanche cockpit program on a separate machine on my network and had EECHCommserver sending it the data. All the headings and other text data worked fine (compass turned when banking heli) but none of the indicators worked.

This happened before during an update and Firebird rewrote the EECHCommserver program as the data as being put in a different location.

Has anyone else tried the new version with data export and got it working ?

Cheers,

Andy

really strange, none of shared memory functions or variables was changed. what you mean by indicators - lamps, weapons state?

Hi Thealx,
I've added a screen capture of the program below. It displays all the stuff that is shown in the comanche cockpit in the game. I didn't bother top export the MFDs on the snapshot, but they fit in where they should.

Basically, all the data shown in the small screen to the left of the "Master Caution" light works fine, but none of the indicator lights come on and the stealth display of the heli doesn't change.

It may be something I'm doing wrong, but I'm pretty sure I'm doing the same as I did in the past.

Any help/advice would be appreciated.

Cheers,

Andy

Hi Guys,

When rooting about in the folders of EECH I found that a version of EECHCommUDPServer.exe had been included. I had been using the old version 5 EECHCommServer.exe

So I tried again with that program, unfortunately still the same. When I switched on the logging in the UDPSpeed program and checked the log it just kept repeating "Error in data" ten times a second.

Just tried running UDP and then starting EECHCommUDPServer and it filled the log with the same message again. I wasn't even running EECH.

Cheers,

Andy

Hey Andy

When did you start using UDP overlays?
Is that just for the "mini-pit" you are setting up for your visitors?

I thought you were using a SIOC interface to commserver, to drive the real indicators in your pit, like I do?

Are you still using that, too?
Any testing on its functionality?

I have been hesitant to try the newer versions (post version 11), as they were too buggy for the pit.
With all the recent hard work and bug hunting, I have been considering tying the new version.

with what version UDPspeed works properly - 1.15.0 or earlier?

GrizzlyT - No, I was trying out the new version on a different PC before I committed to installing it on my pit (been caught out like that before).

thealx - I think it was 1.14.0 was when Firebird fixed it.

Cheers,

Andy

I have INVALID VERSION error with CommUDPServer, can't understand what cause it - udpspeed or commserver. where I can find EECHCommServer?

Hi thealx,

You can download them from here:

www.simpit.me.uk/download/EECH_CommServer5.zip

www.simpit.me.uk/download/UDPSpeed_Comanche_Beta_02.zip

Cheers,

Andy

Hi thealx,

Have you had any success with this so far ?

Cheers,

Andy

hello. sorry for the delay, I was little busy.
after some experiments I can say that link "eech1.15.2->EECHCommUDPServer" works fine. commserver has debug log that can be enabled by adding "1" after port number in console string, aftre that all received and transmitted data will be visible. for example this log for default UDPSpeed comanche setup:


after Replied is transmitted data is listed - /variable\value/variable\value/ ... after quick check I found it correct (variables types can be checked here - http://eechcentral.simhq.com/index.php?title=EECH_CommServer). only problem makes requests of variable "1", it returns "INVALID COMMAND" (because it is). this problem caused by 03 MFDs Top, 04 MFDs Left, 05 MFDs Middle, 06 MFDs Right, 07 MFDs Bottom configs. to fix it change RequestString string in their ini file to something correct - /28 for example, it always returns "2".

but I have another problem - UDPSpeed very often gives "not floating value" error. I spent a lot of time trying different settings for elements, but it's unpredictable. some buttons are works and some not, but all digital indicators (that receive actual floating data) works properly. maybe it caused by some sort incompatibly of this application with my OS, or received data can't be read properly. please try to solve "INVALID COMMAND" like I described, maybe everything will work after that for you.

Hi Thealx,

I did as you suggested and changed the requeststrings to /28. Still not working.

I'm getting an "Invalid Version" error when I run the debug ( see pic).

Very strange....

Andy

are you using EECHCommUDPServer (creation date 27.12.2012)? EECHCommServer can't be used anymore.
just in case, check that MEMEXPORT is enabled =)

Hi Thealx,

The version I'm using was in the cohokum folder after I'd ran all the updates. It's creation date is 26.12.2012 so I take that it's the right one. And MEMEXPORT is set to 1, but I'm not even running EECH at this point.

As the machine I was trying this on is a 64 bit Windows 7 system, I tried putting both on another machine (32 bit windows 7) and ran them there - exactly the same errors.

Very strange this ....

Andy

you should run EECH, otherwise it will not work without data.

Just worked that out - what an idiot.

When I run EECH the floating point stuff is changing (heading etc) but not the indicators (see image).



the IP 192.168.2.6 is the machine with the UDP graphics on it. The game is running on 192.168.2.2

I have set these IPs in the UDP.ini and shortcut to Commserver program.

cheers,

Andy

what about Havoc or Hokum? just to find out what problem is. UDP client doesn't work for me at all.

Have tried all Russian aircraft and AH-64 as well. All the same.

I added the 1 to the end of the command line for UDPcommserver and I can see the data changing in response to the requests strings, but it doesn't change anything in UDPspeed.

I now have EECH, UDPcommserver and UDPspeed all on one machine. I set UDPspeed.ini to send 127.0.0.1 the request strings. That is obviously working as UDPcommserver is answering with data. It just doesn't get to UDPspeed program.

If I switch on the demo mode of UDPspeed all the lights cycle through.

Any ideas ?

Cheers,

Andy

Hi Thealx,

I came across an old thread between a member and Firebird discussing the same problem. Firebird had suggested removing all the folders from the UDPspeed directory except the floating point data ones such as heading, radar alt etc.

I tried that and they worked!

I put one of the digital indicators folders back in (left MFD indicator) and I started to get the "error in data" message in the UDPspeed log file.

Obviously there is some sort of data incompatibility between the UDPspeed guages program and what EECH\UDPCommserver are sending it.

Since it's not a program that a lot of people use, and you've been more than generous with your time already, I'd be inclined to forget about it.

Thanks for your help anyway.

Cheers,
Andy