Jetcat Windows Software
10-07-2003 | 03:00 PM
#1
Thread Starter
Senior Member
My Feedback: (11)
Jetcat Windows Software
I'd like to know more about the software that Jetcat sells for ([:'(] [:@]) Windows...
Unfortunately there isn't much info on it on the Jetcat site. Is anyone here using it ? If so:
[ul][*] How often do you use it ?[*] How useful is it ?[*] What does it do ?[*] What doesn't it do that you wish it did ?[*] Can you view data from multiple historical runs simultaneously ? (e.g. to spot a trend of an increasing pump voltage)[*] What system requirements are there ? (O.S., connection ports etc)[*] Has anyone run this with Windows on a PocketPC / PDA ?
[/ul]
Thanks,
Gordon
Unfortunately there isn't much info on it on the Jetcat site. Is anyone here using it ? If so:
[ul][*] How often do you use it ?[*] How useful is it ?[*] What does it do ?[*] What doesn't it do that you wish it did ?[*] Can you view data from multiple historical runs simultaneously ? (e.g. to spot a trend of an increasing pump voltage)[*] What system requirements are there ? (O.S., connection ports etc)[*] Has anyone run this with Windows on a PocketPC / PDA ?
[/ul]
Thanks,
Gordon
10-07-2003 | 05:51 PM
#2
My Feedback: (11)
RE: Jetcat Windows Software
Gordon:
I have the Jettronics for Windows software. My intent was to use it for diagnosing problems (haven't had any that weren't my fault ie. forgot to open the manual fuel valve), getting baselines on engine performance (1st run vs. latest runs), and looking at throttle responses (to adjust throttle curves in TX to make it more linear).
The only way to compare history of runs simultaneously is to export it to MS Excel (comma delimited file).
I've got the software to work with WIN 95, WIN 98 and WIN XP.
One slight problem that I discovered is that you have to act as if you are going to save a file then click on "load log" to get a historical run file to load. If you try to click on load log first without "saving the log" the load dialog box does not open.
Another thing to watch for is that you need a PC / laptop that has a serial port with a 16550 UART to be able to keep up with the incoming data stream (any baud rate). If you have an old laptop without the 16550 UART, the data ends up as garbage as soon as the buffer is overrun. The software doesn't include any software or hardware "handshaking" between the PC and the ECU.
These are my experiences only. I think it is a GOOD value when you think of preventative maintenance possibilities (fuel pump voltage, etc. as you pointed out).
Thanks
I have the Jettronics for Windows software. My intent was to use it for diagnosing problems (haven't had any that weren't my fault ie. forgot to open the manual fuel valve), getting baselines on engine performance (1st run vs. latest runs), and looking at throttle responses (to adjust throttle curves in TX to make it more linear).
The only way to compare history of runs simultaneously is to export it to MS Excel (comma delimited file).
I've got the software to work with WIN 95, WIN 98 and WIN XP.
One slight problem that I discovered is that you have to act as if you are going to save a file then click on "load log" to get a historical run file to load. If you try to click on load log first without "saving the log" the load dialog box does not open.
Another thing to watch for is that you need a PC / laptop that has a serial port with a 16550 UART to be able to keep up with the incoming data stream (any baud rate). If you have an old laptop without the 16550 UART, the data ends up as garbage as soon as the buffer is overrun. The software doesn't include any software or hardware "handshaking" between the PC and the ECU.
These are my experiences only. I think it is a GOOD value when you think of preventative maintenance possibilities (fuel pump voltage, etc. as you pointed out).
Thanks
10-08-2003 | 01:25 PM
#4
My Feedback: (10)
RE: Jetcat Windows Software
Well I can weigh in I guess.
First it is my understanding it will not run on Pocket PC, has something to do with math co processor support in Pocket PC. BTW I have tried to get the source code to fix this myself with the DOS version, I still think it would be neat but with my real job I have no time.
Second I do not think you could overlay one flight's data with another, and even if you could I am not sure what that would tell you. What you CAN do however is lay one parameter over another, like throttle position, RPM, EGT, pump voltage, etc. This is great for troubleshooting, especially fuel system or pump problems. You can also monitor all of the turbine states as well.
You could easily lay one flight over another with Excel I guess, if that is what you want. I used to do this all the time with the old software to lay parameters like speed and RPM against one another.
Also not sure if anyone knows this but the new software stores the last 4 seconds of the flight in EEPROM, so you can diagnose 90% of fuel shutdown problems with just the GSU, a major new feature.
First it is my understanding it will not run on Pocket PC, has something to do with math co processor support in Pocket PC. BTW I have tried to get the source code to fix this myself with the DOS version, I still think it would be neat but with my real job I have no time.
Second I do not think you could overlay one flight's data with another, and even if you could I am not sure what that would tell you. What you CAN do however is lay one parameter over another, like throttle position, RPM, EGT, pump voltage, etc. This is great for troubleshooting, especially fuel system or pump problems. You can also monitor all of the turbine states as well.
You could easily lay one flight over another with Excel I guess, if that is what you want. I used to do this all the time with the old software to lay parameters like speed and RPM against one another.
Also not sure if anyone knows this but the new software stores the last 4 seconds of the flight in EEPROM, so you can diagnose 90% of fuel shutdown problems with just the GSU, a major new feature.
