Page 1 of 3 123 LastLast
Results 1 to 10 of 23

Thread: Pin # on serial cable on v2 q

  1. #1
    Senior Member restless@westnet.com.au's Avatar
    Join Date
    Aug 2008
    Posts
    199

    Default Pin # on serial cable on v2 q

    HI
    guys im making a cable to connect an AEM 30-2310 inline wideband unit ( no gage ) to a v2
    i gather its the gray serial wire to pin #2 on v2 my question is witch is PIN # 2 do they read from left to right ? 1 to 6 and wich way is the plug held to determine the front ?

    thanks
    Click image for larger version. 

Name:	DSC01597.jpg 
Views:	366 
Size:	991.0 KB 
ID:	14998Click image for larger version. 

Name:	DSC01598.jpg 
Views:	493 
Size:	913.7 KB 
ID:	14999Click image for larger version. 

Name:	DSC01640.JPG 
Views:	331 
Size:	162.4 KB 
ID:	15000

  2. #2
    Joe (Moderator) joecar's Avatar
    Join Date
    Apr 2003
    Posts
    28,403

    Default




    from post #22 of this thread: AEM-wideband-to-FlashScan-V2

  3. #3
    Senior Member restless@westnet.com.au's Avatar
    Join Date
    Aug 2008
    Posts
    199

    Default

    Quote Originally Posted by joecar View Post



    from post #22 of this thread: AEM-wideband-to-FlashScan-V2
    hi joe
    im having trouble getting my v2 to read a friends car that we are doing the AEM UGO wideband in it all works perfect in my car 08 /e38 ls3 my friends in a 011/ l76
    AND IT IS TUNED WITH HP TUNERS will that affect it not wanting to work with my v2 ??





    This has got me FU#$@#$K

    I have down loaded the latest ver 0f both 5.7 and v8 ( I see the pid list in BBX is different NOW you cant search for just the one pid ?by typing it in )
    I have configure the SD card and the v2 memory and the old pid list

    I have up graded the the boot block and the firm ware to the latest ones (last months date ) it says they are both ok

    I found if I deleted all the pids from the v2 and installed new ones one at a time from the NEW BBX LIST GENERIC PIDS AND ECM INHANCED PIDS
    Some of The ones we need work BUT none of the custom pids like AFRATIO-M or INLVTMP will work when you put them in it just says error pid AFRATIO -M unsupported please deselect it
    I spent about 4 hrs putting pids in and taking them out till igot most of the ones needed still some that wont work though

    And the ugo widband is a head #%$%#@ as I'm sure its wired wright and the module under the bonnet blinks the correct lights when you switch on the ign for 30 sec then goes solid green
    ALL SO on the v2 second from the left orange light blinks when the wide band is connected ( stops if you select a different wide band in v2 list )

    But it still says NOT FOUND if you scroll through the list ( not like in my car it brings up the AFR as soon as you get to techedge 2 in the list then says NOT FOUND if you select some other type )

    I have the the comports on 02 WIDBAND AEM UGO AFR ONLY

    AND THE PID WO2AFR1 selected it shows up on the screen but NO read out
    All works fine in my car no problems at all
    But is a problum in my friends car could there be a problem because its tuned with HP ??

  4. #4
    Joe (Moderator) joecar's Avatar
    Join Date
    Apr 2003
    Posts
    28,403

    Default

    No, HPT would not be the reason, but rather not all the _M (_DMA) pids work on all year/ECM/OS combinations.

    Try crossing the wires on pins 1 and 2 (see above diagram).

    Did you read thru this thread: AEM-wideband-to-FlashScan-V2

    Look closely at your serial comms cable and compare to his.

    Which wideband do you have...? And he has a AEM UEGO 30-2310...?

    Then when you get serial wideband working, instead of AFRATIO_M try LAMBDA (if this works then you will need WO2LAM1 also).

  5. #5
    Senior Member restless@westnet.com.au's Avatar
    Join Date
    Aug 2008
    Posts
    199

    Default

    Quote Originally Posted by joecar View Post
    No, HPT would not be the reason, but rather not all the _M (_DMA) pids work on all year/ECM/OS combinations.

    Try crossing the wires on pins 1 and 2 (see above diagram).

    Did you read thru this thread: AEM-wideband-to-FlashScan-V2

    Look closely at your serial comms cable and compare to his.

    Which wideband do you have...? And he has a AEM UEGO 30-2310...?

    Then when you get serial wideband working, instead of AFRATIO_M try LAMBDA (if this works then you will need WO2LAM1 also).
    hi joe

    this guy has the AEM UEGO 30-2310 the inline one with no gage it has a white wire and a brown wire for analog and a GRAY wire for serial

    white i'm finding that is confusing FOR ME is the diagram from MR prick shows 3 wires going into the v2 i don't understand how this works as its supposed to be serial just using the rs232 plug on top of the v2

    i have a techedge 2 in my car ( works great ) no gage and it only has a cable going to the rs232 plug on top of the v2 ( nice and neat )
    we don't want wires going everywhere on this install as it has to be unplugged frequently

    i will try the wiring as per mr pricks diagram to see if it works,
    is it a serial connection or an analog connection when its wired that way ???? so i can config the v2
    witch pid should i load into the v2 ? analog or serial WO2AFR1 (thats the one that works with my techedge 2 )

    i know that the AFRATIO-M is the ECU commanded read out and has nothing to do with the wideband


    i see now with the new ver software you don't get all the lambda and QRI ect pids come up on the v2 screen when load the WO2AFR1 PID

  6. #6
    Joe (Moderator) joecar's Avatar
    Join Date
    Apr 2003
    Posts
    28,403

    Default

    mr.prick's diagram shows wiring for both analog and serial... just ignore the analog wiring.


    so you will need to connect like this:
    Connect like this:
    AEM grey wire -> V2 RJ11 pin 1
    AEM black wire -> V2 RJ11 pin 5

    The black wire also goes to vehicle/battery ground.
    If that doesn't work (the orange LED does not flash at all), then try connecting the AEM grey wire to V2 RJ11 pin 2...

    see this:
    See post #19 here: DCE-to-DCE

    V2 RJ11 pin 2 = Tx (on DCE devices Tx receives data)...

    [ DTE is as labelled; DCE is opposite of as labelled ]
    On DCE devices: Tx receives data, Rx transmits data.
    i.e. the AEM grey wire should go to V2 RJ11 pin 2 (the Tx pin) since V2 is DCE.
    Last edited by joecar; May 8th, 2013 at 12:54 PM.

  7. #7
    Joe (Moderator) joecar's Avatar
    Join Date
    Apr 2003
    Posts
    28,403

    Default

    Also see this:

    Quote Originally Posted by Blacky View Post
    If you see the orange LED (second from the left) on FlashScan's keypad flashing, then that indicates serial data is being received by FlashScan.
    That means the physical connection is probably working correctly.

    In that case, let it receive data for about 5-10 seconds, then select the option:
    F1: Scan Tool -> F3 Scan Options -> F1 Save Trace File.

    Then using EFILive_Explorer, copy the saved trace file to your PC and email it to me at paul@efilive.com (include a link to this thread so I know what its about).
    I will try to figure out why FlashScan is not recognizing the device.

    P.S. When using the FlashScan option:
    F1: Scan Tool -> F2: Data Logging -> F3: Display WO2
    there are a number of hotkeys that you may find useful:

    1. Backspace will cycle through all wideband options, make sure you have the correct wide band selected.
    2. Enter will cycle through the different display format options.
    3. For innovate the "0" key will perform a free air calibration.

    Regards
    Paul

  8. #8
    Senior Member restless@westnet.com.au's Avatar
    Join Date
    Aug 2008
    Posts
    199

    Default

    well i have connected gray wire to pin 2 on v2

    and black wire from cars ground to pin 5 on v2

    there no black wire coming from the uego , only brown neg and white pos
    the orange light on the v2 ( second from the left ) blinks when its connected this way
    but with v2 config to AEM UEGO and comport wideband selected and WO2AFR1 it still says NOT FOUND ??

  9. #9
    Senior Member restless@westnet.com.au's Avatar
    Join Date
    Aug 2008
    Posts
    199

    Default

    well now i have bigger problums

    after downloading some pid in to my v2 with the latest ver of v8 and 5.7 boot block firmware etc
    i took it out to MY car to make sure it was working before i tried it out on the other car we are trying to get wideband working on

    when i plugged in to my ute it started to throw codes straight up no driving just sitting still with ign on , i lost some of the dash and the gearbox control will only read and go in 2nd even i change gears with the stick
    pids are
    TCM U0073
    ECM PO575
    ECM PO 700
    ECM PO703
    ECM PO856
    ECM P2544
    ECM U0073

    when i try to clear them it says no dtc to clear ??
    what's the fix for this one
    cheers

  10. #10
    Joe (Moderator) joecar's Avatar
    Join Date
    Apr 2003
    Posts
    28,403

    Default

    I notified Paul.

Page 1 of 3 123 LastLast

Similar Threads

  1. serial cable
    By stick100 in forum General
    Replies: 1
    Last Post: April 22nd, 2012, 10:42 PM
  2. ALDL (GM OBD1) cable with 16 pin connector ,USB
    By wahenn2002 in forum EFILive V4
    Replies: 3
    Last Post: January 22nd, 2012, 06:10 PM
  3. Serial Port Pin Outs
    By Tre-Cool in forum FlashScan V2
    Replies: 6
    Last Post: September 21st, 2011, 11:25 PM
  4. pin-outs for V2 OBD2 cable
    By carl0s in forum FlashScan V2
    Replies: 1
    Last Post: June 27th, 2011, 05:51 AM
  5. LM1 through the 9 pin serial...
    By rubbersidedown in forum FlashScan V2
    Replies: 0
    Last Post: August 2nd, 2008, 03:00 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •