drjdpowell

JSON is always in UTF-8, and JSONtext will try and convert to your computer's character set automatically, so I don't think you need any of that stuff that has "UTF8".  Try simply using the single function to convert to a 2D array of strings.

However, by sure you are actually passing true JSON, with UTF8 encoding, not whatever your computer is using.  

I checked that it works for me, in LabVIEW 2021.  Does code this simple fail for you:

Does that DLL exist at the stated path?

Can you give an example VI showing the problem.  It seems to work in teh current source code.

I think this is teh same issue as this: https://forums.ni.com/t5/JDP-Science-Tools/Cannot-Install-JDP-Science-Common-Utilities/m-p/4418396#M205

The SQLite package requires JDP Common Utilities, and that package seems to have a problem.   Workaround is to download it and have VIPM install it directly, rather than try and get it from the Tools Network servers (it's a server issue, not a problem with the package itself).  I'll attach it here as well.

Try installing this and then retry installing SQLite.

jdp_science_lib_common_utilities-1.4.1.18.vip

11 hours ago, Dpeter said:

I wonder if it is because the DVR section is not a type def or a strict type def.

Does making it a typedef prevent the problem?

1 hour ago, ciozi137 said:

When I added the existing PQ classes to PQ.lvlib I had to fix an error inside "Connection Record.vi" unbundle to get the DVR.

What was this error?  I can't seem to reproduce it.

I will change the terminal name to "Format empty input as null" to prevent reading it as referring to JSON Strings in the input rather than the entire LabVIEW string.   And I'l try and give a better description:

I confirmed the behaviour on my machine.  It is that the Write doesn't pass the file reference through if there is an error in.  Seems like a bug to me.

7 hours ago, codcoder said:

if there is an error in to the Write to Text File the file refnum becomes invalid

I just checked, and it doesn't close teh file reference, but it does pass out a null reference.  The original reference is still valid.

This is still unexpected behavior, though.

Yes, Queues don't make unnecessary copies, but User Events make two copies, so the EventDVRmessenger is just to work around that.

On 7/29/2024 at 2:58 PM, Sam Dexter said:

Dear colleagues and Dr. Powell (hopefully),

I'm sorry, you posted just before I went on a full month of holiday and I never saw this.  Do you still need help?  Any further info?

Has anyone had a chance to use teh new version?  At least as far as trying the new examples.

On 11/10/2023 at 2:09 PM, ciozi137 said:

Sounds good. I will make pull requests as I work through the open issues. I'll stay with LV 2017 for now per updates from @Antoine Chalons

I have published a 0.3.1 package on VIPM.io with Antoine's changes (LabVIEW 2017).  Then I've accepted your Pull Requests and published a 0.4.0 version as well (LabVIEW 2019):

https://www.vipm.io/package/jdp_science_postgresql/

I think your second point is wrong; VIs without the front panel loaded don't use any resources.  EXEs don't even include the code for those front panels.  

I think this is a Windows touch-screen behaviour, due to Windows using press-and-hold to give a right click.  Windows waits for the release before sending "mouse down" so it can decide to make it a right click or not.  It's annoying but I have not found a way around this.

Note the WITHOUT ROWID keyword also, as that could make a significant performance improvement with this kind of table.

A non-JSON option you could try is:

CREATE TABLE TestData (
  Channel,
  Time, 
  Data,  -- individual reading at Time for Channel
  PRIMARY KEY (Channel,Time)
  ) WITHOUT ROWID

This is every reading sorted by a Primary Key that is Channel+Time.  This makes looking up a specific channel in a specific Time Range fast.  

BTW, you don't need to make an index on a Primary Key; there is already an implicit index . 

You would select using something like:

SELECT (Time/60)*60, Avg(Data) FROM TestData
   WHERE Channel=? 
   AND TIME BETWEEN ? AND 1717606846
   GROUP BY Time/60

Why don't you just try it?  Open your SQLite viewer app if choice and execute "SELECT * FROM sqlite_schema"

You're looking for the sqlite-schema table: https://www.sqlite.org/schematab.html

8 hours ago, CT2DAC said:

Cannot install versions more recent than 1.13 with VIPM - error: unable to download from repository.

Do you have the latest version of vipm?

Yes, at some point I intend to make an interface that has "to JSON" and "from JSON" methods, that one can inherit from.  But at the moment JSONtext is based in LabVIEW 2017.

15 hours ago, X___ said:

Raised here: https://bitbucket.org/drjdpowell/jsontext/issues/103/what-to-do-about-complex-numbers

I will fix the inconsistance, either by making comlex numbers full not supported or fully supported.