Sneek Peak of new Hymee Enhanced Product
07-24-2005, 11:12 PM
#677
Administrator
yeah yeah .6 fixed and re attached. the point i was making is that if you do the sort this way you can plot any of them on x or y . Time if you want or not. Unless im missing something"and i probably am
) the pivot table when you chart it always has the time as x axis. this is hard for me to read when im trying to see the change in the afr over the rpm range. this sort and expand way allows you to sort them out but use the time just as any other value. and chart it or not and put therpm on the x.
) the pivot table when you chart it always has the time as x axis. this is hard for me to read when im trying to see the change in the afr over the rpm range. this sort and expand way allows you to sort them out but use the time just as any other value. and chart it or not and put therpm on the x.
07-24-2005, 11:25 PM
#679
Administrator
his is in the bottom half of the first pic. i took a prnt screen cause the spreadsheet wont post. the top haldf is the normal "raw" form then below that is the sort /expand by ajax. it now looks like the pivot table but is not bound by its restrictions.
p.s. this is embarrasing but- wha tis the value the maf is giving? on the live gauge it says "gS" or somethign i just dotn have aclue what that is... :o
p.s. this is embarrasing but- wha tis the value the maf is giving? on the live gauge it says "gS" or somethign i just dotn have aclue what that is... :o
07-31-2005, 07:21 PM
#681
Registered
Join Date: Aug 2003
Location: Brisbane, Australia
Posts: 1,459
Likes: 0
Received 0 Likes
on
0 Posts
Everyone,
We've had a request to change the log file format to make it a bit easier to use in Excel (i.e. not use pivot tables). This is a feature I wanted to put in the first release but didn't make the cut when we were triaging features to get that version out the door.
I'm planning on making the log file to be written in different formats in the upcoming release (that I'm still in the middle of making changes for).
In the meantime, for those of you who want this feature I've written a little utility. You can download it here: http://www.hymee.com/downloads/LogCnv.zip .
This utility will take an existing log file and convert it into a table format with one row per timestamp rather than one row for each individual data item.
To use it extract the .zip into the directory you store your log files. Then open a command prompt, change to that directory then to convert you type in:
logcnv input.csv output.csv
Where input.csv is the name of the log file you want to convert and output.csv is the name of the converted file.
Hope this helps. If you have any hassles with it, send an email to support@hymee.com and include the file you're trying to convert as an attachment.
Cheers
sco
We've had a request to change the log file format to make it a bit easier to use in Excel (i.e. not use pivot tables). This is a feature I wanted to put in the first release but didn't make the cut when we were triaging features to get that version out the door.
I'm planning on making the log file to be written in different formats in the upcoming release (that I'm still in the middle of making changes for).
In the meantime, for those of you who want this feature I've written a little utility. You can download it here: http://www.hymee.com/downloads/LogCnv.zip .
This utility will take an existing log file and convert it into a table format with one row per timestamp rather than one row for each individual data item.
To use it extract the .zip into the directory you store your log files. Then open a command prompt, change to that directory then to convert you type in:
logcnv input.csv output.csv
Where input.csv is the name of the log file you want to convert and output.csv is the name of the converted file.
Hope this helps. If you have any hassles with it, send an email to support@hymee.com and include the file you're trying to convert as an attachment.
Cheers
sco
07-31-2005, 08:08 PM
#682
Registered
Join Date: Aug 2003
Location: Brisbane, Australia
Posts: 1,459
Likes: 0
Received 0 Likes
on
0 Posts
Also, now is the time for any requests for changes or feature suggestions if you haven't already asked. I'm in the middle of the next release and will be locking down the feature set very soon.
08-01-2005, 04:29 AM
#684
Registered
Join Date: Sep 2004
Posts: 292
Likes: 0
Received 0 Likes
on
0 Posts
2;
Ive found I cannot start a log without having the live tab running. Is that normal?
Can you include an option in the log tab to be able to click anywhere in the screen to start/stop the log, without needing a trigger? I'm thinking a button next to the current start button that leads to a second huge button that unconditionally starts, then stops the log, then disappears.
As it is, its fine, but it would make logging a bit easier in certain situations. I wonder if i am the only person who would like to see this.
Ive found I cannot start a log without having the live tab running. Is that normal?
Can you include an option in the log tab to be able to click anywhere in the screen to start/stop the log, without needing a trigger? I'm thinking a button next to the current start button that leads to a second huge button that unconditionally starts, then stops the log, then disappears.
As it is, its fine, but it would make logging a bit easier in certain situations. I wonder if i am the only person who would like to see this.
08-01-2005, 06:10 AM
#685
Registered
Join Date: Sep 2004
Location: Europe
Posts: 581
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by sco
Everyone,
We've had a request to change the log file format to make it a bit easier to use in Excel (i.e. not use pivot tables). This is a feature I wanted to put in the first release but didn't make the cut when we were triaging features to get that version out the door.
I'm planning on making the log file to be written in different formats in the upcoming release (that I'm still in the middle of making changes for).
In the meantime, for those of you who want this feature I've written a little utility. You can download it here: http://www.hymee.com/downloads/LogCnv.zip .
This utility will take an existing log file and convert it into a table format with one row per timestamp rather than one row for each individual data item.
To use it extract the .zip into the directory you store your log files. Then open a command prompt, change to that directory then to convert you type in:
logcnv input.csv output.csv
Where input.csv is the name of the log file you want to convert and output.csv is the name of the converted file.
Hope this helps. If you have any hassles with it, send an email to support@hymee.com and include the file you're trying to convert as an attachment.
Cheers
sco
We've had a request to change the log file format to make it a bit easier to use in Excel (i.e. not use pivot tables). This is a feature I wanted to put in the first release but didn't make the cut when we were triaging features to get that version out the door.
I'm planning on making the log file to be written in different formats in the upcoming release (that I'm still in the middle of making changes for).
In the meantime, for those of you who want this feature I've written a little utility. You can download it here: http://www.hymee.com/downloads/LogCnv.zip .
This utility will take an existing log file and convert it into a table format with one row per timestamp rather than one row for each individual data item.
To use it extract the .zip into the directory you store your log files. Then open a command prompt, change to that directory then to convert you type in:
logcnv input.csv output.csv
Where input.csv is the name of the log file you want to convert and output.csv is the name of the converted file.
Hope this helps. If you have any hassles with it, send an email to support@hymee.com and include the file you're trying to convert as an attachment.
Cheers
sco
Thanks,
Fabrice
08-01-2005, 07:34 AM
#686
Registered
Join Date: Aug 2003
Location: Brisbane, Australia
Posts: 1,459
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Zaku-8
Ive found I cannot start a log without having the live tab running. Is that normal?
Can you include an option in the log tab to be able to click anywhere in the screen to start/stop the log, without needing a trigger? I'm thinking a button next to the current start button that leads to a second huge button that unconditionally starts, then stops the log, then disappears.
As it is, its fine, but it would make logging a bit easier in certain situations. I wonder if i am the only person who would like to see this.
Can you include an option in the log tab to be able to click anywhere in the screen to start/stop the log, without needing a trigger? I'm thinking a button next to the current start button that leads to a second huge button that unconditionally starts, then stops the log, then disappears.
As it is, its fine, but it would make logging a bit easier in certain situations. I wonder if i am the only person who would like to see this.
It wouldn't be too hard for me to set it up so if you click anywhere on the live tab (i.e. on one of the gauges or the space in between) it starts logging and stops it again. I'd probably have an option on logging tab like "Clicking anywhere on the live tab starts and stops logging" so you can choose if you want this turned on or not.
Any comments on this appreciated.
08-01-2005, 09:00 AM
#688
Registered
Join Date: Aug 2003
Location: Brisbane, Australia
Posts: 1,459
Likes: 0
Received 0 Likes
on
0 Posts
Hmm... didn't you read the warnings at the start of the manual 
You guys want this feature because your passenger might have trouble hitting a button if the road's a bit bumpy... right?
You guys want this feature because your passenger might have trouble hitting a button if the road's a bit bumpy... right?
08-01-2005, 09:14 AM
#689
Originally Posted by sco
Hmm... didn't you read the warnings at the start of the manual
You guys want this feature because your passenger might have trouble hitting a button if the road's a bit bumpy... right?
You guys want this feature because your passenger might have trouble hitting a button if the road's a bit bumpy... right?
/actually my girlfriend graciously spends time driving my car as I tinker with the program...I don't think she minds though
08-01-2005, 03:42 PM
#690
Registered
Join Date: Aug 2003
Location: Brisbane, Australia
Posts: 1,459
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by truemagellen
actually my girlfriend graciously spends time driving my car as I tinker with the program...I don't think she minds though
sco "I thought I said to keep it under 3000rpm while it's stone motherless cold"
g/f "I am. I am"
sco (points at tell-tale on the RPM gauge) "What's this thing pointing at five and a half thousand then?"
10-06-2005, 03:28 AM
#691
Registered
Join Date: Aug 2003
Location: Brisbane, Australia
Posts: 1,459
Likes: 0
Received 0 Likes
on
0 Posts
Everyone,
Sorry for the long post... If you're short on time look for the bold text for the key points.
First let me apologise for taking so long to update you with where we're at with the next version of sCANalyser :o . It's taken alot longer to get here than I anticipated. A few good things have happened along the way. Let me explain.
Hymee and I have formalised our partnership and created a company called Performance Design Australia... so you'll see a little bit of a branding change. Hymee's "stamp of approval" still goes on our RX-8 products, so Hymee Enhanced will still be around but you'll be seeing us using Performance Design Australia as the company name. It's just a name change... The people are still the same. Setting all this up has chewed up a lot of time.
We've also had some opportunities presented along the way to do some R&D on some really cool stuff that we hope to add into sCANalyser in the future. I don't want to talk about this yet, for reasons I'll go into shortly. We had to take time out from development of the next version to do that R&D because there was a window of opportunity to do that R&D and if we didn't take it we would have missed it.
You'll also notice that I've stopped talking publicly about new features. There are a couple of reasons for that. Some of the things we've been doing with sCANalyser have been better than some of the existing tools out there ... And what we've been doing may have been copied. So to maximise our success, which means our ability to keep supporting the product and add new features we've deliberately taken the decision to not talk too much about innovation in sCANalyser so we don't give people a head start on what we're doing. Also, it appears that there are competitors out there who have a goal of putting small guys like us out of business and I don't want to give them any help by talking about innovative stuff before it becomes available. I'm really sorry we have to do this but it has become a necessity.
Please continue to send us feedback... We want to hear it. If something you suggest is really cool we'll still include it, but we may just not say that we will publicly until it is "baked".
So with that out of the way let me bring you all up to speed as to where we're at. We're about to release a new beta version of sCANalyser. It has some stuff you all want... Access to non-standard information such as Knock Retard and graphing. We've also listened to all of your feedback and I hope everyone who has requested some changes will be happy. I'm still tidying up some of those feature requests, so if they're not in beta we release shortly, don't despair - I hope to have them added in prior to the final release. Don't be afraid to ask me if something you expected isn't there... I'm pretty sure I've got a complete list, but you never know. There are also other cool features that I'm sure you'll love but I'll save them for a surprise. Best of all, they will be made available to everyone who has a sCANalyser for no cost. A lot of the new features were things we wanted in the first release of the software but didn't have time to do.
Important... We're crossing T's and dotting I's again.. I can't tell you yet exactly when we'll release the beta, but we want those of you who are interested in helping us test this new version to know as soon as it is. I have a fixed list of things to get done before I release it and as soon as that list is done and testing shows we've got a reasonably stable version then we'll release.
To get access to this beta version when it becomes available, please email beta@performancedesign.com.au with a short email asking to be added to our beta email list and also let us know what your sCANalyser serial number is (the number on the back of the black box interface).
We may not respond immediately.. give us a few days... we're focused getting through all the outstanding tasks as quickly as possible.
In getting access to the beta version we ask some small favours:
1. You don't talk about the new features publicly for reasons I've outlined above unless of course I've already discussed them publicly.
2. You expect to hit a few bugs. The purpose of a beta is to have you test the software under normal use. This helps us by capturing any use that we didn't anticipate (and thus didn't test). It also gets us feedback on new features before we lock down the final release (so we can tweak any major issues). We'd appreciate it if you report any bugs direct to us at beta@performancedesign.com.au. Please don't talk about them publicly (for the same reasons I outlined above). If we come across an issue that seems like it affects more than one or two people I'll send everyone who signed up for the beta an email describing the issue and what course of action to take.
I hope that's not too bold of me to ask.
I'm working as quickly as I can to get this out to you... I really appreciate your patience. I hope it will be rewarded.
Finally thankyou to everyone who has purchased sCANalyser and also thanks to everyone who has provided feedback.
Cheers
sco
Sorry for the long post... If you're short on time look for the bold text for the key points.
First let me apologise for taking so long to update you with where we're at with the next version of sCANalyser :o . It's taken alot longer to get here than I anticipated. A few good things have happened along the way. Let me explain.
Hymee and I have formalised our partnership and created a company called Performance Design Australia... so you'll see a little bit of a branding change. Hymee's "stamp of approval" still goes on our RX-8 products, so Hymee Enhanced will still be around but you'll be seeing us using Performance Design Australia as the company name. It's just a name change... The people are still the same. Setting all this up has chewed up a lot of time.
We've also had some opportunities presented along the way to do some R&D on some really cool stuff that we hope to add into sCANalyser in the future. I don't want to talk about this yet, for reasons I'll go into shortly. We had to take time out from development of the next version to do that R&D because there was a window of opportunity to do that R&D and if we didn't take it we would have missed it.
You'll also notice that I've stopped talking publicly about new features. There are a couple of reasons for that. Some of the things we've been doing with sCANalyser have been better than some of the existing tools out there ... And what we've been doing may have been copied. So to maximise our success, which means our ability to keep supporting the product and add new features we've deliberately taken the decision to not talk too much about innovation in sCANalyser so we don't give people a head start on what we're doing. Also, it appears that there are competitors out there who have a goal of putting small guys like us out of business and I don't want to give them any help by talking about innovative stuff before it becomes available. I'm really sorry we have to do this but it has become a necessity.
Please continue to send us feedback... We want to hear it. If something you suggest is really cool we'll still include it, but we may just not say that we will publicly until it is "baked".
So with that out of the way let me bring you all up to speed as to where we're at. We're about to release a new beta version of sCANalyser. It has some stuff you all want... Access to non-standard information such as Knock Retard and graphing. We've also listened to all of your feedback and I hope everyone who has requested some changes will be happy. I'm still tidying up some of those feature requests, so if they're not in beta we release shortly, don't despair - I hope to have them added in prior to the final release. Don't be afraid to ask me if something you expected isn't there... I'm pretty sure I've got a complete list, but you never know. There are also other cool features that I'm sure you'll love but I'll save them for a surprise. Best of all, they will be made available to everyone who has a sCANalyser for no cost. A lot of the new features were things we wanted in the first release of the software but didn't have time to do.
Important... We're crossing T's and dotting I's again.. I can't tell you yet exactly when we'll release the beta, but we want those of you who are interested in helping us test this new version to know as soon as it is. I have a fixed list of things to get done before I release it and as soon as that list is done and testing shows we've got a reasonably stable version then we'll release.
To get access to this beta version when it becomes available, please email beta@performancedesign.com.au with a short email asking to be added to our beta email list and also let us know what your sCANalyser serial number is (the number on the back of the black box interface).
We may not respond immediately.. give us a few days... we're focused getting through all the outstanding tasks as quickly as possible.
In getting access to the beta version we ask some small favours:
1. You don't talk about the new features publicly for reasons I've outlined above unless of course I've already discussed them publicly.
2. You expect to hit a few bugs. The purpose of a beta is to have you test the software under normal use. This helps us by capturing any use that we didn't anticipate (and thus didn't test). It also gets us feedback on new features before we lock down the final release (so we can tweak any major issues). We'd appreciate it if you report any bugs direct to us at beta@performancedesign.com.au. Please don't talk about them publicly (for the same reasons I outlined above). If we come across an issue that seems like it affects more than one or two people I'll send everyone who signed up for the beta an email describing the issue and what course of action to take.
I hope that's not too bold of me to ask.
I'm working as quickly as I can to get this out to you... I really appreciate your patience. I hope it will be rewarded.
Finally thankyou to everyone who has purchased sCANalyser and also thanks to everyone who has provided feedback.
Cheers
sco
11-16-2005, 12:16 AM
#693
Registered
Join Date: Aug 2003
Location: Brisbane, Australia
Posts: 1,459
Likes: 0
Received 0 Likes
on
0 Posts
Thanks for the prod... an update is definitely in order.
In the last week or so Microsoft released the latest version of their developer tools. I have just upgraded sCANalyser to use those tools. The primary reason for that is to switch to Microsoft serial routines rather than use the third party ones we've been using. I'm hoping this should avoid some of the issues some users have had with certain USB to serial dongles and also solve an occasional crash when shutting down sCANalyser. I'm just testing the upgrade and once this is tested I'll be releasing the beta to those people that asked for access via beta@performancedesign.com.au.
Sorry for the delays. Will post more news as it comes to hand.
Cheers
sco
In the last week or so Microsoft released the latest version of their developer tools. I have just upgraded sCANalyser to use those tools. The primary reason for that is to switch to Microsoft serial routines rather than use the third party ones we've been using. I'm hoping this should avoid some of the issues some users have had with certain USB to serial dongles and also solve an occasional crash when shutting down sCANalyser. I'm just testing the upgrade and once this is tested I'll be releasing the beta to those people that asked for access via beta@performancedesign.com.au.
Sorry for the delays. Will post more news as it comes to hand.
Cheers
sco
11-16-2005, 12:48 AM
#694
Originally Posted by sco
Thanks for the prod... an update is definitely in order.
In the last week or so Microsoft released the latest version of their developer tools. I have just upgraded sCANalyser to use those tools. The primary reason for that is to switch to Microsoft serial routines rather than use the third party ones we've been using. I'm hoping this should avoid some of the issues some users have had with certain USB to serial dongles and also solve an occasional crash when shutting down sCANalyser. I'm just testing the upgrade and once this is tested I'll be releasing the beta to those people that asked for access via beta@performancedesign.com.au.
Sorry for the delays. Will post more news as it comes to hand.
Cheers
sco
In the last week or so Microsoft released the latest version of their developer tools. I have just upgraded sCANalyser to use those tools. The primary reason for that is to switch to Microsoft serial routines rather than use the third party ones we've been using. I'm hoping this should avoid some of the issues some users have had with certain USB to serial dongles and also solve an occasional crash when shutting down sCANalyser. I'm just testing the upgrade and once this is tested I'll be releasing the beta to those people that asked for access via beta@performancedesign.com.au.
Sorry for the delays. Will post more news as it comes to hand.
Cheers
sco
beers
11-16-2005, 01:08 AM
#697
Registered
Join Date: Aug 2003
Location: Brisbane, Australia
Posts: 1,459
Likes: 0
Received 0 Likes
on
0 Posts
Oh, while I think of it.... important info for anyone running V1.1 beta and V1.0
Microsoft has made .NET Framework 2.0 available for download. sCANalyser V1.0/1.1 will run fine if you download this as .NET framework V1.1 and V2.0 can be installed on the same computer. There is no need to uninstall .NET Framework V1.1 (and I recommend that you don't as I have yet to test sCANalyser V1.0/1.1 when only .NET framework V2.0 is installed).
Microsoft has made .NET Framework 2.0 available for download. sCANalyser V1.0/1.1 will run fine if you download this as .NET framework V1.1 and V2.0 can be installed on the same computer. There is no need to uninstall .NET Framework V1.1 (and I recommend that you don't as I have yet to test sCANalyser V1.0/1.1 when only .NET framework V2.0 is installed).
