99 Blazer, T16-003, Toshiba 2595CDT

Help
Johann8384
2005-05-15
2013-04-24
  • Johann8384

    Johann8384 - 2005-05-15

    I posted this in general discussion by mistake, should have been here.

    Can anyone tell me what's going on here:

    diag_l2: diag_l2_init called
    diag_l2: diag_l2_open MET16 subid 0 L1proto 4 called
    diag_l0_muleng: open subinterface 0 protocol 4
    diag_l0_muleng: Device /dev/ttyS0 opened, fd 3
    diag_os: setup: device fd 3 proto 4 flags 0xa0
    diag_l2: diag_l2_startCommunications fd 3 L2proto 4 type 0 baud 10400 target 0x6a src 0xf1 called
    diag_l2_j1850: diag_l2_j1850_startcomms conn 8553db0
    diag_l2: diag_l2_StartComms returns 0x8553db0
    diag_l2: diag_l2_ioctl 0x8553db0 cmd 8225
    diag_l2: diag_l2_msg 0x8553db0 0xfef953b0 called
    diag_l2_j1850: diag_l2_j1850_send 0x8553db0 msglen 2 called
    diag_l2_j1850: dial_l2_j1850_send sending 5 bytes to L1
    diag_l0_muleng: getflags fd 3 proto 4 0xa0
    diag_l0_muleng: device fd3 send 5 bytes protocol 4 0x68 0x6a 0xf1 0x1 0x0
    diag_10_muleng: device fd 3 sending to ME device: 0x38 0x02 0x05 0x68 0x6a 0xf1 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xcb
    diag_l2: diag_l2_send returns 0
    diag_l2_j1850: diag_l2_j850_int_recv offset 0
    diag_l0_muleng: fd3 recv upto 1024 bytes timeout 250, rxlen 0 offset 0
    diag_l2: diag_l2_request returns 0x0, err -8
    diag_l2: diag_l2_close 3 called
    diag_l2: diag_l2_init called
    diag_l2: diag_l2_open MET16 subid 0 L1proto 8 called
    diag_l2: diag_l2_closelink 3 called
    diag_l0_muleng: device fd 124654048 info 3 closing
    diag_l0_muleng: open subinterface 0 protocol 08
    diag_l0_muleng: Device /dev/ttyS0 opened, fd 3
    diag_os: setup: device fd 3 dt 806ax64 speed 19200 bits 8 stopbits 1 parity 3
    diag_l0_muleng: getflags fd 3 proto 8 flags 0xa0
    diag_l2: diag_l2_startCommunications fd 3 L2proto 4 type 0 baud 10400 target 0x6a src 0xf1 called
    diag_l2_j1850: diag_l2_j1850_startcomms conn 8554618
    diag_l2: diag_l2_StartComms returns 0x8554618
    diag_l2: diag_l2_ioctl 0x8554618 cmd 8225
    diag_l2: diag_l2_msg 0x8554618 0xfef953b0 called
    diag_l2: diag_l2_send 0x8554618 msg 0xfef953b0 msglen 2 called
    diag_l2_j1850: diag_l2_j1850_send 0x9554618 msd 0xfef953b0 len 2 called
    diag_l2_j1850: diag_l2_j1850_send sending 5 bytes to L1
    diag_l0_muleng: getflags fd 3 proto 8 flags 0xa0
    diag_l0_muleng: device fd 3 send 5 bytes protocol 8 0x61 0x6a 0xf1 0x1 0x0
    diag_l0_muleng: device fd 3 sending to ME device: 0x38 0x04 0x05 0x61 0x6a 0xf1 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xc6
    diag_l2: diag_l2_send returns 0
    diag_l2_j1850: diag_l2_j1850_int_recv offset 0
    diag_l0_muleng: fd 4 recv upto 1024 bytes timeout 250, rxlen 0 offset 0
    diag_l2: diag_l2_request returns 0x0,err -8
    diag_l2: diag_l2_close 3 called
    diag_l2: diag_l2_init called
    diag_l2: diag_l2_open MET16 subid 0 L1proto 2 called
    diag_l2: diag_l2_closelink 3 called

     
    • Johann8384

      Johann8384 - 2005-05-25

      looks like this project is kinda dead. I found out the problem, the id in my T16-003 is 25 not 22 or 38 as I was originally advised.

       

Log in to post a comment.