I'd say port linux for mobile version (android) before going for mac!Originally Posted by steveo
I'd say port linux for mobile version (android) before going for mac!
i've looked at doing that. it's not happening. a mac one could happen in probably an hour. android would take a serious effort, and i'd have to maintain two UIs, one that works on a tiny device and one that doesn't... (not to mention porting qserialport to android, which would be a pain in the ass)
It would be nice to flash from an android.. could have radio,tuning, and logging all on one screen and built into dash ;)
Well, see how many have macs and want to try it. I've never even used one outside of iPhone.
Thanks a lot for your help.
I can get the details tonight, but its a fairly recent release of Ubuntu
Can't hijack my wife's windows laptop anymore to use Tunercat/Datamaster, so hopefully I can get this working on Linux as I have a machine I can leave in the car with me.
me either; but the port should be easyI've never even used one outside of iPhone.
im sure we can figure that out, thenits a fairly recent release of Ubuntu
played around a bit with this 'graphing range' problem
decided i'd just bite the bullet and add a min/max range to the definition file, but with automatic calculation if you don't specify anything.
When I get home this evening I can make a quick write up.
A few things right off the top of my head.
You shouldn't have to install any driver for the ftdi on linux. It will show up as something like /dev/ttyUSB0 or something similar. To access this device your going to have to add yourself to the dialup group. I'll look into what exactly it is in ubuntu.
You will want to download qt 5.6, then download the $ EEHack source. Once you have the source file extracted navigate to that folder in a terminal window, command promt in Windows speak.
Once there, you'll need to run qmake from the downloaded qt 5.6.
For example.
Type something like. .
/home/me/qt/5.6/bin/qmake
Once that's done, type "make" in the terminal window
these paths are all wrong though
Should get you started
1994 LT1/4L60E Formula
Maybe let's do a binary release for 64 bit linux. The license of eehack permits a statically compiled build which should be portable enough.
qt5.6 should be out soon but distributions will take like a year to pick it up
Last edited by steveo; 03-15-2016 at 10:57 PM.
Hi steveo
just loaded 4.5b4
Just been playing with the graphing pane.
I feel it needs a cursor similar to Datamaster so when you select a record in the graph it can alter the playback to point to the selected record.
I find i'm following the graph & then have to manually set the record to where i'm looking so i can single step through it.
Also Analyzer: CL Performance: BLM Average is still showing 180-192 where my blm's are 120-130
Another thought:
How hard would it be to work out what gear a manual was in?
Excellent Stuff. Keep it coming.
Mitch
Last edited by Terminal_Crazy; 03-16-2016 at 01:25 AM.
please post your datalog so I can look into this blm thing. I'm not suprised its broken.
I know what you mean with the graph and log events. I removed the click to move feature as the old one didn't work with the new graph window (it was really hacky) but i plan to add it back in with a cursor.
manual gear selection? actually kinda easy. I had it working in my last aldl tool. it actually showed you sync points so you had a double-clutch gauge that got you perfect sync. clutch slip could be measured too with a coarse resolution. it would require a properly calibrated vss though. This is low priority.
Last edited by steveo; 03-16-2016 at 03:51 AM.
Data Log: http://www.sand-hill.freeserve.co.uk...og_048n.eedata
ScreenShot: http://www.sand-hill.freeserve.co.uk...zer_Screen.jpg
Mitch
ahh.. that analyzer
fixed the problem, thanks!
and holy crap you have a lot of knock in cruising range
im not finding many bugs right now, so i started working on the graphing cursor thing.
one thing is im going to have the cursor move on playback, but if there's new data, you'll still have to manually replot. i dont want to real-time graph the incoming data, it's too slow
also going to use a double click to move the graph position, otherwise it'll move every time you try to scroll the graph (since clicking is also used for scrolling)
any thoughts?
Yes.
That's why i've been very cautious since getting this motor back on the road.
I've not heard any knock or found any sign of detonation on the plugs yet.
I think it's the high compression :-).
When i tested it i was getting 230-240 psi on each cylinder. I think it's just ringing like a bell with the Mac Mid tubes sitting over the sensor.
Old sensor was retorqued when i read overtightening was bad for them. I have also replaced it with new without any change.
That was why i was playing with the adjustable resistor mod on the knock sensor last week.
I have since started reducing the knock sensor attack rate as you suggested until i can find a happy medium. I didn't want to just switch it off like most posts suggest.
Car runs pretty awesome. I thought i was giving it some abuse on that data log with it going sideways on a couple of occasions. When i looked at the log i've only hit 5k.
It also runs out of road very quickly :-) (Ours are a bit smaller than yours).
Mitch
Posting Permissions
Reply With Quote
Bookmarks