Jump to content

Rozsko

Members
  • Posts

    232
  • Joined

  • Last visited

Posts posted by Rozsko

  1. 9 hours ago, Ming said:

    hi did you manage to resolve the misfire issue? i ve the same issue.

    The car just runs fine. I gave up on the misfire at idle. It is still missing couple of beats here and there, but I gave up chasing it. Anything I checked just took me into a rabbit hole.

  2. Hey Guys,

    Just checking real quick. As per the latest PCLink release notes, there should be a Nitrous control section in the motorsports menu.

    In the sample G5 map, I can surely see that, but I can't see that in my G4x upgraded map with the latest firmware.

    Is the nitrous control availble only in G5? In the release ntoes, I see couple of items clearly marked for Voodoo only, but nitrous controls is NOT one of them.

    Thanks,

    Béla

  3. Hey Guys,

    I see there is a new version of PCLink supporting G5 and the G5 product page is also updated with some details.

    I assume that means the new ECU is ready for sale, but with a quick google search I could not find it yet advertised.

    When is it going to be available for real?

    Thanks,

    Béla

  4. On 7/3/2023 at 3:26 PM, DenisAlmos said:

    If any one wants to know, I tried to solder the power and communication wires of 3 USB cables to allow communication and charge on my Note8 and SpeeedStudio CAN analyzer but it didn't work.

    I'm using the OEM Samsung OTG adapter delivered with the smartphone for now and have no solution on how to display and charge in the same time.

    I am using an HP USB-C mini dock (7PJ38AA) with my Samsung Tab S7. It works like charm. There are some odd cases when I have to powercycle the dock, but 80% of the times it just works fine.

  5. 34 minutes ago, Adamw said:

    I dont think there is a firm release date yet and I have no idea where price will be.  PC Link will be basically the same as G4X and G4X maps should load straight in.

    Thanks Adam

  6. Hey Guys,

    Just wanted to ask if there is anything you can share on G5.

    Planned release date, price range, is it going to use the same PCLink that the g4x, will g4x maps be compatible or atleast portable to g5,... ?

    Thanks,

    Bela

  7. 45 minutes ago, koracing said:

    I see this pretty commonly on busy screens with the Link and my own i5 HP Probook 650 G1 laptop (12G ram, 1TB SSD, Intel onboard HD Graphics 4600) -- also still has a 9 pin serial port on the back.  I think this is also a comms bandwidth issue.  I get my best connection speeds by using a Belkin active USB cable (5 meters long is the shortest active one you can buy) -- even if no extension is needed, it seems to boost the signals.  If I need to see data with a fast sample rate - I just use the internal logger on the link.  The link PC logging max sample rate is 40Hz versus 1000Hz on the internal logger.

    Thanks Kris,

    I think I understand what you are sayin, but I tend not to believe the same. Today I tested it with two more HP Elitebooks, one has a Ryzen CPU the other one has a gen 8 i5 Intel (both are single GPU). Both (with the out of the box fullhd layout) performed the same crappy way as my Asus and the Surface laptop using the same full hd default layout does that 40Hz thing and does not drop below 25 when watching the logging screen. I can definitely say and agree with you on that, the more gauges you have on the screen or the more data you display on a time plot, the worse it gets. And you are absolutely right that the internal logging is capable of 1000Hz, though you can't see and observe the logged values realtime and the other thing to be honest I don't really mind a 4-10Hz display rate in the application, but I tend to believe that this is not on the display rate, but the data acquisition rate too and results in quite some squary (if that is a word) waveforms.

  8. Hey Guys,

    Sorry, but I can't really give up on this problem.

    I played with the drivers but nothing really helps. To recap, here is my current config: Asus TUF laptop with Ryzen 5 6400H with builtin AMD Radeon (TM) graphics + an nVidia GeForce GTX1650Ti.

    • I downgraded the driver for the nVidia to the oldest (2020 march I think) --- did not help
    • upgraded to the latest nVidia driver --- did not help
      • AMD released a new driver late last year and the claim they improved the OpenGL performance roughly with 50%, so I updated to the latest driver --- guess what, did not help.
    • I disabled the Radeon,then the nVidia - did not help
    • left both enabled and selected one then the other in the Windows Graphics settings (System - Display - Graphics; and btw I use Win11 now). I checked in PCLink's about that it was using one or the other respectively, depending on which one was selected in the Control panel. --- unfortunately did not help.
    • I installed nVidia's Nsight Systems that is a tool you can use to benchmark the GPU performance of any application, but I wasn't able to see any bottlenecks.
    • Finally, I installed PCLink on my work laptop that is a Surface laptop 4 and that one was running with the same performance that you described Adam. Right away the display rate was around 50Hz after the connection was established and when I started PC logging, it never went below 25Hz, rather it was more around 30. Even the operation/responsiveness of PCLink was sensibly better, meaning for example when you filter a list of parameters to a specific one, it does that much quicker then on my ASUS.

    Is this something we could debug with a developer? I am pretty sure many of us would appreciate if this could be improved.

    Or anyone, any other suggestion to try?

    Thanks a lot,

    Béla

  9. 3 hours ago, Adamw said:

    Try dropping the write interval to 500.

    That might have done the trick.

    With 500ms, it had about 1 fault per 5 mins, so I dropped it top 100ms and logged the value for more then 10 mins and no fault during that time.

    This means then I guess, when there is a collision, then RealDash just drops the frame and waits for the next event, causing the 2sec fault threshold being violated randomly.

    Is there a way to control this 2 sec threshold somehow? At least for on/off CAN DIs? 

  10. 7 hours ago, Adamw said:

    Do you have any errors showing in the CAN tab of the runtimes screen when that happens?  What else is connected on the same bus and what bit rate are you running?  I vaguely remember seeing this before in our car but I dont remember what it was.  

    Will need to check on the CAN tab.

    The bus is 500kbps speed and has a 22 channel AEM module, 2 x series AEM gauges, a Link CAN lambda and an ECUmaster egt modul and an AEM x series CAN display.

  11. Hey Guys,

    Quick question for you.

    Just received my Seeedstudio CAN adapter and hooked it up to my G4x. To start with, I used the provided sample xml, rd file and configured the streams as explained. All pieces of the puzzle seem to get together nicely as I see data coming from the ECU displayed in RealDash and the button works as well that is set to CAN DI1, even if I set it to on/off toggle button.

    On the other hand, CAN DI1 is showing a Fault status time to time. Not repeated at exactly the same time interval, it is kind of random but usually takes 10-30 seconds to get a fault which then is reset in about a second. I don't have latching configured which means it just replicates what is received over CAN.

    Now, I read in the G4x help file, if CAN data is not received for 2 seconds, then a fault is set, but the xml has a writeInterval parameter set to 1000ms, so I assume, that should not be the case.

    So, do you have any idea what can cause the fault status on a CAN DI parameter?

    Thanks,

    Béla

  12. Hi Guys,

    Bringing this old topic back with some updates I've just done, just in case anyone else is running into the same issue.

    So after a long time I started to mess with my car again and the next project is RealDash. Now that means I have to realign quite a bit of my gauge setup. Namely, I will get rid of the AEM X-series gauges that currently feed to the ECU through CAN and I will simply connect their sensors to the 22 channel AEM CAN modul. This means that I am running out of Analog Volt based inputs on the CAN module with the currently applied workaround.

    So what I have done is that I moved the three IAT sensors back to Analog 9, 10 and 11 to transmit the values in resistance.

    Then I created a math channel for each of them with the following formula to calculate the Voltage from the resistance: "5/(a+2200)*a" (2200 is the ohm value of the pull-up resistor in the AEM CAN modul) (https://1drv.ms/u/s!Ale4oyMCOgLThYwSd5VyWMOJ8WsRBQ ), and I feed these math channels into the GP Temp inputs with the same Voltage based calibration table I used before (https://1drv.ms/u/s!Ale4oyMCOgLThYwUXrauN8NfPe-i1w)

    So now, I have enough Analog Voltage inputs on the AEM CAN modul to connect the oil pressure, the fuel pressure and the oil temp sensors.

    Cheers,

    Béla

  13. 3 minutes ago, Electredge said:

    what resolution are you using? and how much ram do your laptops have? have you tried a new page with just the time plot running? if so does it do the same thing? 

    resolution is FHD, ram is 16GB, and no, I did not try the timeplot on an otherwise empty page, but I can do that.

  14. I just realized I promised to get back on this, and I never got to (so far).

    Since then I got a new laptop (Asus TUF AMD ryzen 5 CPU), and this is still a problem.

    No matter if I disable the nVidia or the AMD video card, the refresh rate is going down to below 10Hz whenever I have a timeplot running for about a minute or two.

    I just can't understand why PCLink is not utilizing the hardware resources available. The CPU utilization never goes above 20%. No matter what I do in it. GPU utilization is 0%.

    Is there way to improve this somehow? Are you guys planning to introduce 64bit processing?

  15. On 4/25/2022 at 10:48 PM, dingdongdrift said:

    just wanted to update, i leaned out the high vacuum high RPM cells even more so now it just pops and bangs and shoots flames all the time. got tired of trying to give it the correct amount of throttle to get it to pop. but holy cow the pops are loud now, i flinch almost everytime now lol. 

    So when you say leaned out, what is the actual lambda you reaching and are you still at -5 degree ignition?

    I tried this pop and bang thing myself too, but can't get any serious noise out of the exhaust. I would say it does more of a grousing but nothing loud.

    Thanks

  16. 9 hours ago, randolph said:

    Hello guys,

    we have a sti 08 hatchback and wonder if anyone here has manage to install the wrx v10 g4x plug in successfully on them

    link states that this ecu will not fit the gr chassis,

    but just checking if anyone has had any luck with it or not,

    pics for attention.

    thank you

    00A5CEB0-87DD-4A52-813A-918B969086F4.jpeg

    This was something I was planning to try as I don't see a reason why you couldn't make it work, however the pinout will be different from a 07 STi, so you will need to repin the header connectors or have an adapter built. If you enable the Subaru CAN on one of the CAN channels then that should work with the WRX107 as well.

  17. On 1/16/2022 at 8:18 AM, Adamw said:

    Weve got a couple of fairly significant motorsport functions added in the next release and these still need more track testing before public release.  May still be a month away yet.  

    Hey Adam,

    Any good news on this?

    Thanks

×
×
  • Create New...