Rtek Android Rtek feedback
10-04-12, 03:41 AM
#2
for editing the map, since its on a small screen, and using finger touches, it would need a way to move between cells to edit them. Maybe, when editing the cell, you can add a number keypad along with a -/+ to adjust. I can see it looking better on a tablet though with the large screen area. When switching to map view, add in a zoom -/+. Also, uploading maps somehow.
As for Live data view, the way it was in the palm was alright. it would be nice to set an alarm setting to show up on the live view somehow if we hit a predetermined alarm/trigger setting. maybe having a tablet option to view the data in a more streamline way. Such as on the tablets, you can view more data as a graph instead of just numbers.
Colors, we need those
As for Live data view, the way it was in the palm was alright. it would be nice to set an alarm setting to show up on the live view somehow if we hit a predetermined alarm/trigger setting. maybe having a tablet option to view the data in a more streamline way. Such as on the tablets, you can view more data as a graph instead of just numbers.
Colors, we need those
10-04-12, 09:57 AM
#3
I think what you have going on the palm seems to work. Add Touch to Pick cells and/or Arrows to change cells, an adjust up(+) and down(-) button, or type in the value.
Color coded cells might be neat too.
Sample.
I think the live data view is ok on the palm, but it would be neat to add gauges, and red flashing screen and sound for alarm. Additional types of readout, line graphing(as on the palm), bar graphing, digital text(as on the palm), gauges.
The ability to Log features w/o them taking up the screen. Eg. I only want to view boost and AFR, but I want to log Timing, Fuel index, boost index, air temps, rpm, etc...
Looking forward to this!
Color coded cells might be neat too.
Sample.
I think the live data view is ok on the palm, but it would be neat to add gauges, and red flashing screen and sound for alarm. Additional types of readout, line graphing(as on the palm), bar graphing, digital text(as on the palm), gauges.
The ability to Log features w/o them taking up the screen. Eg. I only want to view boost and AFR, but I want to log Timing, Fuel index, boost index, air temps, rpm, etc...
Looking forward to this!
10-04-12, 04:41 PM
#4
i think it would be nice to swipe up and down to change value, that way both small and large changes could be done without having to type in numeric values. swipe motions to move around the map, then select a cell, then use up/down swipes to scroll through values for the cell. select outside the value column to exit back to the map. also be able to select multiple cells to apply % correction or apply single value to all.
10-04-12, 06:25 PM
#5
Yeah, it's an interesting dilemma to be able to move the map around with your finger, but also select multiple cells with your finger. I guess we'll need a "select" button that will stop the map from moving and instead select cells.
10-05-12, 03:29 PM
#7
Another thought, would be to have the menu key at the bottom open up a select range option. then it asks you for the range, say 4k-6k rpm, and then it ask'd you what psi(for MAP tuning) say 10psi-16psi, and then add value to all selected -10 to 10? or an interpolate option. all cells between 4k and 6k and 10 and 16psi get 10 more degrees. or less.
Trending Topics
10-13-12, 07:54 PM
#10
The key to UX/UI design is to be explicit in documenting the user stories or scenarios. Here's an example:
As an RX7 Home Tuner, I need to tune my AFRs to my targets across the RPM range.
As we explore this story we'll see that
As an RX7 Home Tuner, I start with a full throttle pull on the dyno or a flat straight road recording my AFRs.
As an RX7 Home Tuner my full throttle target AFRs will change from 2000 to 8000 rpm; going from 11.7 at 2000 to 12.3 at 3800 and back down to 11.5 by 8000 (all made up for example but the concept is I think correct).
As an RX7 Home Tuner I want to minimize the time and effort required to adjust my fuel at each RPM. Note that the natural response to this is that I can make three or four runs and the RTek software on the android will fine tune my fuel parameters so the AFR curve matches my target AFR curve. If you can do this the fanciness of the individual cell editing becomes irrelevant.
As an RX7 Home Tuner I usually have to move several values at the same time. If I select a range of values from 3200 to 4400 and pull up on the 3500 node the nodes from 3200 to 4400 will also move up as if on a rubber band.
I'm not a skilled enough tuner to know what all the legitimate stories would be. This technique is well established in Scrum by folks like Mike Cohn and Anthony Ulwick's Outcome-Driven Innovation.
When it is clear what jobs the user is trying to perform and how they measure successful execution of the job, the UI design almost manifests all on its own.
We're an all iOS household but will happily get an Android device to retire the Palm! :-D
As an RX7 Home Tuner, I need to tune my AFRs to my targets across the RPM range.
As we explore this story we'll see that
As an RX7 Home Tuner, I start with a full throttle pull on the dyno or a flat straight road recording my AFRs.
As an RX7 Home Tuner my full throttle target AFRs will change from 2000 to 8000 rpm; going from 11.7 at 2000 to 12.3 at 3800 and back down to 11.5 by 8000 (all made up for example but the concept is I think correct).
As an RX7 Home Tuner I want to minimize the time and effort required to adjust my fuel at each RPM. Note that the natural response to this is that I can make three or four runs and the RTek software on the android will fine tune my fuel parameters so the AFR curve matches my target AFR curve. If you can do this the fanciness of the individual cell editing becomes irrelevant.
As an RX7 Home Tuner I usually have to move several values at the same time. If I select a range of values from 3200 to 4400 and pull up on the 3500 node the nodes from 3200 to 4400 will also move up as if on a rubber band.
I'm not a skilled enough tuner to know what all the legitimate stories would be. This technique is well established in Scrum by folks like Mike Cohn and Anthony Ulwick's Outcome-Driven Innovation.
When it is clear what jobs the user is trying to perform and how they measure successful execution of the job, the UI design almost manifests all on its own.
We're an all iOS household but will happily get an Android device to retire the Palm! :-D
10-16-12, 01:07 AM
#11
I don't suppose having the ability to type in cell values rather than simply doing +/- is an option? It would help those setting up timing maps from scratch.
The log-viewing graph output on the palm itself is also fairly hard to view since every parameter is on it own set of axes. Would graphing on one set of axes (ala PL Viewer) be doable? Viewing AFR alone is not useful with comparing directly to RPM, MAP, IAT, injector D/C, etc... It might allow me to tune fuel while I'm out driving around rather than going back home, synching the palm, viewing the data, then changing the maps and heading out for another test drive.
vrracing - would you like to be the scrum master, product owner or a member of the development team?
The log-viewing graph output on the palm itself is also fairly hard to view since every parameter is on it own set of axes. Would graphing on one set of axes (ala PL Viewer) be doable? Viewing AFR alone is not useful with comparing directly to RPM, MAP, IAT, injector D/C, etc... It might allow me to tune fuel while I'm out driving around rather than going back home, synching the palm, viewing the data, then changing the maps and heading out for another test drive.
vrracing - would you like to be the scrum master, product owner or a member of the development team?
12-02-12, 01:39 PM
#13
As an RX7 Home Tuner I want to minimize the time and effort required to adjust my fuel at each RPM. Note that the natural response to this is that I can make three or four runs and the RTek software on the android will fine tune my fuel parameters so the AFR curve matches my target AFR curve. If you can do this the fanciness of the individual cell editing becomes irrelevant.
i cant wait for the android app to be ready... i just got a new pc that doesnt support the old palmOne software and i'm having issues connecting my M100 to my new pc... its such a headache even trying to work with the palm any more... lack of data cables available lack of software support for the palm... not fun
i want to upgrade my primary injectors but the thought of trying to fine tune on my m100 gives me nightmares. im literally waiting for the android app to come out before i do any more upgrades and re-tuning.
Last edited by fc3schick87; 12-02-12 at 01:42 PM.
03-01-13, 09:30 AM
#16
Trunks are for corpses.
Join Date: Nov 2003
Location: St.Pete FL
Posts: 189
Likes: 0
Received 0 Likes
on
0 Posts
Dunno if you guys are still taking suggestions, but the realtime graphs view from the Palm would be good with a couple improvements since we're dealing with limited screen space.
1. Select which graphs to show on the screen independently of which sensors to log
2. Let the user choose the order of the graphs.
This way you can log RPM, Airflow, injector DC, timing, O2/EGT/whatever on the analog input, but not have the analog input pushed off the bottom of the screen by both injectors DC and timings (like it does on the palm currently)
Also, provide two color themes. (I believe Android has two "Holo" themes by defailt, just use those?) One with a light background to overcome glare during the day, and one with a black background for use at night or to save battery on phones and tablets with OLED displays.
1. Select which graphs to show on the screen independently of which sensors to log
2. Let the user choose the order of the graphs.
This way you can log RPM, Airflow, injector DC, timing, O2/EGT/whatever on the analog input, but not have the analog input pushed off the bottom of the screen by both injectors DC and timings (like it does on the palm currently)
Also, provide two color themes. (I believe Android has two "Holo" themes by defailt, just use those?) One with a light background to overcome glare during the day, and one with a black background for use at night or to save battery on phones and tablets with OLED displays.
07-09-13, 06:25 PM
#18
Trunks are for corpses.
Join Date: Nov 2003
Location: St.Pete FL
Posts: 189
Likes: 0
Received 0 Likes
on
0 Posts
09-05-15, 05:06 PM
#22
You couldn't afford it. lol.
My point being, to take the months it would require to write a PC program for it (not counting the months I already put into one), and the few copies I'd sell, I'd have to charge $5000 a copy to even break even. Unfortunately an "interest" and a "market" are two different things..
In the mean time, use the android emulator and bluetooth adapter, which is the closest thing you are going to get to a PC program.
My point being, to take the months it would require to write a PC program for it (not counting the months I already put into one), and the few copies I'd sell, I'd have to charge $5000 a copy to even break even. Unfortunately an "interest" and a "market" are two different things..
In the mean time, use the android emulator and bluetooth adapter, which is the closest thing you are going to get to a PC program.
09-06-15, 02:42 PM
#23
Full Member
You couldn't afford it. lol.
My point being, to take the months it would require to write a PC program for it (not counting the months I already put into one), and the few copies I'd sell, I'd have to charge $5000 a copy to even break even. Unfortunately an "interest" and a "market" are two different things..
In the mean time, use the android emulator and bluetooth adapter, which is the closest thing you are going to get to a PC program.
My point being, to take the months it would require to write a PC program for it (not counting the months I already put into one), and the few copies I'd sell, I'd have to charge $5000 a copy to even break even. Unfortunately an "interest" and a "market" are two different things..
In the mean time, use the android emulator and bluetooth adapter, which is the closest thing you are going to get to a PC program.
Thread
Thread Starter
Forum
Replies
Last Post
LongDuck
1st Generation Specific (1979-1985)
12
10-07-15 08:12 PM
