Jump to content

FixedWire

Members
  • Content Count

    36
  • Joined

  • Last visited

  • Days Won

    3

FixedWire last won the day on March 25

FixedWire had the most liked content!

Community Reputation

4

About FixedWire

  • Rank
    More Active

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2015
  • Since
    1998

Recent Profile Visitors

1,001 profile views
  1. The LV TLS examples led me astray with the X.509. Mind numbing indeed but the DUT firmware needs to be written over Bluetooth. And that I can understand needs to be secured being a med tech device. ...of course IT is all over this right from the get-go. So the real question is how to secure a BT connection with X.509? Or better yet, I'd like to provide the client with a solution that works on our end first.
  2. Client: "And we need you to securely write the firmware to the DUT using X.509" I'm trying to get a better understanding on how to use X.509 certificates and deciding if the new TLS functionality is the best approach. The examples for using TLS are a bit sparse... If someone could share their battle scars or provide suggestions it'd be appreciated. btw, thank you Neil Pate for posting your code!
  3. "Available in LabVIEW 2020 and later: the TLS functions are available in the Functions > Data Communication > Protocols > TCP > Transport Layer Security (TLS) palette." I'm posting here in case someone comes along like myself after stepping into a deep "let's secure this" hole and needs ideas or hasn't seen this yet.
  4. Cross post, Hopefully someone here can shed light on the why authention with the LabVIEW HTTP Client VIs isn't working. I've heard that you need to register the SSL? Does anyone know more on this? Thanks a bunch.
  5. I'm also getting authentication issues to an Apache server. Did you ever resolve this? For anyone else, this may help: cross-post: How Do I Change the Default SSL Certificate That Ships with LabVIEW? https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019YHDSA2&l=en-CA Securing Web Services with SSL https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019N27SAE&l=en-CA
  6. Thank you JKSH! The first step was to find a way to call the java libraries (i.e. the customer's BT interface) from LabVIEW & get it working. The validation introduces another layer all together. Have you used the IKVM?
  7. Hi everyone, The client is asking to connect to their DUT using their own BT (validated) Java driver. Creating a wrapper dll for the SDK really complicates this as it will need to be validated. The http://weblog.ikvm.net/ .NET interface seems dated and no longer supported. Does anyone have any ideas on the best approach? In short, the client decided on java as a "simple" way to connect to the DUT for R&D, testing & production environments.
  8. This solved an issue of not knowing which additional dll's to include when building the exe. One dll may call a number of other dll's etc. Used PowerShell & ran the following: [Reflection.Assembly]::LoadFile('C:\absolute\path\to\my.dll').GetReferencedAssemblies() This neatly produces a list
  9. To all the warriors out there a heads up if your computer is suddenly running at 100% CPU. In the Task Manager, the Task Manager process will gobble up any CPU available. I swore it was a virus. A 3rd party tech support knew about this. Turns out a camera did not shut down correctly. To avoid Windows willy-nilly starting a process it likes that will screw up tasks such as frame grabbing response this Windows setting is used. Use PowerShell & run the following: "C:\Program Files\Point Gey Research\FlyCap2 Viewer\bin64\PGRIdleStateFix.exe enable"
  10. Since there's still an issue with 32 working (but not on some machines) & the 64 bit hanging when trying to relink the dll to the installed PQ libraries, I tried to create the CIN wrappers automagically. The process gets stuck and becomes beyond my current knowledge. Don't know how you did it but kudos to you Mr. Powell! I'm sure you wrestled with this a bit. 😬 Looks like multiple .h files need to be referenced. libpq.dll needs the libpq-fe.h which in turn needs the stdio.h, postgres_ext.h & pg_config_ext.h according to: https://doxygen.postgresql.org/libpq-fe_8h.html
  11. Yes, correct Rolf. The target was the enterprise version & that's why it ran in the first place. Interestingly enough installing the exe on 3 other machines under Win10 resulted in the 2 working & the 3rd not finding the dll just like the Win10 IoT. With a new build it suddenly didn't find the dll on one that did work. With not having time to debug I created an installation and the program worked since even with new builds. On regular Win10 there shouldn't have been an issue... At this point I'll try and link the latest 64bit Postgres dll's & try that.
  12. If Postgres is already running on the Win 10 IoT box, I should be able to link the CINs to the same installation C:\Program Files\PostgreSQL\11\bin. Theoretically. LabVIEW 64bit hung up when linked to these installed dll's. Hence using the 32 bit dll's supplied & going that route in the first place. It just worked. Note that there also some changes such as libint.dll likely replaced by the libintl-9.dll in the \11\bin directory. Win 10 IoT Enterprise should be able to run regular programs where as the Core version is limited to UWP apps (understanding this requires ARM compiled c
  13. On a regular Win10 box the exe loads the dll's just fine & then times out as expected without Postgresql installed. So it's looking a lot like a Win IoT issue... My understanding is that you wrapped 32 bit dll's with a CIN. Looking at does-windows-iot-support-my-dll the answer was: Windows IoT required DLL to be as follows: Compiled using the ARM target Needs to target .NET Core Those restrictions strictly apply when using UWA you may be able to get away by using a console app but it is not that simple on IoT as everything is sandboxed
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.