Since it looks like you’ve never really done a serial terminal with Xojo, I would first get your communications and command structure ironed out using a dedicated terminal (e.g. Teraterm, Coolterm). You can then follow the SFE example @Norman Palardy & @Ulrich Bogun suggested. Something like (but seriously I would just run through the SFE tutorial):
command: ATZ
wait for response ...
command: ATDP
wait for response ...
command: AT@1
wait for response ...
command: ATRV
Once you have the cable talking to a dedicated serial terminal, then I would move to coding the desired commands and response capturing in Xojo. - I would do it this way even if I was seasoned doing serial terminals in XOJO (just until I understood very clearly how to structure the commands and how to expect the responses).
Yes, it is pre-built and in working condition.
From xojo application, when a command is sent over the cable to OBD II port of any car, indicator on the OBD II connector blinks. So command is actively going on the cable. But, no response is received.
Tried with CoolTerm and goSerial Applications … no response received. I ordered a new generic cable and will test again tomorrow
Thanks to all for your help!
@Chakravarthy Cuddapah
Something is not making sense on this whole thread. Here you mentioned that the cable works without problems on Windows but you can’t get it to communicate in XOJO.
Here you say is not working in a MAC
Wouldn’t you think it would be easier to just keep one variable constant instead of trying to change serial terminals and computing platforms?
If it were me I would choose whichever platform it is working on, and then try the more common serial terminals there. As an example, if it works in Windows (with their software) I would try with Coolterm and Teraterm. One was done in XOJO and the other wasn’t… But I would not be jumping platforms left and right just to keep trying, otherwise why not go ahead and try Linux while you are at it.
