3.023 v
8 key on number keyboard block, in Num Lock mode - not enters 8, just show/hide help block.
Sensors and input: not saves to project: Analog inputs pullup/down and filters, VSS, PPS and tolerances, switches: clutch/brake and builtin swithches mode, latches switch, iat clt safe and calibrations and so on…
What do you mean that sensor and input no saves to the project ? Do you mean the user names for above sensors ?
sensor input assigments not saves.
- new project
- fill some data, tired, save, close soft
- start soft, load project - all what i assign - in default values
my project start.emub3 (56.7 KB)
Yes, there is a problem with saving user names in 3.023.
It will be fixed in next version
V3 3.024
problem with VVT strange angle in log file
24042024-1.emub (146.0 KB) my V2 soft
20240424_1906_38.zip (2.2 MB) log V2
20240425_0835_49.emublog3 (6.6 MB) log V3
20240425_0905_09.emub3 (58.1 KB) my V3 soft
scope_2024426_820.emubscp3 (650 Bytes)
Please make also scope. I will take a look tommorow.
Scope attached in previous post.
Assuming the solenoids werent powered during taking this scope you should enter
angle 448 for CAM1 and 181 for CAM2.
Looks very good
Thank you, i will try.
Dear Jadzwin,
I dont understand, please explane me if possible why change angle when change version to V3? onV2 all work correct.
I change angle to your variant, but changes in drive small different.
Cam2 angle in map and log different
I can’t speak to the reason’s why as well as Jadzwin can. But I had to change both CAM offset’s in V3 from what I had set in V2. The existing trigger options in V3 are different than V2 which I’m guessing drives the need to change the offsets. to get accurate numbers for offsets I ran the car and monitored the CAM angle numbers while setting the cam offset values to 0. After I got that all sorted I also had to change the CAM PID min and max values to get the cams to respond and track the targets correctly (still some work to be done). Again, Jadzwin can likely explain “why” better. But it is the same experiece I had when moving values over from V2 to V3. May CAM offset values were wildly different due to changes in the trigger settings, is my thought.
Thank you Dear! i will try to change all
Long story short. In v2 the reference angle wasnt absolute and depends on some factors like firstvtrigger tothe, etc.
In V3 the reference angle is absolute angle, and what is the most important you can read it from the scope.
In v3 it is more logical and correct.
2 Likes
Problem connecting/reading configuration from ecu
Version 3.025
-
After turning off the ignition and turning it back on, the software does not reconnect with the ecu. Disconnecting the usb cable and reconnecting does not solve the problem. Only after restarting the software is the connection established.
-
After connecting to the ecu does not read values from 2D/3D maps (all these maps have default values) All input/output settings, trigger configurations, etc. are read. The engine starts and runs normally.
Edit: After restarting the system, everything works normally now
Using software version 3.025.
When I try to append a data log none of the logs from my EDL-1 SD card appear.
Opening a log.
Appending a log.
Open window shows .BG3 file type.
Append window shows .BGG3 file type.
V325 crashed on exit. I have crashdumb saved. Should I email it?
Yes please to v3@ecunaster.com
1 Like
I’ve noticed that after few power cycles (I was sorting out cranking) the V3 client hangs. Cannot kill it, need to reboot Windows. I’m working on a VM, so this might impact the scenario though. Happened few times already.