yes i believe so. thank you for the assistance.
Search found 4 matches
- Wed Mar 04, 2015 3:55 pm
- Forum: Box and application development
- Topic: Generic Raw Telnet Reader - Format of Raw Buffer
- Replies: 5
- Views: 13094
- Mon Mar 02, 2015 5:55 pm
- Forum: Box and application development
- Topic: Generic Raw Telnet Reader - Format of Raw Buffer
- Replies: 5
- Views: 13094
Re: Generic Raw Telnet Reader - Format of Raw Buffer
Actually, the \n terminating character seemed to offset my data as well.
Using no terminating characters seemed to solve this problem.
so one continuous stream of samples.
Using no terminating characters seemed to solve this problem.
so one continuous stream of samples.
- Wed Feb 25, 2015 7:50 pm
- Forum: Box and application development
- Topic: Generic Raw Telnet Reader - Format of Raw Buffer
- Replies: 5
- Views: 13094
Re: Generic Raw Telnet Reader - Format of Raw Buffer
From what i've ascertained, the data is sent in whatever format you have chosen for your acquisition server. in byte format (ie 2 bytes for 16-bit) (4 bytes for 32-bit) in a string of bytes (with no delimiters or spaces) , setting the proper endian format for each byte. with an \n terminating charac...
- Mon Feb 16, 2015 10:35 pm
- Forum: Box and application development
- Topic: Generic Raw Telnet Reader - Format of Raw Buffer
- Replies: 5
- Views: 13094
Generic Raw Telnet Reader - Format of Raw Buffer
I am trying to send an EEG stream over the acquisition server through the 'Generic Raw Telnet Reader' My python servero sends 14 channels of data on one line. (i modified the acquisition ui to accept my 1 line sample count) My question is, what format should this be sent in? I was told in binary, bu...