PDA

View Full Version : DeviceLink Help/Suggestion



WB_Outlaw
06-21-2004, 05:00 PM
I'm not an IP expert so feel free to tell me to shut the hell up, but, wouldn't it be easier to have DeviceLink receive requests on one port and send the answers on another?

Also, I posted this in the community help with no luck. Since there have been some discussion about DeviceLink here I thought it might get better results...

Has anyone been able to successfully query engines other than #1 (index 0) in a reasonable manner? The only way I can make a query with an engine index is to do each piece of info seperately (rpm, manifold pressure, etc.) for each engine. That's 6 queries per engine for what I want to monitor. Considering how many queries fail alltogether, there are huge lags in updates. If I don't supply an engine index I can get more than 24 requests in a single query including the #1 engine info. Below are some examples of what does/doesn't work for me.

This mega query works everytime but only returns the #1 engine info...
R/30/32/34/36/38/40/42/44/46/48/52/64/66/68/70/72/74/84/86/88/94/96/98

These also work because there is nothing after the engine index...
R/30/32/34/36/38/40/42/64\0
R/30/32/34/36/38/40/42/64\1

ANYTHING entered after the engine index fails to get a response...
R/30/32/34/36/38/40/42/64\0/64\1/66\0/66\1
R/30/32/34/36/38/40/42/64\0/44

Thanks for any help available.

-Outlaw.

WB_Outlaw
06-21-2004, 05:00 PM
I'm not an IP expert so feel free to tell me to shut the hell up, but, wouldn't it be easier to have DeviceLink receive requests on one port and send the answers on another?

Also, I posted this in the community help with no luck. Since there have been some discussion about DeviceLink here I thought it might get better results...

Has anyone been able to successfully query engines other than #1 (index 0) in a reasonable manner? The only way I can make a query with an engine index is to do each piece of info seperately (rpm, manifold pressure, etc.) for each engine. That's 6 queries per engine for what I want to monitor. Considering how many queries fail alltogether, there are huge lags in updates. If I don't supply an engine index I can get more than 24 requests in a single query including the #1 engine info. Below are some examples of what does/doesn't work for me.

This mega query works everytime but only returns the #1 engine info...
R/30/32/34/36/38/40/42/44/46/48/52/64/66/68/70/72/74/84/86/88/94/96/98

These also work because there is nothing after the engine index...
R/30/32/34/36/38/40/42/64\0
R/30/32/34/36/38/40/42/64\1

ANYTHING entered after the engine index fails to get a response...
R/30/32/34/36/38/40/42/64\0/64\1/66\0/66\1
R/30/32/34/36/38/40/42/64\0/44

Thanks for any help available.

-Outlaw.

WWSensei
06-21-2004, 05:41 PM
"I'm not an IP expert so feel free to tell me to shut the hell up, but, wouldn't it be easier to have DeviceLink receive requests on one port and send the answers on another?"

No, in fact, would be a smidgen harder because I'd have to worry about synching threads across two ports. So far one is bad enough. ;-)

As for querying the engine...with all due respect to Oleg and his team I don't think they could have designed a more inefficient and cumbersome interface if they had tried.

The failure after the index is because they don't handle multiple "\" marks in a string (betting an escape issue).

Don't feel bad about the failure rate. I can't get 3 simple landing gear status replies reliably.

Also having trouble when you drop out of game and into a menu structure. Seems the server side (game) grabs the port causing it to block and then never lets go until it times out.

It's cauing a problem for me on doing a monitoring thread whenever a user would drop out of game to the config window like in QMB...