MSefi.com read only forum (Jan.15,2018)

This is very interesting.

I have a datalogger running on an mbed. I should be able to connect to it over a network interface using a android tablet. Do you have interface code that actually pulls data from the MS? I have the protocol but do not know how to make this work for the smartphone/tablet ...

I don't recall. Between S and Q... One is board revision and one is code variant.

time to code some If () statements related to the above information.

I just thought about this for two seconds and forgot the "Q" sends back the code variant. Ahh now I have new ideas...

Phil, Do you have any documentation on the query command? Is it buried in the base code or .ini file?

I don't recall reading of that function. I am already changing the code for MSII extra since the outpc is different byte length.

Fixed my bugs. Everything is working well now. I am going to try and run some boards. I started a new thread in the expansion board section.

viewtopic.php?f=67&t=37342

Just a quick update. I changed some code and now have things working. Sort of...

I can generate an .frd file that will convert from TS. I am getting a few extra bytes on the end of my header that create parsing problems for the MS outpc string. I am getting so close now. Just the fact that it will ...

Eureka!

I think you just solved my problem. I didn't realize the two bytes were required on each read cycle loop. I thought they were just tagged in the header...

I am in format heck.

If I send a hex designation it recognizes as two separate bytes. Therefore my header is 166 byes long instead of 83. Yeah, that kinda screws up the offset count. At least I now know what the problem is.

On to find a solution...

I cheated a bit and copied the header line from a frd file created in TS. Here is my 83 byte group. I added line breaks and spaces for clarity.

0x46 0x52 0x44 0x00 0x00 0x0 0x00 0x01 0x4b 0x61
0xf1 0x63 0x4d 0x53 0x49 0x49 0x20 0x52 0x65 0x76
0x20 0x32 0x2e 0x38 0x38 0x30 0x30 0x30 0x20 0x20 ...

Ok I am making progress. If I change the extension of my txt file to .log I can see all the data in the binary viewer. Its all there and lines up perfectly with the slider set to 112.

However, I can not import into TS or MLV. I tried the convert binary log (.frd or .ms3) and this did not work. I ...

I never noticed the binary log viewer before. I think this will help tremendously.

I will report back after I have tried a few ideas for the code.

You have been most helpful. maybe there will be enough interest in this project to do a run of boards.

Best Regards,

jamie

Phil,

I will try to see if some of those other functions will work. I am coding in C. I am using a development board using the NXP LPC series microcontroller. Its pretty powerful for its size and has lots of easily configurable serial ports to connect lots of devices. The protoboard has an online ...

There is nothing wrong with using the binary values. I just don't know how to code writing the raw data. I agree its inefficient. However, the step of writing to the SD card from my micro controller is the slow step in the process. I get almost 20Hz when every thing is running.

right now, I poll ...

Phil, I am bringing this topic back up. Can you make a suggestion for the data format. Here are my choices (pasted below) using a printf() function. I have been writing as a decimal or integer. I have all of my functionality working except for logging the MS outpc in a recognizable format.

Thank ...

And my lack of understanding has been brought to light.

I see exactly what you are saying. I have a working dash display and I had to work hard to get the data in a character format for display readout. When I first started coding the display project all I got was gibberish in the graphic ...

Phil,

I generate a .csv that imports into Excel. Here is a sample of my output taken from the stim. The call is for runtime variables using "a,0,6". the captured format is binary although I can easily switch this to hex as well. The last three are the XYZ axes from an accelerometer. I am also ...

Phil,

I tried to setup a format. Can you make a few clarifications for me?

The string output is in hex? I am currently logging in binary. I can switch easily.

There appears to be no delimiter between bytes when I look at the file. This makes it appear a bit jumbled. Any suggestions?

The "next ...

I just completed the first version of a micro-SD card datalogger for MSII. My output file is currently a CSV of the 113 byte string output. I saw that TunerStudio is capable of the file conversion process. Can you provide some file format guidelines to import the data from binary numbers?

Thanks.