{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":562620470,"defaultBranch":"master","name":"c172hc-fsconnect","ownerLogin":"jkirk","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2022-11-06T22:10:56.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/288637?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1685356028.713942","currentOid":""},"activityList":{"items":[{"before":"6b1c94a72a5dfebfcf45cf3ec73bea76c9bd29e0","after":"5f95823dca246299a84284dbbe0e2c73bce1ce84","ref":"refs/heads/master","pushedAt":"2023-06-04T13:05:06.972Z","pushType":"push","commitsCount":1,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"On SendMessage try to open the serial port\n\nIf the serial port was disconnected or the configuration changed, the serial connection was not re-established.\n\nPreviously, we opened the serial connection when the port was newly detected or when the configuration changed. But if the serial port was lost and we got the same port again, we did not open it again.\nWe now open the serial connection (if it was not already open) every time we send a message.\n\nAlso, disable the SendSingleMessageBlock before we start the fsmaster class,\nbecause there was a race condition where the serial port was detected\nand the SendSingleMessageBlock button was enabled, but we disabled it immediately afterwards.","shortMessageHtmlLink":"On SendMessage try to open the serial port"}},{"before":"1947b08ba39a0c14635f3cfe806872804b344822","after":"6b1c94a72a5dfebfcf45cf3ec73bea76c9bd29e0","ref":"refs/heads/master","pushedAt":"2023-06-02T11:28:58.379Z","pushType":"push","commitsCount":1,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Send SerialPortChanged event if serial ports changed\n\nAllow to set COM port and baud rate.","shortMessageHtmlLink":"Send SerialPortChanged event if serial ports changed"}},{"before":"1022450536a47864ab66eb4d678f8283abadb601","after":"1947b08ba39a0c14635f3cfe806872804b344822","ref":"refs/heads/master","pushedAt":"2023-06-01T23:27:10.998Z","pushType":"push","commitsCount":3,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Add Send Single Message Block button\n\nSend 4 messages with the MakerFaire values to c172hc-fsmaster.","shortMessageHtmlLink":"Add Send Single Message Block button"}},{"before":"d1fb93e96d130250b3d51fd77e966740bb802abb","after":"1022450536a47864ab66eb4d678f8283abadb601","ref":"refs/heads/master","pushedAt":"2023-06-01T19:24:03.545Z","pushType":"push","commitsCount":3,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Request Cessna Six Pack values\n\nWe want to receive the values of the so-called Cessna Six Pack, the primary flight instruments.\nThese are the following:\n\n- Airspeed Indicator\n- Attitude Indicator (pitch + bank)\n- Altimeter\n- Vertical Speed Indicator\n- Heading Indicator\n- Turn Coordinator\n\nWe do not need latitude and longitude, so remove them.\nWe also do not want to output all previous values, only the most recent.\nWe also allow the user to stop requesting new data.","shortMessageHtmlLink":"Request Cessna Six Pack values"}},{"before":"3543fd6828a9e7da2d150c1730108b595d966cfc","after":"d1fb93e96d130250b3d51fd77e966740bb802abb","ref":"refs/heads/master","pushedAt":"2023-05-29T13:01:13.419Z","pushType":"push","commitsCount":1,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Enable the .NET Framework 2.0 runtime activation policy\n\nFSX:Steam Edition and FSX Deluxe Edition come with two different versions of Microsoft.FlightSimulator.SimConnect:\n\n- FSX: Steam Edition: Version 10.0.62615\n- FSX: Deluxe Edition: Version 10.0.61355\n\nThe SimConnect DLL of FSX:SE works without this  .NET Framework 2.0 runtime activation policy but the one with  FSX: Deluxe Edition does not.\nOne recieves the following error:\n\n  Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.","shortMessageHtmlLink":"Enable the .NET Framework 2.0 runtime activation policy"}},{"before":"f7ee377a92cdc784fc366b73d6f894043d36cd6b","after":"3543fd6828a9e7da2d150c1730108b595d966cfc","ref":"refs/heads/master","pushedAt":"2023-05-29T10:55:54.794Z","pushType":"push","commitsCount":1,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Remove obsolete SimConnectTest project\n\nWe now also show AIRSPEED INDICATED.","shortMessageHtmlLink":"Remove obsolete SimConnectTest project"}},{"before":"9ea6015026ad167d7dc25743aea36d80cb9266f2","after":"f7ee377a92cdc784fc366b73d6f894043d36cd6b","ref":"refs/heads/master","pushedAt":"2023-05-29T10:38:59.350Z","pushType":"push","commitsCount":1,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Import Managed Data Request sample from FSX SDK\n\nCopied \"Managed Data Request\" from\n  FSX\\SDK\\Core Utilities Kit\\SimConnect SDK\\Samples\\Managed Data Request\nand added the project to this solution.\nA one-time conversion was required.\n\nWhen trying to build the project, the following error was displayed:\n\n  Severity Code Description Project File Line Suppression State\n  Error  The reference assemblies for .NETFramework,Version=v4.0 were not found.\n\nIn the project properties changed the following:\n- Application -> Target framework to .NET Framework 4.8\n- Build -> Platform target from Any CPU to x86","shortMessageHtmlLink":"Import Managed Data Request sample from FSX SDK"}},{"before":null,"after":"29c458829f4dc9a4e30da585b430346ff7d9e021","ref":"refs/heads/readme-gauges","pushedAt":"2023-05-29T10:27:08.713Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Initial README.md\n\nDescribe the project itself, the gauges and the gauge codes.","shortMessageHtmlLink":"Initial README.md"}},{"before":"46296dd6734771f7d3a9b033fe5a74c5299dfa2c","after":"df4b1ad00523fc9b89ca1312a2a6d8f534ea3b1d","ref":"refs/heads/jkirk/readme","pushedAt":"2023-05-29T10:13:35.863Z","pushType":"push","commitsCount":1,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Update README.md\n\nImprove wording.","shortMessageHtmlLink":"Update README.md"}},{"before":"308b6eac551f09681bac5e1030c6281e1407b920","after":"9ea6015026ad167d7dc25743aea36d80cb9266f2","ref":"refs/heads/master","pushedAt":"2023-05-24T15:52:10.986Z","pushType":"push","commitsCount":2,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Add repeat messages options\n\nTo make it easier to resend the same of similar messages, 3 options were added before the use can continue.\n- r to repeat the same messages\n- i to change the message interval only\n- t to change the target value only","shortMessageHtmlLink":"Add repeat messages options"}},{"before":"771517e54cde836d81e4644335b77c0bba24a943","after":"308b6eac551f09681bac5e1030c6281e1407b920","ref":"refs/heads/master","pushedAt":"2023-05-24T13:00:07.253Z","pushType":"push","commitsCount":1,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Fix for loop overflow and underflow\n\nWhen value hits 0, value -= step_value is still executed, causing value to underflow and get 2^32 -1.\nAs this is greater than target_value, the for loop never stops.\n\nThe same can happen with the value += step_value loop: if value hits 2^32-1 value + step_value is executed and value overflows.\n\nSo we check whether value is still greate or less than the start_value to prevent this from happening.\n\nHowever, we should consider signed values.","shortMessageHtmlLink":"Fix for loop overflow and underflow"}},{"before":"fc2b527c0b1b2ecda00ea2ccc27eb725d4745e37","after":"771517e54cde836d81e4644335b77c0bba24a943","ref":"refs/heads/master","pushedAt":"2023-05-23T23:21:02.743Z","pushType":"push","commitsCount":2,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Add LatencyAnalysis (Send n messages @ m ms)\n\nAsk the user for the gauge code, a start and a target value, a step value, a message interval and a no data timeout and perform a latency analysis when the start code is detected.\n\nThis means that a number of messages are sent to the c172hc-fsmaster within 10 seconds after the start code is received. We then compare the number of sent messages with the number of messages c172hc-fsmaster received.\n\nIf no data is received within the no data time interval (which defaults to 10 seconds) we timeout and start over.\n\nNote, that we defined 0x55 as the start code but c172hc-fsmaster currently (bcca6e4) sends 0x55 via Serial.println() where it gets converted to the string \"85\\r\\n\". Therefor we need to trim the received line and compare it against \"85\".\n\nCloses: jkirk/c172hc-fsconnect#1","shortMessageHtmlLink":"Add LatencyAnalysis (Send n messages @ m ms)"}},{"before":"6fb7ac96059e7e4b0ba1f8bcbe8e964930770eb7","after":"fc2b527c0b1b2ecda00ea2ccc27eb725d4745e37","ref":"refs/heads/master","pushedAt":"2023-05-16T23:55:58.725Z","pushType":"push","commitsCount":1,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"On successive messages, query all message parameters (except gauge type + start value)\n\nWe used to ask only for the (new) target value on successive messages.\nIt turned out that we needed to change more.\nWe now ask for all the message parameters (except gauge type + start value) on successive messages.","shortMessageHtmlLink":"On successive messages, query all message parameters (except gauge ty…"}},{"before":"7754c5d61d9f111d5743c61c6a366ea2e5bb5392","after":"6fb7ac96059e7e4b0ba1f8bcbe8e964930770eb7","ref":"refs/heads/master","pushedAt":"2023-05-14T03:37:26.719Z","pushType":"push","commitsCount":4,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Generate + send messages from start to target value with custom step + message interval\n\nImplemented StartToTargetMessageInterval() where Gauge Code,\na start and target value, a step value and a message interval are given.\nMessages are then generated with the specified step value and at the specified message interval.","shortMessageHtmlLink":"Generate + send messages from start to target value with custom step …"}},{"before":"7754c5d61d9f111d5743c61c6a366ea2e5bb5392","after":"46296dd6734771f7d3a9b033fe5a74c5299dfa2c","ref":"refs/heads/jkirk/readme","pushedAt":"2023-05-13T22:27:36.794Z","pushType":"push","commitsCount":1,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"WIP: Create README.md\n\nUsage was AI generated and does not reflect the reality. This needs to be improved or deleted.","shortMessageHtmlLink":"WIP: Create README.md"}},{"before":null,"after":"7754c5d61d9f111d5743c61c6a366ea2e5bb5392","ref":"refs/heads/jkirk/readme","pushedAt":"2023-05-13T22:26:17.783Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Update CalculateChecksum function\n\nInitially (in our meeting on 2022-07-06) we defined our c172hc-message-protocol\nas follows:\n\n- STX 0x02\n- Gauge Code (1 Byte, i.e. 0x20 for Airspeed)\n- Gauge Value (4 Byte)\n- Checksum: 0xFF XOR GaugeCode -> XOR first Byte (MSB) -> XOR second byte -> XOR third byte -> XOR fourth byte\n- ETX 0x03\n\nThe message-protocol and checksum implementation was tested against\nc172hc-fsmaster which generated different checksums (see\njkirk/c172hc-fsconnect@05218eb).\n\nIt turned out that we had a misunderstanding about how to implement the\nchecksum and after a long debugging session we finally agreed on a calculation\nbased on the Intel Hex file checksum implementation:\nhttps://tewarid.github.io/2013/08/01/calculate-intel-hex-file-checksum-using-windows-calculator.html\n\nch172hc-fsmaster was fixed partially (see: jkirk/c172hc-fsmaster@b8b101e): We\nagreed to calculate the checksum using only the Gauge Code and Gauge Value (and\nwithout STX (0x02)). Currently c172hc-fsmaster still uses STX to calculate the\nchecksum, this needs to be fixed.\n\nAdded a new Airspeed Demo Message function AirspeedDemoMessageCalculated()\nwhere the given Gauge Type (0x20) and Gauge Value (0x1D 0x80) are used to\ncalculate the checksum and where the generated message is then sent to\nc172hc-fsmaster.\n\nThe original function AirspeedDemoMessage() was renamed to\nAirspeedDemoMessageHardcoded but basically does the same as before: It sends\nthe hard coded the Airspeed Demo Message to the serial port. The checksum\n(0x43) was calculated by hand: NOT(0x20 + 0x1D + 0x80) + 1.\n\nWhile at it also implemented a PrintMessage function which takes a byte array\nmessage and prints the content of the message in hexadecimal format.","shortMessageHtmlLink":"Update CalculateChecksum function"}},{"before":"924504b29ebb0b0bace48411a0aaaf04e72e954d","after":"7754c5d61d9f111d5743c61c6a366ea2e5bb5392","ref":"refs/heads/master","pushedAt":"2023-05-13T02:42:14.384Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Update CalculateChecksum function\n\nInitially (in our meeting on 2022-07-06) we defined our c172hc-message-protocol\nas follows:\n\n- STX 0x02\n- Gauge Code (1 Byte, i.e. 0x20 for Airspeed)\n- Gauge Value (4 Byte)\n- Checksum: 0xFF XOR GaugeCode -> XOR first Byte (MSB) -> XOR second byte -> XOR third byte -> XOR fourth byte\n- ETX 0x03\n\nThe message-protocol and checksum implementation was tested against\nc172hc-fsmaster which generated different checksums (see\njkirk/c172hc-fsconnect@05218eb).\n\nIt turned out that we had a misunderstanding about how to implement the\nchecksum and after a long debugging session we finally agreed on a calculation\nbased on the Intel Hex file checksum implementation:\nhttps://tewarid.github.io/2013/08/01/calculate-intel-hex-file-checksum-using-windows-calculator.html\n\nch172hc-fsmaster was fixed partially (see: jkirk/c172hc-fsmaster@b8b101e): We\nagreed to calculate the checksum using only the Gauge Code and Gauge Value (and\nwithout STX (0x02)). Currently c172hc-fsmaster still uses STX to calculate the\nchecksum, this needs to be fixed.\n\nAdded a new Airspeed Demo Message function AirspeedDemoMessageCalculated()\nwhere the given Gauge Type (0x20) and Gauge Value (0x1D 0x80) are used to\ncalculate the checksum and where the generated message is then sent to\nc172hc-fsmaster.\n\nThe original function AirspeedDemoMessage() was renamed to\nAirspeedDemoMessageHardcoded but basically does the same as before: It sends\nthe hard coded the Airspeed Demo Message to the serial port. The checksum\n(0x43) was calculated by hand: NOT(0x20 + 0x1D + 0x80) + 1.\n\nWhile at it also implemented a PrintMessage function which takes a byte array\nmessage and prints the content of the message in hexadecimal format.","shortMessageHtmlLink":"Update CalculateChecksum function"}},{"before":"5922ccf250d7293d032cd49c62b3c56e37f2f773","after":"924504b29ebb0b0bace48411a0aaaf04e72e954d","ref":"refs/heads/master","pushedAt":"2023-05-13T02:39:32.686Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Update CalculateChecksum function\n\nInitially (in our meeting on 2022-07-06) we defined our c172hc-message-protocol\nas follows:\n\n- STX 0x02\n- Gauge Code (1 Byte, i.e. 0x20 for Airspeed)\n- Gauge Value (4 Byte)\n- Checksum: 0xFF XOR GaugeCode -> XOR first Byte (MSB) -> XOR second byte -> XOR third byte -> XOR fourth byte\n- ETX 0x03\n\nWhile at it also implemented a PrintMessage function which takes a byte array message and prints the content of the message in hexadecimal format.\n\nThe message-protocol and checksum implementation was tested against\nc172hc-fsmaster which generated different checksums (see\njkirk/c172hc-fsconnect@05218eb).\n\nIt turned out that we had a misunderstanding about how to implement the\nchecksum and after a long debugging session we finally agreed on a calculation\nbased on the Intel Hex file checksum implementation:\nhttps://tewarid.github.io/2013/08/01/calculate-intel-hex-file-checksum-using-windows-calculator.html\n\nch172hc-fsmaster was fixed partially (see: jkirk/c172hc-fsmaster@b8b101e): We\nagreed to calculate the checksum using only the Gauge Code and Gauge Value (and\nwithout STX (0x02)). Currently c172hc-fsmaster still uses STX to calculate the\nchecksum, this needs to be fixed.\n\nAdded a new Airspeed Demo Message function AirspeedDemoMessageCalculated()\nwhere the given Gauge Type (0x20) and Gauge Value (0x1D 0x80) are used to\ncalculate the checksum and where the generated message is then sent to\nc172hc-fsmaster.\n\nThe original function AirspeedDemoMessage() was renamed to\nAirspeedDemoMessageHardcoded but basically does the same as before: It sends\nthe hard coded the Airspeed Demo Message to the serial port. The checksum\n(0x43) was calculated by hand: NOT(0x20 + 0x1D + 0x80) + 1.\n\nWhile at it also implemented a PrintMessage function which takes a byte array\nmessage and prints the content of the message in hexadecimal format.","shortMessageHtmlLink":"Update CalculateChecksum function"}},{"before":"be2e572c672d6a87014798ad508a32c1543b3f23","after":"5922ccf250d7293d032cd49c62b3c56e37f2f773","ref":"refs/heads/master","pushedAt":"2023-05-13T02:15:37.549Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Update CalculateChecksum function\n\nInitially (in our meeting on 2022-07-06) we defined our c172hc-message-protocol as follows:\n\n- STX 0x02\n- Gauge Code (1 Byte, i.e. 0x20 for Airspeed)\n- Gauge Value (4 Byte)\n- Checksum: 0xFF XOR GaugeCode -> XOR first Byte (MSB) -> XOR second byte -> XOR third byte -> XOR fourth byte\n- ETX 0x03\n\nThe message-protocol and checksum implementation was tested against c172hc-fsmaster which generated different checksums (see jkirk/c172hc-fsmaster@05218eb).\n\nIt turned out that we had a misunderstanding about how to implement the checksum and after a long debugging session we finally agreed on a calculation based on the Intel Hex file checksum implementation: https://tewarid.github.io/2013/08/01/calculate-intel-hex-file-checksum-using-windows-calculator.html\n\nch172hc-fsmaster was fixed partially (see: jkirk/c172hc-fsmaster@b8b101e): We agreed to calculate the checksum using only the Gauge Code and Gauge Value (and without STX (0x02)). Currently c172hc-fsmaster still uses STX to calculate the checksum, this needs to be fixed.\n\nAdded a new Airspeed Demo Message function AirspeedDemoMessageCalculated() where the given Gauge Type (0x20) and Gauge Value (0x1D 0x80) are used to calculate the checksum and where the generated message is then sent to c172hc-fsmaster.\n\nThe original function AirspeedDemoMessage() was renamed to AirspeedDemoMessageHardcoded but basically does the same as before: It sends the hard coded the Airspeed Demo Message to the serial port. The checksum (0x43) was calculated by hand: NOT(0x20 + 0x1D + 0x80) + 1.\n\nWhile at it also implemented a PrintMessage function which takes a byte array message and prints the content of the message in hexadecimal format.","shortMessageHtmlLink":"Update CalculateChecksum function"}},{"before":"05218eb5efaafd3d1f3574ac36b935307d9fe382","after":"be2e572c672d6a87014798ad508a32c1543b3f23","ref":"refs/heads/master","pushedAt":"2023-05-13T02:12:21.650Z","pushType":"push","commitsCount":2,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Update CalculateChecksum function\n\nInitially (in our meeting on 2022-07-06) we defined our c172hc-message-protocol as follows:\n\n- STX 0x02\n- Gauge Code (1 Byte, i.e. 0x20 for Airspeed)\n- Gauge Value (4 Byte)\n- Checksum: 0xFF XOR GaugeCode -> XOR first Byte (MSB) -> XOR second byte -> XOR third byte -> XOR fourth byte\n- ETX 0x03\n\nThe message-protocol and checksum implementation was tested against c172hc-fsmaster which generated different checksums (see c172hc-fsmaster@05218eb).\n\nIt turned out that we had a misunderstanding about how to implement the checksum and after a long debugging session we finally agreed on a calculation based on the Intel Hex file checksum implementation: https://tewarid.github.io/2013/08/01/calculate-intel-hex-file-checksum-using-windows-calculator.html\n\nch172hc-fsmaster was fixed partially (see: jkirk/ch172hc-fsmaster@b8b101e): We agreed to calculate the checksum using only the Gauge Code and Gauge Value (and without STX (0x02)). Currently c172hc-fsmaster still uses STX to calculate the checksum, this needs to be fixed.\n\nAdded a new Airspeed Demo Message function AirspeedDemoMessageCalculated() where the given Gauge Type (0x20) and Gauge Value (0x1D 0x80) are used to calculate the checksum and where the generated message is then sent to c172hc-fsmaster.\n\nThe original function AirspeedDemoMessage() was renamed to AirspeedDemoMessageHardcoded but basically does the same as before: It sends the hard coded the Airspeed Demo Message to the serial port. The checksum (0x43) was calculated by hand: NOT(0x20 + 0x1D + 0x80) + 1.\n\nWhile at it also implemented a PrintMessage function which takes a byte array message and prints the content of the message in hexadecimal format.","shortMessageHtmlLink":"Update CalculateChecksum function"}},{"before":"b70e813ce88afe077d397661281cb4913213e45f","after":"05218eb5efaafd3d1f3574ac36b935307d9fe382","ref":"refs/heads/master","pushedAt":"2023-04-30T16:25:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Implement CalculateChecksum + StartToTargetValue\n\nStartToTargetValue() asks the user for the start value, the end value\nand the so called 'target time interval', the time  which should pass\nbetween start and end value.\n\nThe message interval is (currently hardcoded) 50ms and the message value\nis then sent to the c172hc-master in corresponding steps via the serial\ninterface.\n\nSince the message is generated dynamically, the checksum must be\nrecalculated for each value. This is done in the CalculateChecksum\nfunction.\n\nThis code was used for our first tests in the early morning of\n2022-11-07. We noticed problems with the checksum calculation code\n(either on the this (c172hc-fsconnect) or the c172hc-fsmaster side), but\nran out of time for further investigation.","shortMessageHtmlLink":"Implement CalculateChecksum + StartToTargetValue"}},{"before":"80438f3580d5ab9866f1b9d1097419f7ecaf3a4d","after":"b70e813ce88afe077d397661281cb4913213e45f","ref":"refs/heads/master","pushedAt":"2023-04-30T14:18:02.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"jkirk","name":"Darshaka Pathirana","path":"/jkirk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/288637?s=80&v=4"},"commit":{"message":"Initial StartToTargetValue\n\nQuery the user for start value, target value and target time interval and output the given input.","shortMessageHtmlLink":"Initial StartToTargetValue"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADOlbwbwA","startCursor":null,"endCursor":null}},"title":"Activity · jkirk/c172hc-fsconnect"}