How to import labVIEW codes to different editor (KitEditor in EA eDIPTFT70-A)

[Borjomy]

bug send

[Borjomy]

bug send

[enthusiast4]

Thanks a ton again for your Support and dedication!

[wiebe@CARYA]

---

@Gayatri4 wrote:

I would be more glad if you can explain the working of the VI .

---

What part isn't clear? It's VISA, with formatting of data to send. You need to understand all of this before you have any change of successfully making this driver.

[enthusiast4]

Yes,I will learn and understand about VISA before implementing your VI to send data to the EA eDIPTFT70-A

[enthusiast4]

I have a basic doubt. Directly connecting the display USB cable to port (for e.g COM3) is enough to get the Interface bv VISA right? Since, in 'VISA Serial' function  , we can select the port COM3(under VISA resource name)to  where the Display EA eEDIPTFT70-A USB cable is connected. This is enough to have the physical Interface between LabVIEW and the Display EA eDIPTFT70-A (excluding the LabVIEW VISA VI code)?

[Borjomy · Accepted solution]

Spoiler

Directly connecting the display USB cable to port (for e.g COM3) is enough to get the Interface bv VISA right?

If inside in NI-MAX COM3 is present, then this is enough. The only condition for normal operation is to close COM-port when you stop VI. And do not use the Abort button.

[enthusiast4]

Can someone help me tell me what is the datatype of 'type'  in typecast (blue part in the image) , how to find it and what 255 is doing? I am not able to understand the logicPS:I am a novice in LabVIEW and trying to learn.

[Borjomy · Accepted solution]

Operation Typecast converts data from one type to another without processing. Here at the input is an array of bytes (obtained from a string), which must be converted into an array of words. Here, you could also do with the "Menu Programming / Numeric / Conversion / To unsigned long integer" transformation. It is best to do this, because in the first case the calculation of the checksum may be incorrect, as I now think. The number 255 is simply a default value, which is assigned to a non-empty array element. In this case, the array is empty, this value can be any, does not affect. The meaning of the conversion is that the sum of the byte array will exceed the number 255, which is the maximum number for the byte. Therefore, the bit depth of the representation must be increased, at least up to U16. An array of constants in this case is used only to indicate the type to which the input data is converted. Therefore, its contents can be any.

[JÞB]

---

@Borjomy wrote:

 The meaning of the conversion is that the sum of the byte array will exceed the number 255, which is the maximum number for the byte. Therefore, the bit depth of the representation must be increased, at least up to U16. An array of constants in this case is used only to indicate the type to which the input data is converted. Therefore, its contents can be any.

---

Why? You immediately mask the most significant 24 bits anyhow! 

Just let the rollover happen in the sum array elements and cast to string.  (Unless you charge on a per-primitive basis, of course.  Then its dandy!)