Results 1 to 8 of 8

Thread: Serial wideband input disappearing from Channels once I start scanning...

  1. #1
    Potential Tuner
    Join Date
    Nov 2018
    Location
    Pike County, IN
    Posts
    1

    Serial wideband input disappearing from Channels once I start scanning...

    Is anyone else having this issue with VCM Scanner? I am having problems with both the stable release (4.10.5) and the latest beta(4.11.482) and the issue only started when I updated from the last stable version.
    I have my AEM wideband set up for serial input, and have the channel as such in VCM Scanner. The PID shows up on the channel list when scanner is opened, but disappears as soon as I press the "Start Scanning" button. Any help/insight is greatly appreciated.

  2. #2
    Tuner in Training
    Join Date
    Dec 2019
    Posts
    39
    Not a fix, but sometimes it takes me several start/stop/start scanning tries before serial input is recognized. Frustrating as hell, especially when you're trying to start logging on the fly.

  3. #3
    Advanced Tuner
    Join Date
    Aug 2014
    Location
    Central, LA
    Posts
    738
    Check your device manager for bluetooth com ports. If they are present, disable/uninstall them.

  4. #4
    Potential Tuner
    Join Date
    Jul 2022
    Posts
    1
    Quote Originally Posted by sevinn View Post
    Check your device manager for bluetooth com ports. If they are present, disable/uninstall them.
    I was banging my head against the wall for quite awhile trying to get this problem fixed! Problems disappeared after disabling the bluetooth com ports!

    Thanks for this!

    Sorry about reviving this thread but I felt that the feedback was warranted

  5. #5
    Advanced Tuner
    Join Date
    Aug 2014
    Location
    Central, LA
    Posts
    738
    Quote Originally Posted by Captainfalcon View Post
    I was banging my head against the wall for quite awhile trying to get this problem fixed! Problems disappeared after disabling the bluetooth com ports!

    Thanks for this!

    Sorry about reviving this thread but I felt that the feedback was warranted
    Feedback is always welcome. Thanks for replying!

  6. #6
    Senior Tuner 04silverado6.0's Avatar
    Join Date
    Sep 2021
    Location
    Kentucky
    Posts
    1,036
    I have issues with analog input with the pro link. Usually unplugging and connecting the cable during a active log will fix the issue. Obviously ruins the log but you shouldnt be going after good data until the wb is reading.

  7. #7
    i have the same issue.
    i have a surface pro using a serial input and a lc1

    60% of the time it works great logs fine gives great lamda EQ error
    but the rest of the time i want to start smashing stuff because it's visible when i connect to the car and soon as i start to log it disappears.
    people say turn off the laptop and reset it with everything then reconnect

    some say tune on LM programmer and make sure the laptop sees the LC1 ( it connects to the LC1 every time

    as i am logging in lambda there is no adjusting to be done on the lc 1

    there are no polling speeds to adjust Aswell in the channels

    can't turn of the Bluetooth coms as the mouse uses it

    when the lc1 is connect its displaying com port 7

  8. #8
    i have the same issue with a LC2, there needs to be some improvements to the serial device, or even better LET US CHOSE THE COM PORT?!?! its not that hard and choosing a com port will solve all the issues with VCM scanner chosing a wrong comport "automaticly".