Its Not Conecting to get a PID from the ECU...
you need to check the connection between the OBD and the instrument your reading...
cable or wireless...the instrument your reading the message from will indicate when your connected

kind regards kdag

Hi

The message comes up if no protocol replied - so you need to respond to ATSP commands and also the 0100 command.

I use some test code here for 0100 responses (which then cause the message to be cleared) - take note of the protocol defines what headers are used (and if they are turned on or off)

         } else if (checkText.startsWith("0100")) {

               write(HEADER+"4100BE3EB811\n>"); // remember > at end
               //write("7E906410088180010\n>");
               //  write("486B104100BE3EB811C9\n>");
               // write("486B404100BE3CB810F6\n");
         }

Any PID that's unsupported should return 'NO DATA'

eg:

write("NO DATA\n>");

(note no \r at the end of the line after the '>')

Thank you for the info. I will try some changes to my 0100 response. Currently I have it set as "4100E8193012\n>\r".

The ATSP0 and ATSP6 response is set as "OK\n>\r". ATDPN response is "6\n>\r".

I have all unsupported PIDs returning "NO DATA\n>\r" but I was unaware that the "\r" can be a problem.

One other issue I'm having is that Torque seems to be requesting data from the PIDs listed as unsupported in my 0100 response, for example the fuel % trim PIDs. Is this also related to the unnecessary "\r" that I've been using?