Jump to content

FixedWire

Members
  • Posts

    43
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by FixedWire

  1. We ended up finding a relatively simple solution using command line calls from http://srecord.sourceforge.net/ At least there is source code if it is ever needed and it's compiled unlike the Python approach. For what we need the risks can be mitigated. Thanks everyone. It's just incredible to have such resources available. Kudos to all.
  2. Thanks Rolf, Sam. This certainly helps and the vi gives a lot of detailed insight. The validation is the rabbit hole. If I use the simple InteHex Python code, as there a way to "lock down" a Python module so the Python dev environment isn't available for someone to access?
  3. Appreciate that Neil! NI Support didn't find anything right away either.
  4. Hi everyone, After searching both forums I've not been able to source a way to easily create either file format. There are examples reading these files but not writing them. Segger simply gave the Python script below. Unfortunately we can't simply just install Python as this is in a regulated environment. So we're hoping for a native LabVIEW solution. Surely someone has done this before. It gets a bit complicated if we need to roll our own down to the bit level & then having to do a full validation on it. I'd really rather not go there. Thanks in advance! python script (the "intelhex" does the heavy lifting) from intelhex import IntelHex h = IntelHex(None) h[0x1000] = 0x12 h[0x1001] = 0x34 h[0x1002] = 0x56 h[0x1003] = 0x78 h.write_hex_file('patch.hex')
  5. I've automated https://www.gurock.com/testrail/ (owned by the same company as Ranorex). It was a few years ago so a few things might be better now. Wasn't a bad experience with the api and allowed the integration to jira. The prime area of interest for the client was the ability to combine different specifications for a product. ... there are a lot of different automation tool concepts.
  6. Just be really careful if you intend to used packed libraries. Start building the exe & ppls now. It is not trivial. It's of limited use if it can't be deployed. This is the best documentation I've found yet. Effectively_Using_Packed_Project_Libraries_SEPAD.pdf ‏2772 KB https://forums.ni.com/t5/NIWeek-Session-Content/Software-Engineering-Processes-Architecture-and-Design-nbsp/ta-p/3929895?profile.language=en
  7. 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.
  8. 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!
  9. "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.
  10. 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.
  11. 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
  12. 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?
  13. 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.
  14. 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
  15. 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"
  16. 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 Just selecting a few basic options like open/close was not successful & returned: "The library specified for this node cannot be found or cannot be loaded." Do you remember how you did it?
  17. 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.
  18. 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 code). what-s-difference-between-windows-10-iot-versions I think Win IoT is mulching things somehow where regular Win 10 accepts the dll's. Looks like the best approach for right now is to remotely get into the database via the localhost/IP address and run things on a laptop. Your help's been very appreciated!
  19. 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. Otherwise the other way to use the DLL on the Pi is to run a nix OS like Raspbian, install the latest MONO and then you can embed DLL's into your projects and it should just run, even if targeted for x86 - Thanks to all the clever stuff mono does.
  20. Correct, the above is exactly the same for the build & works from different directories on the dev machine. It's on the deployed machine it gives errors. In the Build properties for the exe I've tried to set the destination to a specific path but it didn't help. Perhaps I missed something?
  21. Thanks to the nice work of drjdpowell I was able to easily connect & work with PostgreSQL. Did have to use the 32bit included dll's though. Now when I try to install & run it on a Win10 IoT machine the dll's are not found and throwing errors. Sorry no screenshot at the moment. The 64bit of PostgreSQL is installed on both machines & works. The exe of course works just fine on the dev machine. Does anyone have any ideas? I'm at a loss at the moment & need to get this running. Thanks.
  22. Thank you Paul. Nice work. Sweet. Thank you all!
×
×
  • Create New...

Important Information

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