Csafe_pm_get_forceplotdata

[old] Daren C · Post by **[old] Daren C** » September 9th, 2005, 4:18 am

Hi, all. Me again! My current problem is with CSAFE_PM_GET_FORCEPLOTDATA in order to recover the points to plot on the force curve. I never seem to get more than the first part of the curve, points of data, even though I'm calling the method repeatedly. According to another thread on the topic, CSAFE_PM_GET_FORCEPLOTDATA will return up to 32 points each time, and it should be possible to accumulate the whole set (up to 144 points) by repeated calls. However, my first call returns 32 points, and subsequent calls return 0, so I'm not getting the whole code. Here's the code I'm using at the moment, followed by example output: <table width='95%' cellspacing='1' cellpadding='3' border='0' align='center'><tr><td><div class='genmed'>CODE</div></td></tr><tr><td class='code'><div> string splotdata = ""; if (bEndOfDrive) { splotdata = "End of drive. " + CurrentSPM.ToString() + "SPM. Recovering plot data...\n"; // we've completed the drive, so let's recover the force curve. uint nPointsInPlot = 0x0; uint nPointsReturned = 0xFF; int [] ForcePlotPoints = new int[256]; cmd_data_size = 0; cmd_data[cmd_data_size++] = (uint)CSAFE.CSAFE_SETUSERCFG1_CMD; cmd_data[cmd_data_size++] = 0x03; cmd_data[cmd_data_size++] = (uint)CSAFE.CSAFE_PM_GET_FORCEPLOTDATA; cmd_data[cmd_data_size++] = 0x01; cmd_data[cmd_data_size++] = 0x20; // read data points until there are none left to read. while (0 < nPointsReturned) { ecode = tkcmdsetCSAFE_command(0, cmd_data_size, cmd_data, ref rsp_data_size, rsp_data); if (0 == ecode) { nPointsReturned = rsp_data[4]; splotdata += " Recovered " + nPointsReturned.ToString() + " points\n"; for( uint i = 0; i < nPointsReturned; i+=2) { splotdata += " ForcePlotPoints[" + nPointsInPlot.ToString() + "] = " + (rsp_data[5+i]).ToString("x") + " + " + (rsp_data[6+i] << 8).ToString("x") + "\n"; ForcePlotPoints[nPointsInPlot++] = (int)(rsp_data[5+i] + (rsp_data[6+i] << 8)); } } } Console.WriteLine(splotdata); }</div></td></tr></table> Output: <table width='95%' cellspacing='1' cellpadding='3' border='0' align='center'><tr><td><div class='genmed'>CODE</div></td></tr><tr><td class='code'><div> End of drive. 30SPM. Recovering plot data... Recovered 32 points ForcePlotPoints[0] = 8 + 0 ForcePlotPoints[1] = 16 + 0 ForcePlotPoints[2] = 16 + 0 ForcePlotPoints[3] = 32 + 0 ForcePlotPoints[4] = 3a + 0 ForcePlotPoints[5] = 41 + 0 ForcePlotPoints[6] = 41 + 0 ForcePlotPoints[7] = 43 + 0 ForcePlotPoints[8] = 47 + 0 ForcePlotPoints[9] = 4c + 0 ForcePlotPoints[10] = 4b + 0 ForcePlotPoints[11] = 4b + 0 ForcePlotPoints[12] = 4e + 0 ForcePlotPoints[13] = 4e + 0 ForcePlotPoints[14] = 51 + 0 ForcePlotPoints[15] = 55 + 0 Recovered 0 points End of drive. 25SPM. Recovering plot data... Recovered 32 points ForcePlotPoints[0] = 19 + 0 ForcePlotPoints[1] = 19 + 0 ForcePlotPoints[2] = 20 + 0 ForcePlotPoints[3] = 27 + 0 ForcePlotPoints[4] = 2f + 0 ForcePlotPoints[5] = 32 + 0 ForcePlotPoints[6] = 32 + 0 ForcePlotPoints[7] = 38 + 0 ForcePlotPoints[8] = 3e + 0 ForcePlotPoints[9] = 42 + 0 ForcePlotPoints[10] = 44 + 0 ForcePlotPoints[11] = 45 + 0 ForcePlotPoints[12] = 45 + 0 ForcePlotPoints[13] = 47 + 0 ForcePlotPoints[14] = 49 + 0 ForcePlotPoints[15] = 4b + 0 Recovered 0 points End of drive. 22SPM. Recovering plot data... Recovered 32 points ForcePlotPoints[0] = 19 + 0 ForcePlotPoints[1] = 19 + 0 ForcePlotPoints[2] = 25 + 0 ForcePlotPoints[3] = 29 + 0 ForcePlotPoints[4] = 2f + 0 ForcePlotPoints[5] = 31 + 0 ForcePlotPoints[6] = 31 + 0 ForcePlotPoints[7] = 34 + 0 ForcePlotPoints[8] = 35 + 0 ForcePlotPoints[9] = 38 + 0 ForcePlotPoints[10] = 3a + 0 ForcePlotPoints[11] = 3a + 0 ForcePlotPoints[12] = 3c + 0 ForcePlotPoints[13] = 3c + 0 ForcePlotPoints[14] = 3e + 0 ForcePlotPoints[15] = 3e + 0 Recovered 0 points End of drive. 21SPM. Recovering plot data... Recovered 32 points ForcePlotPoints[0] = 1a + 0 ForcePlotPoints[1] = 1a + 0 ForcePlotPoints[2] = 29 + 0 ForcePlotPoints[3] = 32 + 0 ForcePlotPoints[4] = 39 + 0 ForcePlotPoints[5] = 39 + 0 ForcePlotPoints[6] = 3d + 0 ForcePlotPoints[7] = 40 + 0 ForcePlotPoints[8] = 43 + 0 ForcePlotPoints[9] = 43 + 0 ForcePlotPoints[10] = 44 + 0 ForcePlotPoints[11] = 46 + 0 ForcePlotPoints[12] = 48 + 0 ForcePlotPoints[13] = 48 + 0 ForcePlotPoints[14] = 48 + 0 ForcePlotPoints[15] = 49 + 0 Recovered 0 points End of drive. 23SPM. Recovering plot data... Recovered 32 points ForcePlotPoints[0] = 21 + 0 ForcePlotPoints[1] = 21 + 0 ForcePlotPoints[2] = 36 + 0 ForcePlotPoints[3] = 45 + 0 ForcePlotPoints[4] = 4d + 0 ForcePlotPoints[5] = 4d + 0 ForcePlotPoints[6] = 4f + 0 ForcePlotPoints[7] = 50 + 0 ForcePlotPoints[8] = 54 + 0 ForcePlotPoints[9] = 54 + 0 ForcePlotPoints[10] = 5d + 0 ForcePlotPoints[11] = 67 + 0 ForcePlotPoints[12] = 72 + 0 ForcePlotPoints[13] = 7c + 0 ForcePlotPoints[14] = 7c + 0 ForcePlotPoints[15] = 84 + 0 Recovered 0 points End of drive. 26SPM. Recovering plot data... Recovered 32 points ForcePlotPoints[0] = 18 + 0 ForcePlotPoints[1] = 36 + 0 ForcePlotPoints[2] = 36 + 0 ForcePlotPoints[3] = 77 + 0 ForcePlotPoints[4] = 8b + 0 ForcePlotPoints[5] = 99 + 0 ForcePlotPoints[6] = 99 + 0 ForcePlotPoints[7] = 9f + 0 ForcePlotPoints[8] = a0 + 0 ForcePlotPoints[9] = a4 + 0 ForcePlotPoints[10] = aa + 0 ForcePlotPoints[11] = ac + 0 ForcePlotPoints[12] = b2 + 0 ForcePlotPoints[13] = b9 + 0 ForcePlotPoints[14] = b8 + 0 ForcePlotPoints[15] = bb + 0 Recovered 0 points End of drive. 28SPM. Recovering plot data... Recovered 32 points ForcePlotPoints[0] = 31 + 0 ForcePlotPoints[1] = 31 + 0 ForcePlotPoints[2] = 52 + 0 ForcePlotPoints[3] = 6b + 0 ForcePlotPoints[4] = 72 + 0 ForcePlotPoints[5] = 79 + 0 ForcePlotPoints[6] = 83 + 0 ForcePlotPoints[7] = 8b + 0 ForcePlotPoints[8] = 9d + 0 ForcePlotPoints[9] = a5 + 0 ForcePlotPoints[10] = a6 + 0 ForcePlotPoints[11] = aa + 0 ForcePlotPoints[12] = b3 + 0 ForcePlotPoints[13] = b4 + 0 ForcePlotPoints[14] = b7 + 0 ForcePlotPoints[15] = ba + 0 Recovered 0 points End of drive. 28SPM. Recovering plot data... Recovered 32 points ForcePlotPoints[0] = 26 + 0 ForcePlotPoints[1] = 3a + 0 ForcePlotPoints[2] = 4b + 0 ForcePlotPoints[3] = 58 + 0 ForcePlotPoints[4] = 5d + 0 ForcePlotPoints[5] = 61 + 0 ForcePlotPoints[6] = 6a + 0 ForcePlotPoints[7] = 79 + 0 ForcePlotPoints[8] = 84 + 0 ForcePlotPoints[9] = 91 + 0 ForcePlotPoints[10] = 9c + 0 ForcePlotPoints[11] = a6 + 0 ForcePlotPoints[12] = af + 0 ForcePlotPoints[13] = b6 + 0 ForcePlotPoints[14] = b9 + 0 ForcePlotPoints[15] = bc + 0 Recovered 0 points </div></td></tr></table> As you can see, there are different stroke rates, so there should be different numbers of points, I'm sure. Thanks once again for any help.

[old] mlyons · Post by **[old] mlyons** » September 9th, 2005, 8:42 am

Daren, There was a bug fix to the force plot data command back in Beta Rev 88 Build 9. So any Beta release Build 10 or newer should be working properly. I verified proper operation on Build 15 this morning (this is the Beta release available on the C2 website now). Cheers and thanks again. Mark

[old] Daren C · Post by **[old] Daren C** » September 9th, 2005, 9:09 am

<table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><div class='genmed'>QUOTE(mlyons @ Sep 9 2005, 01:42 PM)</div></td></tr><tr><td class='quote'>Daren, There was a bug fix to the force plot data command back in Beta Rev 88 Build 9. So any Beta release Build 10 or newer should be working properly. I verified proper operation on Build 15 this morning (this is the Beta release available on the C2 website now). Cheers and thanks again. Mark </td></tr></table> I'm using Revision 88 Build 15, just checked by restarting the PM3. Does my code logic appear correct, above?

[old] haboustak · Post by **[old] haboustak** » September 9th, 2005, 9:56 am

<table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><div class='genmed'>QUOTE(Daren C @ Sep 9 2005, 08:09 AM)</div></td></tr><tr><td class='quote'> cmd_data_size = 0; cmd_data[cmd_data_size++] = (uint)CSAFE.CSAFE_SETUSERCFG1_CMD; cmd_data[cmd_data_size++] = 0x03; cmd_data[cmd_data_size++] = (uint)CSAFE.CSAFE_PM_GET_FORCEPLOTDATA; cmd_data[cmd_data_size++] = 0x01; cmd_data[cmd_data_size++] = 0x20; </td></tr></table> What's the 0x01 for? I haven't used the FORCEPLOTDATA command myself, but I found the description in rev010 of the documentation. It seems that byte 0 of the command is the response length (e.g. 0x20). I don't see that the PM3 is expecting a length prefix on the command, which would make the length prefix of the USERCFG1_CMD 0x02. Mike

[old] mlyons · Post by **[old] mlyons** » September 9th, 2005, 10:12 am

Daren, I looked at your code sample...it's a little difficult to say whether it's right or wrong. Let me suggest the following...instead of only collecting force plot data at the end of the drive, try collecting continuously to see if more data is available. Also, don't terminate your collection based on receiving 0 data bytes back from the PM3, but terminate at the beginning of the drive. The data is collected from the beginning to the end of the drive. It is available for reading via the force plot command immediately (e.g., during the drive) and is not reset until the catch at the beginning of the next drive. I've used the SDK APIDemo application to repeatedly sample the the force plot data and store it to file. Everything appears to work as I expect. Mark

[old] Daren C · Post by **[old] Daren C** » September 9th, 2005, 10:16 am

<table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><div class='genmed'>QUOTE(haboustak @ Sep 9 2005, 02:56 PM)</div></td></tr><tr><td class='quote'><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><div class='genmed'>QUOTE(Daren C @ Sep 9 2005, 08:09 AM)</div></td></tr><tr><td class='quote'> cmd_data_size = 0; cmd_data[cmd_data_size++] = (uint)CSAFE.CSAFE_SETUSERCFG1_CMD; cmd_data[cmd_data_size++] = 0x03; cmd_data[cmd_data_size++] = (uint)CSAFE.CSAFE_PM_GET_FORCEPLOTDATA; cmd_data[cmd_data_size++] = 0x01; cmd_data[cmd_data_size++] = 0x20; </td></tr></table> What's the 0x01 for? I haven't used the FORCEPLOTDATA command myself, but I found the description in rev010 of the documentation. It seems that byte 0 of the command is the response length (e.g. 0x20). I don't see that the PM3 is expecting a length prefix on the command, which would make the length prefix of the USERCFG1_CMD 0x02. Mike </td></tr></table> The 0x01 is the number of data bytes following for the command. This is the same format I use for setting the splits up, for example (CSAFE_PM_SET_SPLITDURATION): <table width='95%' cellspacing='1' cellpadding='3' border='0' align='center'><tr><td><div class='genmed'>CODE</div></td></tr><tr><td class='code'><div> cmd_data[cmd_data_size++] = (uint)CSAFE.CSAFE_SETUSERCFG1_CMD; cmd_data[cmd_data_size++] = 0x07; // 7 bytes of data to follow cmd_data[cmd_data_size++] = (uint)CSAFE.CSAFE_PM_SET_SPLITDURATION; cmd_data[cmd_data_size++] = 0x05; // 5 bytes of data to follow cmd_data[cmd_data_size++] = 0x80; // 0 = time, 128 (0x80) = distance cmd_data[cmd_data_size++] = 0xF4; // distance byte 0 cmd_data[cmd_data_size++] = 0x01; // distance byte 1 cmd_data[cmd_data_size++] = 0x00; // distance byte 2 cmd_data[cmd_data_size++] = 0x00; // distance byte 3 </div></td></tr></table> Certainly, if I change the length of CSAFE_SETUSERCFG1_CMD's data to 0x02 and remove the 0x01 my PM3 displays an error.

[old] Daren C · Post by **[old] Daren C** » September 9th, 2005, 10:17 am

<table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><div class='genmed'>QUOTE(mlyons @ Sep 9 2005, 03:12 PM)</div></td></tr><tr><td class='quote'>Daren, I looked at your code sample...it's a little difficult to say whether it's right or wrong. Let me suggest the following...instead of only collecting force plot data at the end of the drive, try collecting continuously to see if more data is available. Also, don't terminate your collection based on receiving 0 data bytes back from the PM3, but terminate at the beginning of the drive. The data is collected from the beginning to the end of the drive. It is available for reading via the force plot command immediately (e.g., during the drive) and is not reset until the catch at the beginning of the next drive. I've used the SDK APIDemo application to repeatedly sample the the force plot data and store it to file. Everything appears to work as I expect. Mark </td></tr></table> OK, thanks Mark, I shall persevere.

[old] Daren C · Post by **[old] Daren C** » September 9th, 2005, 2:06 pm

OK, I think I've got it reading the data now, but I still have a question. Sometimes the 'Byte 0: Bytes read' field is an odd number. Shouldn't this always be even (since there are two bytes in each datum)? And if not, shouldn't a subsequent call start with the missing byte from the previous call? i.e. if I'm told there are 7 bytes recovered, and they're 0xb9 0x00 0xb9 0x00 0xbb 0x00 0xbb, then shouldn't the next set of data start with the missing 0x00 that would have made a pair on the previous call, or is this just silently dropped? If it's dropped, does this matter? What's the range of values that will be returned? Can it go over 256? If so, the second value could be significant (i.e. if a 0x01 got discarded). Or is the "spare" value in the first set always guaranteed to be 0x00 and therefore safe to ignore, as seems to be the case by empirical observation?

[old] mlyons · Post by **[old] mlyons** » September 9th, 2005, 2:35 pm

Daren, The force plot data is defined as 16-bit values because it is necessary...so the MS byte is important. I'm double checking now, but it looks like there may be another bug in the processing of this command that isn't handling the byte count properly and may not be stepping through the array of data properly. Stepping through the array properly looks like it may only be an issue whenever data is requested, but less than the amount requested is available. I'll update this reply when I'm sure about the bug. If it is a bug, it will be fixed in next week's Beta release. Mark

[old] Daren C · Post by **[old] Daren C** » September 9th, 2005, 4:07 pm

Thanks, Mark. If it's of any use, this is the sort of data I'm often getting: <table width='95%' cellspacing='1' cellpadding='3' border='0' align='center'><tr><td><div class='genmed'>CODE</div></td></tr><tr><td class='code'><div> Recovered 7 points Data: 9 0 9 0 13 0 0 ForcePlotPoints[0] = 9 + 0 ForcePlotPoints[1] = 9 + 0 ForcePlotPoints[2] = 13 + 0 Recovered 7 points Data: 24 0 24 0 28 0 0 ForcePlotPoints[3] = 24 + 0 ForcePlotPoints[4] = 24 + 0 ForcePlotPoints[5] = 28 + 0 Recovered 6 points Data: 2f 0 2f 0 32 0 ForcePlotPoints[6] = 2f + 0 ForcePlotPoints[7] = 2f + 0 ForcePlotPoints[8] = 32 + 0 Recovered 8 points Data: 38 0 3c 0 3c 0 41 0 ForcePlotPoints[9] = 38 + 0 ForcePlotPoints[10] = 3c + 0 ForcePlotPoints[11] = 3c + 0 ForcePlotPoints[12] = 41 + 0 Recovered 7 points Data: 4c 0 4c 0 4f 0 0 ForcePlotPoints[13] = 4c + 0 ForcePlotPoints[14] = 4c + 0 ForcePlotPoints[15] = 4f + 0 Recovered 7 points Data: 5c 0 5f 0 62 0 0 ForcePlotPoints[16] = 5c + 0 ForcePlotPoints[17] = 5f + 0 ForcePlotPoints[18] = 62 + 0 Recovered 7 points Data: 69 0 6a 0 6a 0 0 ForcePlotPoints[19] = 69 + 0 ForcePlotPoints[20] = 6a + 0 ForcePlotPoints[21] = 6a + 0 Recovered 7 points Data: 6a 0 6a 0 68 0 0 ForcePlotPoints[22] = 6a + 0 ForcePlotPoints[23] = 6a + 0 ForcePlotPoints[24] = 68 + 0 Recovered 7 points Data: 56 0 51 0 51 0 0 ForcePlotPoints[25] = 56 + 0 ForcePlotPoints[26] = 51 + 0 ForcePlotPoints[27] = 51 + 0 Recovered 4 points Data: 1e 0 14 0 ForcePlotPoints[28] = 1e + 0 ForcePlotPoints[29] = 14 + 0 </div></td></tr></table> These readings are taken during the drive/dwell part of the stroke, and there's at least a 50ms thread sleep between each request.

[old] Chris Brett · Post by **[old] Chris Brett** » November 2nd, 2005, 1:52 pm

Hi there, Is the FORCEPLOTDATA command working in the latest BETA Release? I seem to be getting reasonable data but my pairs of data points appear to be coming in the order LSB first i.e Data Point Pair 1: rsp_data[ 5]= 31 (LSB) & rsp_data[ 6]= 0 (MSB) Data Point Pair 2: rsp_data[ 7]= 31 (LSB) & rsp_data[ 8]= 0 (MSB) Data Point Pair 3: rsp_data[ 9]= 67 (LSB) & rsp_data[ 10]= 0 (MSB) ..etc. In the 6/6/2005 Manual (Revision 0.10) it lists the output as being returned MSB first. Does this mean that my response data is incorrect? I am sending the following command data to the PM3 Monitor using tkcmdsetCSAFE_command(unit_address, cmd_data_size, cmd_data, &rsp_size, rsp_data); command_data="1a, 03, 6b, 01, 20"; Thankyou for any help/guidance you can offer. The response data is output as follows: read data size= 37 rsp_data_read_size= 37 rsp_data_read[ 0]= 26 rsp_data[ 0]= 26 rsp_data_read[ 1]= 35 rsp_data[ 1]= 35 rsp_data_read[ 2]= 107 rsp_data[ 2]= 107 rsp_data_read[ 3]= 33 rsp_data[ 3]= 33 rsp_data_read[ 4]= 14 rsp_data[ 4]= 14 rsp_data_read[ 5]= 31 rsp_data[ 5]= 31 rsp_data_read[ 6]= 0 rsp_data[ 6]= 0 rsp_data_read[ 7]= 31 rsp_data[ 7]= 31 rsp_data_read[ 8]= 0 rsp_data[ 8]= 0 rsp_data_read[ 9]= 67 rsp_data[ 9]= 67 rsp_data_read[ 10]= 0 rsp_data[ 10]= 0 rsp_data_read[ 11]= 96 rsp_data[ 11]= 96 rsp_data_read[ 12]= 0 rsp_data[ 12]= 0 rsp_data_read[ 13]= 121 rsp_data[ 13]= 121 rsp_data_read[ 14]= 0 rsp_data[ 14]= 0 rsp_data_read[ 15]= 126 rsp_data[ 15]= 126 rsp_data_read[ 16]= 0 rsp_data[ 16]= 0 rsp_data_read[ 17]= 120 rsp_data[ 17]= 120 rsp_data_read[ 18]= 0 rsp_data[ 18]= 0 ********************VALID POINTS READ********************** rsp_data_read[ 19]= 0 rsp_data[ 19]= 0 rsp_data_read[ 20]= 0 rsp_data[ 20]= 0 rsp_data_read[ 21]= 0 rsp_data[ 21]= 0 rsp_data_read[ 22]= 6 rsp_data[ 22]= 6 rsp_data_read[ 23]= 176 rsp_data[ 23]= 176 rsp_data_read[ 24]= 84 rsp_data[ 24]= 84 rsp_data_read[ 25]= 0 rsp_data[ 25]= 0 rsp_data_read[ 26]= 1 rsp_data[ 26]= 1 rsp_data_read[ 27]= 3 rsp_data[ 27]= 3 rsp_data_read[ 28]= 180 rsp_data[ 28]= 180 rsp_data_read[ 29]= 0 rsp_data[ 29]= 0 rsp_data_read[ 30]= 209 rsp_data[ 30]= 209 rsp_data_read[ 31]= 88 rsp_data[ 31]= 88 rsp_data_read[ 32]= 88 rsp_data[ 32]= 88 rsp_data_read[ 33]= 0 rsp_data[ 33]= 0 rsp_data_read[ 34]= 0 rsp_data[ 34]= 0 rsp_data_read[ 35]= 0 rsp_data[ 35]= 0 rsp_data_read[ 36]= 0 rsp_data[ 36]= 0 rsp_data[4]= 14 rsp_data[5]= 31 rsp_data[6]= 0 data_points_count= 0 Counter= 4 Rsp_Size = 37 Data_points= 14 i= 5 i+1= 6Point 0: MSB= 31 + LSB= 0. Total= 7936 i= 7 i+1= 8Point 1: MSB= 31 + LSB= 0. Total= 7936 i= 9 i+1= 10Point 2: MSB= 67 + LSB= 0. Total= 17152 i= 11 i+1= 12Point 3: MSB= 96 + LSB= 0. Total= 24576 i= 13 i+1= 14Point 4: MSB= 121 + LSB= 0. Total= 30976 i= 15 i+1= 16Point 5: MSB= 126 + LSB= 0. Total= 32256 i= 17 i+1= 18Point 6: MSB= 120 + LSB= 0. Total= 30720 ********************VALID POINTS READ********************** i= 19 i+1= 20Point 7: MSB= 0 + LSB= 0. Total= 0 i= 21 i+1= 22Point 8: MSB= 0 + LSB= 6. Total= 6 i= 23 i+1= 24Point 9: MSB= 176 + LSB= 84. Total= 45140 i= 25 i+1= 26Point 10: MSB= 0 + LSB= 1. Total= 1 i= 27 i+1= 28Point 11: MSB= 3 + LSB= 180. Total= 948 i= 29 i+1= 30Point 12: MSB= 0 + LSB= 209. Total= 209 i= 31 i+1= 32Point 13: MSB= 88 + LSB= 88. Total= 22616

[old] mlyons · Post by **[old] mlyons** » November 2nd, 2005, 5:04 pm

Chris, Your are correct in that the data is coming LS Byte first ("little endian"). The document is incorrect. All the public CSAFE communcation must be in "little endian" format to comply with the specification. We will get the document updated and issue a new revision. Thanks, Mark

[old] Chris Brett · Post by **[old] Chris Brett** » November 5th, 2005, 2:43 pm

When using the concatanated Stroke state with Csafe_pm_get_forceplotdata. Is it possible that data points from the beginning of the next stroke are recorded in the current stroke before the stroke_state 0f 2=Driving is recognized. I seem to sometimes get more positive values after a series of zeroes which seem to be from the next stroke. The example output below seems to suggest that this is happening. Is this a possibilty? Can I solve it by checking for changes in stroke state separately from calls to Csafe_pm_get_forceplotdata? Thanks again for your help. NEW STROKE! drive_current if == 0 old stroke count = 1 dpc=0, drive current *************STROKE READ START OF STROKE DATA******************** No. of data points= 74 POINT 0: LSB= 0 MSB= 0 Total= 0 POINT 1: LSB= 0 MSB= 0 Total= 0 POINT 2: LSB= 61 MSB= 0 Total= 61 POINT 3: LSB= 61 MSB= 0 Total= 61 POINT 4: LSB= 61 MSB= 0 Total= 61 POINT 5: LSB= 59 MSB= 0 Total= 59 POINT 6: LSB= 59 MSB= 0 Total= 59 POINT 7: LSB= 59 MSB= 0 Total= 59 POINT 8: LSB= 51 MSB= 0 Total= 51 POINT 9: LSB= 51 MSB= 0 Total= 51 POINT 10: LSB= 51 MSB= 0 Total= 51 POINT 11: LSB= 46 MSB= 0 Total= 46 POINT 12: LSB= 46 MSB= 0 Total= 46 POINT 13: LSB= 46 MSB= 0 Total= 46 POINT 14: LSB= 41 MSB= 0 Total= 41 POINT 15: LSB= 41 MSB= 0 Total= 41 POINT 16: LSB= 41 MSB= 0 Total= 41 POINT 17: LSB= 32 MSB= 0 Total= 32 POINT 18: LSB= 32 MSB= 0 Total= 32 POINT 19: LSB= 20 MSB= 0 Total= 20 POINT 20: LSB= 20 MSB= 0 Total= 20 POINT 21: LSB= 20 MSB= 0 Total= 20 POINT 22: LSB= 6 MSB= 0 Total= 6 POINT 23: LSB= 6 MSB= 0 Total= 6 POINT 24: LSB= 6 MSB= 0 Total= 6 POINT 25: LSB= 0 MSB= 0 Total= 0 POINT 26: LSB= 0 MSB= 0 Total= 0 POINT 27: LSB= 0 MSB= 0 Total= 0 POINT 28: LSB= 0 MSB= 0 Total= 0 POINT 29: LSB= 0 MSB= 0 Total= 0 POINT 30: LSB= 0 MSB= 0 Total= 0 POINT 31: LSB= 0 MSB= 0 Total= 0 POINT 32: LSB= 0 MSB= 0 Total= 0 POINT 33: LSB= 0 MSB= 0 Total= 0 POINT 34: LSB= 16 MSB= 0 Total= 16 POINT 35: LSB= 16 MSB= 0 Total= 16 POINT 36: LSB= 16 MSB= 0 Total= 16 *************STROKE READ END OF STROKE DATA******************** NEW STROKE! drive_current if == 0 old stroke count = 2 dpc=0, drive current *************STROKE READ START OF STROKE DATA******************** No. of data points= 86 POINT 0: LSB= 44 MSB= 0 Total= 44 POINT 1: LSB= 44 MSB= 0 Total= 44 POINT 2: LSB= 72 MSB= 0 Total= 72 POINT 3: LSB= 72 MSB= 0 Total= 72 POINT 4: LSB= 84 MSB= 0 Total= 84 POINT 5: LSB= 84 MSB= 0 Total= 84 POINT 6: LSB= 84 MSB= 0 Total= 84 POINT 7: LSB= 83 MSB= 0 Total= 83 POINT 8: LSB= 83 MSB= 0 Total= 83 POINT 9: LSB= 84 MSB= 0 Total= 84 POINT 10: LSB= 84 MSB= 0 Total= 84 POINT 11: LSB= 87 MSB= 0 Total= 87 POINT 12: LSB= 87 MSB= 0 Total= 87 POINT 13: LSB= 85 MSB= 0 Total= 85 POINT 14: LSB= 85 MSB= 0 Total= 85 POINT 15: LSB= 85 MSB= 0 Total= 85 POINT 16: LSB= 80 MSB= 0 Total= 80 POINT 17: LSB= 80 MSB= 0 Total= 80 POINT 18: LSB= 80 MSB= 0 Total= 80 POINT 19: LSB= 80 MSB= 0 Total= 80 POINT 20: LSB= 72 MSB= 0 Total= 72 POINT 21: LSB= 72 MSB= 0 Total= 72 POINT 22: LSB= 70 MSB= 0 Total= 70 POINT 23: LSB= 70 MSB= 0 Total= 70 POINT 24: LSB= 65 MSB= 0 Total= 65 POINT 25: LSB= 65 MSB= 0 Total= 65 POINT 26: LSB= 62 MSB= 0 Total= 62 POINT 27: LSB= 48 MSB= 0 Total= 48 POINT 28: LSB= 48 MSB= 0 Total= 48 POINT 29: LSB= 43 MSB= 0 Total= 43 POINT 30: LSB= 43 MSB= 0 Total= 43 POINT 31: LSB= 23 MSB= 0 Total= 23 POINT 32: LSB= 23 MSB= 0 Total= 23 POINT 33: LSB= 10 MSB= 0 Total= 10 POINT 34: LSB= 10 MSB= 0 Total= 10 POINT 35: LSB= 0 MSB= 0 Total= 0 POINT 36: LSB= 0 MSB= 0 Total= 0 POINT 37: LSB= 0 MSB= 0 Total= 0 POINT 38: LSB= 0 MSB= 0 Total= 0 POINT 39: LSB= 0 MSB= 0 Total= 0 POINT 40: LSB= 0 MSB= 0 Total= 0 POINT 41: LSB= 7 MSB= 0 Total= 7 POINT 42: LSB= 7 MSB= 0 Total= 7 *************STROKE READ END OF STROKE DATA******************** NEW STROKE! drive_current if == 0 old stroke count = 3 dpc=0, drive current *************STROKE READ START OF STROKE DATA******************** No. of data points= 98 POINT 0: LSB= 28 MSB= 0 Total= 28 POINT 1: LSB= 28 MSB= 0 Total= 28 POINT 2: LSB= 49 MSB= 0 Total= 49 POINT 3: LSB= 49 MSB= 0 Total= 49 POINT 4: LSB= 64 MSB= 0 Total= 64 POINT 5: LSB= 64 MSB= 0 Total= 64 POINT 6: LSB= 61 MSB= 0 Total= 61 POINT 7: LSB= 69 MSB= 0 Total= 69 POINT 8: LSB= 69 MSB= 0 Total= 69 POINT 9: LSB= 70 MSB= 0 Total= 70 POINT 10: LSB= 70 MSB= 0 Total= 70 POINT 11: LSB= 72 MSB= 0 Total= 72 POINT 12: LSB= 72 MSB= 0 Total= 72 POINT 13: LSB= 75 MSB= 0 Total= 75 POINT 14: LSB= 75 MSB= 0 Total= 75 POINT 15: LSB= 73 MSB= 0 Total= 73 POINT 16: LSB= 72 MSB= 0 Total= 72 POINT 17: LSB= 72 MSB= 0 Total= 72 POINT 18: LSB= 71 MSB= 0 Total= 71 POINT 19: LSB= 71 MSB= 0 Total= 71 POINT 20: LSB= 68 MSB= 0 Total= 68 POINT 21: LSB= 67 MSB= 0 Total= 67 POINT 22: LSB= 67 MSB= 0 Total= 67 POINT 23: LSB= 65 MSB= 0 Total= 65 POINT 24: LSB= 65 MSB= 0 Total= 65 POINT 25: LSB= 62 MSB= 0 Total= 62 POINT 26: LSB= 61 MSB= 0 Total= 61 POINT 27: LSB= 61 MSB= 0 Total= 61 POINT 28: LSB= 63 MSB= 0 Total= 63 POINT 29: LSB= 61 MSB= 0 Total= 61 POINT 30: LSB= 61 MSB= 0 Total= 61 POINT 31: LSB= 56 MSB= 0 Total= 56 POINT 32: LSB= 56 MSB= 0 Total= 56 POINT 33: LSB= 56 MSB= 0 Total= 56 POINT 34: LSB= 59 MSB= 0 Total= 59 POINT 35: LSB= 59 MSB= 0 Total= 59 POINT 36: LSB= 56 MSB= 0 Total= 56 POINT 37: LSB= 49 MSB= 0 Total= 49 POINT 38: LSB= 49 MSB= 0 Total= 49 POINT 39: LSB= 40 MSB= 0 Total= 40 POINT 40: LSB= 30 MSB= 0 Total= 30 POINT 41: LSB= 30 MSB= 0 Total= 30 POINT 42: LSB= 18 MSB= 0 Total= 18 POINT 43: LSB= 8 MSB= 0 Total= 8 POINT 44: LSB= 8 MSB= 0 Total= 8 POINT 45: LSB= 0 MSB= 0 Total= 0 POINT 46: LSB= 0 MSB= 0 Total= 0 POINT 47: LSB= 0 MSB= 0 Total= 0 POINT 48: LSB= 14 MSB= 0 Total= 14 *************STROKE READ END OF STROKE DATA********************

[old] Chris Brett · Post by **[old] Chris Brett** » November 5th, 2005, 3:08 pm

I've Tried counting the end of the stroke as stroke_state=4 recovery and reading from that point through to the next recovery. It seems to produce more sensible results. Is this what you would advise? NEW STROKE! drive_current if == 0 old stroke count = 1 dpc=0, drive current *************STROKE READ START OF STROKE DATA******************** No. of data points= 136 POINT 0: LSB= 0 MSB= 0 Total= 0 POINT 1: LSB= 0 MSB= 0 Total= 0 POINT 2: LSB= 17 MSB= 0 Total= 17 POINT 3: LSB= 17 MSB= 0 Total= 17 POINT 4: LSB= 45 MSB= 0 Total= 45 POINT 5: LSB= 45 MSB= 0 Total= 45 POINT 6: LSB= 72 MSB= 0 Total= 72 POINT 7: LSB= 72 MSB= 0 Total= 72 POINT 8: LSB= 82 MSB= 0 Total= 82 POINT 9: LSB= 82 MSB= 0 Total= 82 POINT 10: LSB= 80 MSB= 0 Total= 80 POINT 11: LSB= 81 MSB= 0 Total= 81 POINT 12: LSB= 81 MSB= 0 Total= 81 POINT 13: LSB= 89 MSB= 0 Total= 89 POINT 14: LSB= 89 MSB= 0 Total= 89 POINT 15: LSB= 95 MSB= 0 Total= 95 POINT 16: LSB= 95 MSB= 0 Total= 95 POINT 17: LSB= 94 MSB= 0 Total= 94 POINT 18: LSB= 94 MSB= 0 Total= 94 POINT 19: LSB= 100 MSB= 0 Total= 100 POINT 20: LSB= 98 MSB= 0 Total= 98 POINT 21: LSB= 98 MSB= 0 Total= 98 POINT 22: LSB= 98 MSB= 0 Total= 98 POINT 23: LSB= 98 MSB= 0 Total= 98 POINT 24: LSB= 103 MSB= 0 Total= 103 POINT 25: LSB= 100 MSB= 0 Total= 100 POINT 26: LSB= 100 MSB= 0 Total= 100 POINT 27: LSB= 107 MSB= 0 Total= 107 POINT 28: LSB= 109 MSB= 0 Total= 109 POINT 29: LSB= 109 MSB= 0 Total= 109 POINT 30: LSB= 112 MSB= 0 Total= 112 POINT 31: LSB= 107 MSB= 0 Total= 107 POINT 32: LSB= 107 MSB= 0 Total= 107 POINT 33: LSB= 117 MSB= 0 Total= 117 POINT 34: LSB= 118 MSB= 0 Total= 118 POINT 35: LSB= 118 MSB= 0 Total= 118 POINT 36: LSB= 120 MSB= 0 Total= 120 POINT 37: LSB= 121 MSB= 0 Total= 121 POINT 38: LSB= 126 MSB= 0 Total= 126 POINT 39: LSB= 126 MSB= 0 Total= 126 POINT 40: LSB= 124 MSB= 0 Total= 124 POINT 41: LSB= 135 MSB= 0 Total= 135 POINT 42: LSB= 124 MSB= 0 Total= 124 POINT 43: LSB= 124 MSB= 0 Total= 124 POINT 44: LSB= 125 MSB= 0 Total= 125 POINT 45: LSB= 118 MSB= 0 Total= 118 POINT 46: LSB= 120 MSB= 0 Total= 120 POINT 47: LSB= 113 MSB= 0 Total= 113 POINT 48: LSB= 113 MSB= 0 Total= 113 POINT 49: LSB= 112 MSB= 0 Total= 112 POINT 50: LSB= 105 MSB= 0 Total= 105 POINT 51: LSB= 101 MSB= 0 Total= 101 POINT 52: LSB= 98 MSB= 0 Total= 98 POINT 53: LSB= 98 MSB= 0 Total= 98 POINT 54: LSB= 89 MSB= 0 Total= 89 POINT 55: LSB= 82 MSB= 0 Total= 82 POINT 56: LSB= 79 MSB= 0 Total= 79 POINT 57: LSB= 73 MSB= 0 Total= 73 POINT 58: LSB= 70 MSB= 0 Total= 70 POINT 59: LSB= 70 MSB= 0 Total= 70 POINT 60: LSB= 66 MSB= 0 Total= 66 POINT 61: LSB= 53 MSB= 0 Total= 53 POINT 62: LSB= 43 MSB= 0 Total= 43 POINT 63: LSB= 27 MSB= 0 Total= 27 POINT 64: LSB= 24 MSB= 0 Total= 24 POINT 65: LSB= 6 MSB= 0 Total= 6 POINT 66: LSB= 6 MSB= 0 Total= 6 POINT 67: LSB= 0 MSB= 0 Total= 0 *************STROKE READ END OF STROKE DATA******************** NEW STROKE! drive_current if == 0 old stroke count = 2 dpc=0, drive current *************STROKE READ START OF STROKE DATA******************** No. of data points= 114 POINT 0: LSB= 0 MSB= 0 Total= 0 POINT 1: LSB= 16 MSB= 0 Total= 16 POINT 2: LSB= 16 MSB= 0 Total= 16 POINT 3: LSB= 30 MSB= 0 Total= 30 POINT 4: LSB= 56 MSB= 0 Total= 56 POINT 5: LSB= 71 MSB= 0 Total= 71 POINT 6: LSB= 71 MSB= 0 Total= 71 POINT 7: LSB= 82 MSB= 0 Total= 82 POINT 8: LSB= 83 MSB= 0 Total= 83 POINT 9: LSB= 89 MSB= 0 Total= 89 POINT 10: LSB= 89 MSB= 0 Total= 89 POINT 11: LSB= 98 MSB= 0 Total= 98 POINT 12: LSB= 103 MSB= 0 Total= 103 POINT 13: LSB= 103 MSB= 0 Total= 103 POINT 14: LSB= 103 MSB= 0 Total= 103 POINT 15: LSB= 110 MSB= 0 Total= 110 POINT 16: LSB= 118 MSB= 0 Total= 118 POINT 17: LSB= 116 MSB= 0 Total= 116 POINT 18: LSB= 116 MSB= 0 Total= 116 POINT 19: LSB= 118 MSB= 0 Total= 118 POINT 20: LSB= 117 MSB= 0 Total= 117 POINT 21: LSB= 113 MSB= 0 Total= 113 POINT 22: LSB= 122 MSB= 0 Total= 122 POINT 23: LSB= 112 MSB= 0 Total= 112 POINT 24: LSB= 112 MSB= 0 Total= 112 POINT 25: LSB= 121 MSB= 0 Total= 121 POINT 26: LSB= 119 MSB= 0 Total= 119 POINT 27: LSB= 118 MSB= 0 Total= 118 POINT 28: LSB= 114 MSB= 0 Total= 114 POINT 29: LSB= 118 MSB= 0 Total= 118 POINT 30: LSB= 124 MSB= 0 Total= 124 POINT 31: LSB= 118 MSB= 0 Total= 118 POINT 32: LSB= 118 MSB= 0 Total= 118 POINT 33: LSB= 121 MSB= 0 Total= 121 POINT 34: LSB= 112 MSB= 0 Total= 112 POINT 35: LSB= 115 MSB= 0 Total= 115 POINT 36: LSB= 107 MSB= 0 Total= 107 POINT 37: LSB= 107 MSB= 0 Total= 107 POINT 38: LSB= 99 MSB= 0 Total= 99 POINT 39: LSB= 97 MSB= 0 Total= 97 POINT 40: LSB= 99 MSB= 0 Total= 99 POINT 41: LSB= 82 MSB= 0 Total= 82 POINT 42: LSB= 94 MSB= 0 Total= 94 POINT 43: LSB= 66 MSB= 0 Total= 66 POINT 44: LSB= 76 MSB= 0 Total= 76 POINT 45: LSB= 59 MSB= 0 Total= 59 POINT 46: LSB= 67 MSB= 0 Total= 67 POINT 47: LSB= 53 MSB= 0 Total= 53 POINT 48: LSB= 53 MSB= 0 Total= 53 POINT 49: LSB= 57 MSB= 0 Total= 57 POINT 50: LSB= 47 MSB= 0 Total= 47 POINT 51: LSB= 43 MSB= 0 Total= 43 POINT 52: LSB= 45 MSB= 0 Total= 45 POINT 53: LSB= 37 MSB= 0 Total= 37 POINT 54: LSB= 35 MSB= 0 Total= 35 POINT 55: LSB= 18 MSB= 0 Total= 18 POINT 56: LSB= 13 MSB= 0 Total= 13 *************STROKE READ END OF STROKE DATA******************** NEW STROKE! drive_current if == 0 old stroke count = 3 dpc=0, drive current *************STROKE READ START OF STROKE DATA******************** No. of data points= 106 POINT 0: LSB= 14 MSB= 0 Total= 14 POINT 1: LSB= 34 MSB= 0 Total= 34 POINT 2: LSB= 55 MSB= 0 Total= 55 POINT 3: LSB= 55 MSB= 0 Total= 55 POINT 4: LSB= 79 MSB= 0 Total= 79 POINT 5: LSB= 89 MSB= 0 Total= 89 POINT 6: LSB= 94 MSB= 0 Total= 94 POINT 7: LSB= 94 MSB= 0 Total= 94 POINT 8: LSB= 92 MSB= 0 Total= 92 POINT 9: LSB= 92 MSB= 0 Total= 92 POINT 10: LSB= 101 MSB= 0 Total= 101 POINT 11: LSB= 97 MSB= 0 Total= 97 POINT 12: LSB= 97 MSB= 0 Total= 97 POINT 13: LSB= 105 MSB= 0 Total= 105 POINT 14: LSB= 107 MSB= 0 Total= 107 POINT 15: LSB= 109 MSB= 0 Total= 109 POINT 16: LSB= 118 MSB= 0 Total= 118 POINT 17: LSB= 107 MSB= 0 Total= 107 POINT 18: LSB= 116 MSB= 0 Total= 116 POINT 19: LSB= 116 MSB= 0 Total= 116 POINT 20: LSB= 110 MSB= 0 Total= 110 POINT 21: LSB= 110 MSB= 0 Total= 110 POINT 22: LSB= 109 MSB= 0 Total= 109 POINT 23: LSB= 111 MSB= 0 Total= 111 POINT 24: LSB= 111 MSB= 0 Total= 111 POINT 25: LSB= 105 MSB= 0 Total= 105 POINT 26: LSB= 111 MSB= 0 Total= 111 POINT 27: LSB= 111 MSB= 0 Total= 111 POINT 28: LSB= 112 MSB= 0 Total= 112 POINT 29: LSB= 102 MSB= 0 Total= 102 POINT 30: LSB= 108 MSB= 0 Total= 108 POINT 31: LSB= 101 MSB= 0 Total= 101 POINT 32: LSB= 98 MSB= 0 Total= 98 POINT 33: LSB= 100 MSB= 0 Total= 100 POINT 34: LSB= 84 MSB= 0 Total= 84 POINT 35: LSB= 87 MSB= 0 Total= 87 POINT 36: LSB= 75 MSB= 0 Total= 75 POINT 37: LSB= 83 MSB= 0 Total= 83 POINT 38: LSB= 75 MSB= 0 Total= 75 POINT 39: LSB= 78 MSB= 0 Total= 78 POINT 40: LSB= 72 MSB= 0 Total= 72 POINT 41: LSB= 60 MSB= 0 Total= 60 POINT 42: LSB= 54 MSB= 0 Total= 54 POINT 43: LSB= 58 MSB= 0 Total= 58 POINT 44: LSB= 54 MSB= 0 Total= 54 POINT 45: LSB= 58 MSB= 0 Total= 58 POINT 46: LSB= 39 MSB= 0 Total= 39 POINT 47: LSB= 46 MSB= 0 Total= 46 POINT 48: LSB= 34 MSB= 0 Total= 34 POINT 49: LSB= 34 MSB= 0 Total= 34 POINT 50: LSB= 43 MSB= 0 Total= 43 POINT 51: LSB= 27 MSB= 0 Total= 27 POINT 52: LSB= 23 MSB= 0 Total= 23 *************STROKE READ END OF STROKE DATA********************

[old] mlyons · Post by **[old] mlyons** » November 6th, 2005, 8:55 am

Chris, Yes...I think this makes the most sense. Since the PM3 is "detecting" the beginning of stroke itself by observing the flywheel behavior while simultaneously collecting forceplot data there may be a slightly delay (or offset) between the actual stroke beginning as detected by the PM3 and forceplot data collection. Collecting from recovery to recovery guarantees not missing any data. Mark