Support for reading extended Motion Tracker Specification data (eMTS), logging to file and magnetic field mapping

[herrfrei]

get_calib_data.py: new file to record raw data uses by the magnetic field mapper
mtdef.py: ReqEmts = 0x90 and Emts = 0x91 added to class MID
mtdevice.py: changes to MTDevice class
corrected CRC computation error when extended length is used (needed for eMTS data) in read_msg()
added log file writing in read_msg()
added a member logfile and a function set_logfile() to set it
added function ReqEmts() to request the eMTS data

[fcolas]

@herrfrei many thanks for your contributions. But could you please split all three of them (eMTS, logging, and magnetic field mapping) into separate pull requests?
Furthermore, I couldn't find a reference to eMTS in the version of the documentation of the protocol that I have (MT Low Level Communication Documentation from Dec. 2012). Do you have a newer version or is it just undocumented?

[herrfrei]

Franzis, I'll do my best to split them up. The eMTS is not documented, but
needed for magnetic field mapping. So I needed to read the eMTS data and
store it in a file.

Herr Frei

2016-01-19 11:32 GMT+01:00 Francis Colas [email protected]:

@herrfrei https://github.com/herrfrei many thanks for your
contributions. But could you please split all three of them (eMTS, logging,
and magnetic field mapping) into separate pull requests?
Furthermore, I couldn't find a reference to eMTS in the version of the
documentation of the protocol that I have (MT Low Level Communication
Documentation from Dec. 2012). Do you have a newer version or is it just
undocumented?

—
Reply to this email directly or view it on GitHub
#21 (comment)
.

[fcolas]

@herrfrei Are you still interested to contribute?

[fcolas]

@herrfrei Ping?