Issue with Markers from COM port

Back

Issue with Markers from COM port

Author	Message
jcappsiv	jcappsiv posted 6 Years Ago Topic Details Share Topic
Group: Forum Members Posts: 4, Visits: 13	Hi I am communicating with a fNIRS device via COM port and it seems that using inquist or the serial port monitortool to send bytes my device always detects it as different byte... and sometime it changes.... I'll send bytes of 251 and it registers as 230 or some other number. I went back and checked it wasn't my settings... as my e-prime programs send markers just fine. Then I checked inquist via another computer... same issue. Any ideas? Thanks, John
	Reply Like 38
Dave	Dave posted 6 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 12K, Visits: 98K	+x jcappsiv - Friday, November 9, 2018 Hi I am communicating with a fNIRS device via COM port and it seems that using inquist or the serial port monitortool to send bytes my device always detects it as different byte... and sometime it changes.... I'll send bytes of 251 and it registers as 230 or some other number. I went back and checked it wasn't my settings... as my e-prime programs send markers just fine. Then I checked inquist via another computer... same issue. Any ideas? Thanks, John Doing some testing, there seems to be an issue as soon as the highest bit in the byte sent is set. I.e. values between 0 (decimal; 00000000 as 8 bit binary value) and 127 (decimal; 01111111 as 8 bit binary value) are sent correctly, but as soon as the eigth bit is set, i.e. from 128 (decimal; 10000000 as 8 bit binary value) on, things get weird, although I'm not yet sure why. Would that correspond to what you're seeing or are you getting something else?
	Reply Like 39
jcappsiv	jcappsiv posted 6 Years Ago ANSWER Post Details Share Post
Group: Forum Members Posts: 4, Visits: 13	+x Dave - Friday, November 9, 2018 +x jcappsiv - Friday, November 9, 2018 Hi I am communicating with a fNIRS device via COM port and it seems that using inquist or the serial port monitortool to send bytes my device always detects it as different byte... and sometime it changes.... I'll send bytes of 251 and it registers as 230 or some other number. I went back and checked it wasn't my settings... as my e-prime programs send markers just fine. Then I checked inquist via another computer... same issue. Any ideas? Thanks, John Doing some testing, there seems to be an issue as soon as the highest bit in the byte sent is set. I.e. values between 0 (decimal; 00000000 as 8 bit binary value) and 127 (decimal; 01111111 as 8 bit binary value) are sent correctly, but as soon as the eigth bit is set, i.e. from 128 (decimal; 10000000 as 8 bit binary value) on, things get weird, although I'm not yet sure why. Would that correspond to what you're seeing or are you getting something else? I checked, it was a loose cable for things getting weird. However,I can verify the bit problem- I only really now see 128 or 0 nothing else. Is there any way to fix this issue>?
	Reply Like 39
Dave	Dave posted 6 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 12K, Visits: 98K	+x jcappsiv - Thursday, November 15, 2018 +x Dave - Friday, November 9, 2018 +x jcappsiv - Friday, November 9, 2018 Hi I am communicating with a fNIRS device via COM port and it seems that using inquist or the serial port monitortool to send bytes my device always detects it as different byte... and sometime it changes.... I'll send bytes of 251 and it registers as 230 or some other number. I went back and checked it wasn't my settings... as my e-prime programs send markers just fine. Then I checked inquist via another computer... same issue. Any ideas? Thanks, John Doing some testing, there seems to be an issue as soon as the highest bit in the byte sent is set. I.e. values between 0 (decimal; 00000000 as 8 bit binary value) and 127 (decimal; 01111111 as 8 bit binary value) are sent correctly, but as soon as the eigth bit is set, i.e. from 128 (decimal; 10000000 as 8 bit binary value) on, things get weird, although I'm not yet sure why. Would that correspond to what you're seeing or are you getting something else? I checked, it was a loose cable for things getting weird. However,I can verify the bit problem- I only really now see 128 or 0 nothing else. Is there any way to fix this issue>? Sorry, to clarify: You only get either 128 or nothing, regardless of what byte you actually send? I'm asking because that does not seem to match with what I've been seeing, which -- to reiterate -- was: Bytes up to and including 127: Working fine. Bytes >= 128: Some funny results. If you're indeed only getting either 128 or 0, then I would surmise there may still be an issue with the cable or connector.
	Reply Like 39