oh weird man. that's a portability issue
FLT_MIN and FLT_MAX are defined in c++ as floating point's min and max value.
i wonder if there's a QT definition of them
try #include <limits.h> in that file or something
edit: i looked and linux has them in <float.h>. i committed changes for both those issues (and a few other minor ones)
Last edited by steveo; 03-09-2016 at 05:34 AM.
one bug im still working out is what happens when you switch between various logs, or delete logs. sometimes the dashboard is de-synchronized as a result (momentarily, until you move to another record) but the actual tabs with lists of data are still alright. deleting logs can also do odd things, but so far no crashing. just thought i'd mention in case anyone noticed... i am aware of those bugs.
I'm still getting the errorOriginally Posted by steveo
Code:In file included from datalog_packet.h:7:0, from datalog_element.h:5, from datalog_element.cpp:3: datalog_definition.h:37:6: error: use of enum ‘def_special_t’ without previous declaration enum def_special_t; ^ datalog_element.cpp:6:69: warning: unused parameter ‘parent_in’ [-Wunused-parameter] datalog_element::datalog_element(int offset_in, datalog_definition *parent_in) { ^ Makefile:16928: recipe for target 'datalog_element.o' failed make: *** [datalog_element.o] Error 1
1994 LT1/4L60E Formula
sorry, i missed that one. try now. the unused parameter thing should be gone too.
so this obd-ii stuff is bugging me.
going back from the datastream at mode5, i've found there are well over a hundred bytes of memory, some of it in sequential blocks, used for storing OBD-II input, and not much else.
many of them don't have any direct addressing outside of the datastream. can you find what actually dumps data into them?
here's a nearly-complete block list of memory used in datastream output for msg5:
004A-0055
0057-005B
005D-0061
0063-0069
006A-007A
1926-193A
193D-193E
1941-1950
check out the code at E984:
if we want some 'unused' ram to use for hacking the t-side this might be a good place to get it. even corvette guys wouldn't know the code is missing.Code:E984 B6 19 2B LE984: ldaA L192B E987 9A 4A oraA l_004A_unused E989 B7 19 2B staA L192B E98C B6 19 2C ldaA L192C E98F 9A 4B oraA l_004B_unused E991 B7 19 2C staA L192C E994 B6 19 2D ldaA L192D E997 9A 4C oraA l_004C_unused E999 B7 19 2D staA L192D E99C B6 19 2E ldaA L192E E99F 9A 4D oraA l_004D_unused E9A1 B7 19 2E staA L192E E9A4 B6 19 2F ldaA L192F E9A7 9A 4E oraA l_004E_unused E9A9 B7 19 2F staA L192F E9AC B6 19 30 ldaA L1930 E9AF 9A 4F oraA l_004F_unused E9B1 B7 19 30 staA L1930 E9B4 13 79 80 07 brclr L0079, #%10000000, @0 E9B8 FE 19 31 ldX L1931 E9BB 08 incX E9BC FF 19 31 stX L1931 E9BF 13 73 80 07 @0 brclr L0073, #%10000000, @1 E9C3 FE 19 33 ldX L1933 E9C6 08 incX E9C7 FF 19 33 stX L1933 E9CA 13 6F 80 07 @1 brclr L006F, #%10000000, @2 E9CE FE 19 35 ldX L1935 E9D1 08 incX E9D2 FF 19 35 stX L1935 E9D5 13 70 01 07 @2 brclr L0070, #%00000001, @3 E9D9 FE 19 37 ldX L1937 E9DC 08 incX E9DD FF 19 37 stX L1937 E9E0 13 70 40 07 @3 brclr L0070, #%01000000, @4 E9E4 FE 19 39 ldX L1939 E9E7 08 incX E9E8 FF 19 39 stX L1939 E9EB 13 70 80 07 @4 brclr L0070, #%10000000, @5 E9EF FE 19 3B ldX L193B E9F2 08 incX E9F3 FF 19 3B stX L193B E9F6 13 71 04 07 @5 brclr L0071, #%00000100, @6 E9FA FE 19 3D ldX L193D E9FD 08 incX E9FE FF 19 3D stX L193D EA01 13 71 08 07 @6 brclr L0071, #%00001000, @7 EA05 FE 19 3F ldX L193F EA08 08 incX EA09 FF 19 3F stX L193F EA0C 13 71 20 07 @7 brclr L0071, #%00100000, @8 EA10 FE 19 41 ldX L1941 EA13 08 incX EA14 FF 19 41 stX L1941 EA17 13 71 80 07 @8 brclr L0071, #%10000000, @9 EA1B FE 19 43 ldX L1943 EA1E 08 incX EA1F FF 19 43 stX L1943 EA22 13 72 02 07 @9 brclr L0072, #%00000010, @10 EA26 FE 19 45 ldX L1945 EA29 08 incX EA2A FF 19 45 stX L1945 EA2D 13 72 08 07 @10 brclr L0072, #%00001000, @11 EA31 FE 19 47 ldX L1947 EA34 08 incX EA35 FF 19 47 stX L1947 EA38 13 72 20 07 @11 brclr L0072, #%00100000, @12 EA3C FE 19 49 ldX L1949 EA3F 08 incX EA40 FF 19 49 stX L1949 EA43 13 72 80 07 @12 brclr L0072, #%10000000, @13 EA47 FE 19 4B ldX L194B EA4A 08 incX EA4B FF 19 4B stX L194B EA4E 13 73 02 07 @13 brclr L0073, #%00000010, @14 EA52 FE 19 4D ldX L194D EA55 08 incX EA56 FF 19 4D stX L194D EA59 13 73 08 07 @14 brclr L0073, #%00001000, @15 EA5D FE 19 4F ldX L194F EA60 08 incX EA61 FF 19 4F stX L194F EA64 39 @15 ret
i will look into it more but the code's interactions with these bytes might reveal quite a bit more.
compiled and working
flashed and logged this morning, all good so far.
Last edited by fbody_Brian; 03-09-2016 at 05:42 PM.
1994 LT1/4L60E Formula
im glad; but im going to break it againcompiled and working
the whole 'speed packet' thing leads me to believe this entire api is a bit broken.
i want to go back to my memory-address driven model that i conceived earlier.
luckily it's not a complete rewrite...
Few little things so far, on the datalog main tab for Spark adv and KR, I'm assuming that there should bed a degree symbol, but I'm seeing � instead.
also, on the analysis cruising AFR, I'm not sure what's going on, but I'm getting no data in the MAF AFR below 31 AFGS. Not sure if it's not lining up, or the data just isn't making it there.
I've attached the log
1994 LT1/4L60E Formula
found the problem. i typo'd and wrote "map" instead of "maf" in the wideband analyzer for that axis.also, on the analysis cruising AFR, I'm not sure what's going on, but I'm getting no data in the MAF AFR below 31 AFGS. Not sure if it's not lining up, or the data just isn't making it there.
the degree symbol doesn't have any trouble with windows, but i'll drop it in the definition file and just write 'deg' instead, it's easier.on the datalog main tab for Spark adv and KR, I'm assuming that there should bed a degree symbol, but I'm seeing � instead.
thanks for that log. very helpful. i can test the hell out of it. especially nice to have something with wideband data to test the analyzer.I've attached the log
can you tell me your wideband settings?
Posting Permissions
Reply With Quote
Bookmarks