Jump to content
News about the LabVIEW Wiki! Read more... ×

PBD_ctrl

Members
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

0

About PBD_ctrl

  • Rank
    Active

LabVIEW Information

  • Version
    LabVIEW 2012
  • Since
    2008

Recent Profile Visitors

462 profile views
  1. PBD_ctrl

    [CR] JSONtext

    Why is "Get all Object Item Offsets.vi" in JSON Text marked as private scope? Any chance you can add it to the API? I really need the functionality and don't want to hack my install. 🤔
  2. PBD_ctrl

    JSON LabVIEW

  3. PBD_ctrl

    Tree Control API

  4. ***BUMP*** this is still active About Us: Draper is an independent, nonprofit research and development company headquartered in Cambridge, MA. The 1,500 employees of Draper tackle important national challenges with a promise of delivering successful and usable solutions. From military defense and space exploration to biomedical engineering, lives often depend on the solutions we provide. Our multidisciplinary teams of engineers and scientists work in a collaborative environment that inspires the cross-fertilization of ideas necessary for true innovation. For more information about Draper, visit www.draper.com. The Position: This position seeks an engineer with a high proficiency in developing test software for Automated Test Equipment (ATE). Software development and testing support will be performed on a host of ATE platforms implemented for evaluation and test of precision instruments, mixed-signal electronic modules and systems used for guidance and navigation applications. The candidate will be expected to support various software assignments while adhering to formalized software development processes. This includes gathering and generating formal requirements, implementing software architectures and detailed designs, developing and executing formal test plans, and supporting the packaging and deployment of official releases for end-users. The candidate will be expected to maintain software documentation and manage bugs/problems through formal tracking systems. The ability to work and succeed within a process-oriented setting is critical, as is the ability to thoroughly document and communicate one’s work. Job Requirements: Electrical Engineering, Computer Engineering, Computer Science or Mechanical Engineering Degree is required. Candidate must have experience programming in LabView, TestStand or other industry standard test automation software. National Instruments certifications not required but beneficial (CLA, CLD, CLED). Previous experience integrating and developing ATE for mixed-signal hardware devices is desired, as well as familiarity with integrating and developing software for commercial test instrumentation – Data Acquisition Modules, PCI/PXI Instrumentation, Real Time Embedded Controllers, Communication Devices. The engineer will be part of a multi-disciplinary team and will require strong teamwork and interpersonal skills in this fast paced technology development environment. This position requires US Citizenship and the ability to obtain a government security clearance. Draper is committed to creating a diverse environment and is proud to be an equal-opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, gender, gender identity or expression, sexual orientation, national origin, genetics, disability status, age, or protected veteran status. We understand the value of diversity and its impact on a high-performance culture. How To Apply: To view the job opening and apply, please follow the instructions listed below. Logon to our website at https://jobs.draper.com; register, view the job opening, and apply. 6251 - Software Integration & Test Engineer
  5. PBD_ctrl

    [CR] JSON LabVIEW

    I committed variant to JSON and JSON to variant after modifying the refnum cases to a simple I32 and string setup. I look forward to a new package.
  6. PBD_ctrl

    [CR] JSON LabVIEW

    I agree that my "=>" implementation doesn't exactly work. I like the idea of representing it as an object but I worry about opening a can of worms over a rare use case. My vote would be to keep it stupid simple at this point and go with the numerical(string for DAQmx, VISA and IVI references) implementation. It lacks the readability that I desired but I can concede for simplicity.
  7. PBD_ctrl

    [CR] JSON LabVIEW

    I see where your coming from and that was the way that I originally coded it up. Maybe it was too easy to do, but it felt useless without some sort of information about the class. My feeling was that the refnums handled by this API are only going to be valid within a LabVIEW application so it wouldn't hurt anything to throw in a class identifier. I searched around to see if I could find how other JSON APIs handle this and came up short. Do you know of any other JSON APIs not for LabVIEW that handle refnums? As for strings containing "=>" I could change it so that we search from the end of the string to get around this problem. I should also mention that I don't care that much. If it gets a new package built faster with the empty path fix to remove the "=>" and class I support it.
  8. PBD_ctrl

    [CR] JSON LabVIEW

    I figured out what I was doing wrong. Here is a list of what I changed...(there are comments in the code and the commit as well) -Added a case to handle refnums in JSON to Variant and Variant to JSON. I decided to convert the refnums to either I32 or string depending on thier type and then include the class of the refnum proceeded by a "=>". Including the class is valuable from my viewpoint in that it makes the JSON more readable. When converting from a JSON sting back to a variant I use the "Variant (Data Type)" input to define the class and ignote the class name in JSON string. -Added a case to JSON to Variant to handle paths explicitly. This fixes the empty path bug. -Removed OpenG Format Variant Into String from the default case and replaced it with Flattened String to Variant function that mirrors the default case in String to JSON. Take a good look at the refnum handling I am guessing that it will be the thing that you guys may not entirely agree on.
  9. PBD_ctrl

    [CR] JSON LabVIEW

    Did my code get added into this or did my commit fail?
  10. PBD_ctrl

    [CR] JSON LabVIEW

    I just committed my code to BitBucket for handling paths and refnums. Should the commit be showing up in BitBucket before it's reviewed? This is my first BitBucket project and I am trying to make sure that I didn't screw up and step on anybodies toes. Let me know...
  11. PBD_ctrl

    [CR] JSON LabVIEW

    I have a few ideas kicking around about how to handle refnums. Anybody else want to see the class work it's way into the string for readability?
  12. PBD_ctrl

    [CR] JSON LabVIEW

    Sounds good to me. I am new to BitBucket so excuse me if this sounds stupid but do I have to be part of the "Team" to download the source? I have SourceTree installed but I think I am blocked from contributing. If I had access I would be glad to make these changes.
  13. PBD_ctrl

    [CR] JSON LabVIEW

    After doing some testing I found that JSON to Variant can't handle empty paths. The problem is caused by the OpenG Scan Variant From String throwing error #1 because the string it is scanning is empty. A simple fix would be to add an additional case structure to handle paths within JSON to Variant.
  14. PBD_ctrl

    [CR] JSON LabVIEW

    Thanks for making the build. I appreciate everybody's help in getting these fixes made. -Pat
  15. PBD_ctrl

    [CR] JSON LabVIEW

    Thanks for the fix! I wish I had found this thread earlier. Can anybody create a new build and check it into bit bucket or is that reserved for people on the team? Can somebody get the fix into a new build? I have seen similar behavior. I can try to replicate it if anybody is interested. What I found was that if GetTypeInfo is being called by two separate application instances they block each other because it's non-reentrant. I don't think we are going to find a work around for that. This might be a unique situation that I found because of the multiple application instances aspect but I figured it was worth mentioning.
×

Important Information

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