Perform minor edits to Javascript based CAN bus DBC file editor

We have a HTML/Javascript based file editor. This editor allows you to edit/load/download DBC files, which is a standardized database file format used within our industry. You can read about DBC files here: [login to view URL] The editor both enables the creation of the DBC file itself, but it also allows users to view the logic of how signals are encoded in the DBC file via the Signal Preview section. Further, users can test how raw data bytes are going to be decoded via the DBC file using the payload decoding section. You can find the latest source code for the editor below: [login to view URL] The current version of the editor has some bugs and we are looking for a person to fix these, as well as help with future development projects. This project requires good Javascript coding skills as you’ll need to digest a bit of code to identify the right spots to fix the bugs. Further, it is necessary that you have a good understanding of INTEL/MOTOROLA byte ordering and if possible it is an advantage if you are already familiar with CAN bus and DBC files - though not a requirement. NOTE: We will consider your bid as the final budget for the project - we will not accept changes vs. the bid. --------------------------- Task 1 (correct Intel decoding): The ordering of the extracted bits must be done correctly based on whether the user is considering Intel or Motorola signals. Consider the below example using this DBC file: [login to view URL] [see [login to view URL]] The correct ‘raw payload’ in this example is in binary form 10111110 1000 because the signal is Intel and hence the bits from Byte 6 should be placed after the bits from Byte 7 - not before. The final value should thus become 1000 degC for BRTemp in this example. Please update the editor so that the data payload is correctly calculated using Intel byte ordering. As another test, this update should result in the default example with EngineSpeed ending up with the value 1090.375 RPM instead of 612.15 RPM. --------------------------- Task 2 (correct Motorola decoding): Similarly, the Motorola decoding is currently not working correctly. To see this, you can load the following test DBC and insert the payload as in below example. The correct value should be as follows: [login to view URL] Data = 0b0100010010000100 = 0x4484 = 17540 Physical value = 1 * 17540 + 1 = 17541 In other words, the ordering of the bit chunks should be corrected for Motorola. [see [login to view URL]]