Moderator: Freon
calvinc wrote:no timelines set, GUI programming in C++ is not my strong point. i'm also trying to make it as flexible as possible to allow for modifications to the bit masks as we learn and as more ecu types are learnt about.
thinking about releasing v2 as open source when its complete...
calvinc wrote:i'd rather chew off my arm than use microsofts new 'managed' classes within C++ .NET.
VB.NET still isnt up to the task.
C# has potential...but haven't tried the change over yet.
i have some experience in using dialog classes for really basic gui work, so i'm sure i could put 1 out that will be decent enough for what we need.
As I'm sure you're aware, c# is very similar to java. Most folks I know enjoy coding in it.
In case you are interested, you can download the beta 2 "Express" SKU of Whidbey (latest Visual Studio) c# ide here:
http://lab.msdn.microsoft.com/express/v ... fault.aspx
I like c# quite a bit, but I may be somewhat biased in that I work for Microsoft. Although I have hardly used the free "Express" SKU, since I'm not paying for the full SKU.
-Adrian
the interface speed is automatically scaled based on how many parameters you have selected. this is a deficiency of my comms interface and using the VB MSCOMM stuff. i will most definately improve on this in the next app.What is the maximum interface speed we can use or is it always the same?
you can log all analogue signals but its not advisable. this is when the comms routines run into trouble and start fragmenting the messages and finally it loses itself. rather log just what you find most important, your sample rate will also improve. deltadash also suffers from this problem.I noticed that if I was logging all the analog signals (not wise I know) that it would miss the defrost toggle, and would not start logging data.
i will check this out ASAP...The other very minor issue I noticed was the MIN and VALUE columns were swtiched for the digital signals. Ie... the MIN value would change when the switch was toggled, but the VALUE column would reflect the MIN value recorded.
the interface speed is automatically scaled based on how many parameters you have selected. this is a deficiency of my comms interface and using the VB MSCOMM stuff. i will most definately improve on this in the next app.
the ECU operates at fixed settings so they remain static and there is no need to allow the user to change them. maybe to enforce some sort of handshaking but nothing much else.Thanks. I was actually referring to the OS comms setup... ie baud rates,etc. Are those settings used or does the DL1 setup up everything for you?
The other idea I had was to be able to adjust the sample rate of the analog values. For example, sample RPM every time, but reduce the samples for, say, EGT to once every 4 samples. Would that be possible?
dubya_rx wrote:The other idea I had was to be able to adjust the sample rate of the analog values. For example, sample RPM every time, but reduce the samples for, say, EGT to once every 4 samples. Would that be possible?
Return to Data Logging Software
Users browsing this forum: No registered users and 7 guests