Rtek Android Please
03-13-12, 01:56 PM
#26
^ RX7PlViewer.jar is a Java app.....
Logging and tuning is what I do most. The low pixel density of the Palm makes it a little inconvenient to review logged data with any degree of precision. I typically copy the log files to an SD card and review them on a PC. But it would be nice to have slightly more sophisticated graphing tools available on the device talking to the RTek.
With respect to tuning, I'd like to see a toggled feature that interpolates values between two cells, resulting in a smooth transition between the two numbers.
(A little off the topic, but I'd like to be able to specify tire size, diff ratio, gear ratio, and known peak whp value from the dyno (alternatively, vehicle weight + frontal area for street tuning) to plot an estimated hp or torque curve from the rpm vs. time data.)
Logging and tuning is what I do most. The low pixel density of the Palm makes it a little inconvenient to review logged data with any degree of precision. I typically copy the log files to an SD card and review them on a PC. But it would be nice to have slightly more sophisticated graphing tools available on the device talking to the RTek.
With respect to tuning, I'd like to see a toggled feature that interpolates values between two cells, resulting in a smooth transition between the two numbers.
(A little off the topic, but I'd like to be able to specify tire size, diff ratio, gear ratio, and known peak whp value from the dyno (alternatively, vehicle weight + frontal area for street tuning) to plot an estimated hp or torque curve from the rpm vs. time data.)
03-13-12, 02:11 PM
#27
I didn't write it. It was written by a customer.
Yeah with more modern connections like mountable file system, sd cards and internet, I hope to make it much easier to get data in other formats.
Not sure what you mean. The ECU already interpolates between cells. There is no additional resolution that could be set....unless you mean you want to define two to four points in the map (that have at least one cell between them), set those points and have the software calculate and set the cells in between?
Ok, now you are pushing it.. lol. Lets get some basic functionality going before we get to feature requests..
Logging and tuning is what I do most. The low pixel density of the Palm makes it a little inconvenient to review logged data with any degree of precision. I typically copy the log files to an SD card and review them on a PC. But it would be nice to have slightly more sophisticated graphing tools available on the device talking to the RTek.
Ok, now you are pushing it.. lol. Lets get some basic functionality going before we get to feature requests..
04-07-12, 04:31 PM
#32
I started with the ECU setup screen... Took a bit longer than I expected, but I have injector config and staging RPM working. This means the communication foundation is working well and development *should* start going a little faster now....maybe...
I'm hoping to have the first PC boards for the BT dongle ordered be the end of next week.
I'm hoping to have the first PC boards for the BT dongle ordered be the end of next week.
04-08-12, 10:20 PM
#33
Senior Member
I started with the ECU setup screen... Took a bit longer than I expected, but I have injector config and staging RPM working. This means the communication foundation is working well and development *should* start going a little faster now....maybe...
I'm hoping to have the first PC boards for the BT dongle ordered be the end of next week.
I'm hoping to have the first PC boards for the BT dongle ordered be the end of next week.
04-09-12, 10:23 AM
#34
I started with the ECU setup screen... Took a bit longer than I expected, but I have injector config and staging RPM working. This means the communication foundation is working well and development *should* start going a little faster now....maybe...
I'm hoping to have the first PC boards for the BT dongle ordered be the end of next week.
I'm hoping to have the first PC boards for the BT dongle ordered be the end of next week.
damn bro, props!
And to think my Gf has me trying to convince me to get a smart phone, and an android OS at that... guess i'll have too now...
but a few questions...
1. Are you pretty much porting the exact software for the palm, or re writing it all from scratch?
2. I know the answer is you're writing it all from scratch
, does this mean we can design a few necessity from the get go? mainly imputing numbers in to the timing/fuel tables. select more then one box at a time, jump .1 1 or 10 increments...?3. how can i help?
4. why won't you let me help?
04-09-12, 11:26 AM
#35
Yes it's working. When you load the program, it will automatically try to connect to the last connected BT device. Takes about 3-4 seconds to connect up, then maintains the connection.
Yes I'm starting essentially from scratch. Even though java and C are similar, how you interact with the OS is completely different.
Yeah, now's the time to get your feature requests in. I definitely want to improve the map input interface as well as the logging/playback to take advantage of the higher res screens.
Well as soon as the bluetooth hardware is out, I'd like people to start testing on different devices... I can't afford to buy all kinds of devices so I'll need to rely on others for testing. Unfortunately the Android emulator that comes with the SDK doesn't support bluetooth at all. so my program won't even run on it. I have to do all the dev on the device itself.
I may try to pick up a cheap android tablet for testing.
Yes I'm starting essentially from scratch. Even though java and C are similar, how you interact with the OS is completely different.
Yeah, now's the time to get your feature requests in. I definitely want to improve the map input interface as well as the logging/playback to take advantage of the higher res screens.
Well as soon as the bluetooth hardware is out, I'd like people to start testing on different devices... I can't afford to buy all kinds of devices so I'll need to rely on others for testing. Unfortunately the Android emulator that comes with the SDK doesn't support bluetooth at all. so my program won't even run on it. I have to do all the dev on the device itself.
I may try to pick up a cheap android tablet for testing.
04-09-12, 12:07 PM
#38
https://www.google.com/search?hl=en&...w=1280&bih=933
googled some, just steal the **** out of them
04-09-12, 04:57 PM
#39
I just picked up a Vizio VTAB1008 from Costco for $189. Bluetooth was a little temperamental, but once I got it paired, it works. This is running 2.2, but it already asked me if i wanted to update to 3.2, but I wanted to do the 2.2 tests first as it's one less than the 2.3 on my phone.
04-09-12, 08:07 PM
#40
sounds sweet, how much code does it take for the rteks to work with bluetooth and communicate with the tablet, i know the android software side is a BIG TASK. or will there just be a serial to bluetooth adapter that works for all current /new rteks? you said something about a dongle... just curious if we'll be sending our ecus back in, or just buy the extra part
04-10-12, 12:13 AM
#42
Feature Requests
a.) Allow selecting / logging of > 9 parameters so the RTek and 'Roid don't hose each other. i.e., fix this bug.
b.) Fix the AFM temp units. This issue.
c.) Expand the rpm range for AWS, 6PI, and/or VDI outputs so I can activate my shift light at >> 8160 rpm, etc.
d.) Allow a range of values for the rev limiter, rather than just a single setting of 9200.
e.) Interpolate between cells or select multiple and raise by the same or gradually scaled amount, as suggested above.
f.) Implement a smoothing function for the data plots.
g.) Export feature to dump the data directly into a CSV
h.) Estimate and plot power and torque curves from RPM and time data, given a known whp value (i.e. scaling factor).
b.) Fix the AFM temp units. This issue.
c.) Expand the rpm range for AWS, 6PI, and/or VDI outputs so I can activate my shift light at >> 8160 rpm, etc.
d.) Allow a range of values for the rev limiter, rather than just a single setting of 9200.
e.) Interpolate between cells or select multiple and raise by the same or gradually scaled amount, as suggested above.
f.) Implement a smoothing function for the data plots.
g.) Export feature to dump the data directly into a CSV
h.) Estimate and plot power and torque curves from RPM and time data, given a known whp value (i.e. scaling factor).
04-10-12, 12:24 AM
#43
Wow, I totally missed ever seeing bug a.
b is some mismatch caused by a change in the way we formatted the temp. The viewer is not in sync with the palm. Now that I'm learning java, I'll be able to make updates to the log viewer and get that fixed.
C and D are features for the ECU itself, not the logger app.
E I think you or someone mentioned before..def on the list.
F you mean for the maps?
G definitely
H Sounds good.
b is some mismatch caused by a change in the way we formatted the temp. The viewer is not in sync with the palm. Now that I'm learning java, I'll be able to make updates to the log viewer and get that fixed.
C and D are features for the ECU itself, not the logger app.
E I think you or someone mentioned before..def on the list.
F you mean for the maps?
G definitely
H Sounds good.
04-10-12, 12:51 AM
#44
Yeah, I can repro at will.
If the PLViewer's X Y Scatter plot function could be fixed, I would be excited. But before we get to that, yes, finish the 'Roid app first.
Indeed.
No, I mean the data plots, when displayed at high resolution (well, at least better than the Palm's) are frequently noisy. Much of it is due to parameters being internally represented as discrete values inside the ECU (e.g. IAT, AFM, timing advance). Some sensors are more noisy than others (e.g. MAP, some widebands). And a lot of it is just plain electronic s/n issues. Would be nice to have a toggle on the data charts to turn on smoothing globally or for a given parameter.
Indeed.
No, I mean the data plots, when displayed at high resolution (well, at least better than the Palm's) are frequently noisy. Much of it is due to parameters being internally represented as discrete values inside the ECU (e.g. IAT, AFM, timing advance). Some sensors are more noisy than others (e.g. MAP, some widebands). And a lot of it is just plain electronic s/n issues. Would be nice to have a toggle on the data charts to turn on smoothing globally or for a given parameter.
04-10-12, 03:01 PM
#46
Full Member
iTrader: (11)
Join Date: Dec 2009
Location: Saint Louis, MO
Posts: 71
Likes: 0
Received 0 Likes
on
0 Posts
I just ordered the 2.1 upgrade a month ago or so, and I have ICS on my Asus tablet if you want some extra testing. I assume just a 12v wire to power the dongle? or something else?
or a use for the cig lighter hah?
or a use for the cig lighter hah?
Last edited by Dunnhopen; 04-10-12 at 03:05 PM.
04-11-12, 11:07 AM
#48
Full Member
iTrader: (11)
Join Date: Dec 2009
Location: Saint Louis, MO
Posts: 71
Likes: 0
Received 0 Likes
on
0 Posts
Any idea what kind of price points you are looking at? Are you going to do an app on the app store?
I do like the idea of the bluetooth being powered by the cig lighter so I can turn it of and on at well, rather then leave it on all the time.
I do like the idea of the bluetooth being powered by the cig lighter so I can turn it of and on at well, rather then leave it on all the time.
