How to store array of 'set of coordinates' into database table

[enthusiast4]

Okay, I will check about it. But, do you know why only 4 coordinates are displayed instead of 1246. Should I 'concatenate' the for loop after the wire '18' , insteaf of using the 'last value'?

[aputman]

Sorry, I do not have IMAQ library which means I can't run your code.

Are you sure that the pixel coordinates are all available before they are written to the dB?  If not, you need to check your array generation loop.

[enthusiast4]

I will check with that then. Thanks a lot for your help.

[Yamaeda]

Sounds like you're indexing the wrong dimension in the read?

/Y

[aputman]

---

@enthusiast4 wrote:

Okay, I will check about it. But, do you know why only 4 coordinates are displayed instead of 1246. Should I 'concatenate' the for loop after the wire '18' , insteaf of using the 'last value'?

---

I just noticed what you said here about wire 18 (that is actually probe 18).  Yes you are losing data here by only keeping the last value.  That could explain your issue.  Try concatenating mode and see what happens.  If you turn on indexing mode, you'll end up with a 4d array (not what you want).  

[enthusiast4]

---

@Yamaeda wrote:

Sounds like you're indexing the wrong dimension in the read?

/Y

---

Can you please elaborate it please? I didnt get you

[enthusiast4]

---

@aputman wrote:

---

@enthusiast4 wrote:

Okay, I will check about it. But, do you know why only 4 coordinates are displayed instead of 1246. Should I 'concatenate' the for loop after the wire '18' , insteaf of using the 'last value'?

---

I just noticed what you said here about wire 18 (that is actually probe 18).  Yes you are losing data here by only keeping the last value.  That could explain your issue.  Try concatenating mode and see what happens.  If you turn on indexing mode, you'll end up with a 4d array (not what you want).  

---

Correct, probe 18. I tried using 'concatenating' mode instead of 'last value', but then it throws me an error (attached image below).

[aputman]

Looks like a Region Settings problem.  Is your system setup to use a comma as the decimal place separator?  You can turn this off in Labview options->Front Panel->Use Localized decimal point.  This will force Labview to use the period, despite the OS setting.  

You can also use a different format code to in the Array to Spreadsheet String function to only use the period for this one operation.  If you don't need decimal places at all, use the format code %d.  

[enthusiast4]

Yes, I checked my whether System setting and 'comma as the decimal place separator' is already turned off. Since, Labview options->Front Panel->Use Localized decimal point is already 'checked/ticked' (in capture.png image ). I don't need decimal places at all ,so I have used %d format code in Array to Speadsheet String. VI

I have used concatenated instead of last value in probe 1 in attached image (capture2.png ). Probe 2 shows me the correct number of pixel coordinates i.e 1246 pixels instead of 4 (when 'last value' is used). But, probe 7 throws me an error of datatype mismatch criteria. This may be due to large number of pixels in a single cell of a table and the database connectivity toolset doesnt't Support it. Hope the error is resolved when I use MEMO datatype to store those large number of pixels.