Jump to content

Jim Kring

JKI Team
  • Content Count

    1,365
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by Jim Kring

  1. Lars, As Philippe mentioned, it's important to use the Variant to Data function to convert to your expected data type: For examples, you might want to take a look at the EasyXML examples that ship with the product, which are located here: \examples\JKI\EasyXML\ Let us know if you still have issues. -Jim
  2. Hi Lars, You are right. EasyXML doesn't support 2D (multi-dimensional) arrays, at this time. I would recommend writing this data as a 1D array of clusters, as shown below: <CT-Unit> <No>16</No> <Name>GE LightSpeed Pro 16</Name> <Phantom>Head</Phantom> <BQ>Head</BQ> <kV>120</kV> <k>1</k> <Sensitivity></Sensitivity> <CT-Unit> <CT-Unit> <No>17</No> <Name>GE LightSpeed Ultra, 8 slice</Name> <Phantom>Head</Phantom> <BQ>Head</BQ> <kV>120</kV> <k>1</k> <Sensitivity></Sensitivity> <CT-Unit> You should check out the recent EasyXML Tips and Tricks post, Creating ordered elements in XML, for more information on how to do this. The reason EasyXML doesn't support multi-dimensional arrays is that, for the first version of EasyXML, we wanted to limit the number of data types supported to those necessary for generating and parsing any XML data. XML does not have any concept of a multi-dimensional array, so we left this out. You might be interested in reading the following FAQ entry for more information on this decision: Why isn't every LabVIEW data type supported by EasyXML? Please let me know if you need any more pointers on getting your application working with EasyXML. I'm happy to help Thanks, -Jim
  3. Hi Bee, I'm not sure who you tried to contact, but you're talking to the right people, now For installing EasyXML onto LabVIEW 8.5 on the Mac, you should follow the method described, here. I realize that this is not an ideal solution -- we're working on improving it. If this technique doesn't work, please let us know and we'll try to help you out, by some other means. Thanks, -Jim
  4. Hi Ton, Thank you for reporting this. Currently, VIPM only supports LabVIEW 6.0 or greater. You are right about the bug. VIPM should have told you that it cannot be used with older versions of LabVIEW. I've created a tracking number (Case 5342) for this -- it should be resolved in a future version of VIPM. Thanks again, -Jim Kring
  5. Hello Arne, > Thank you... It was exactly what I needed. You're very welcome. I'm glad the example helped. > collecting the data together with oceanographical and meteorological data, saving them on board and also sending them to HQ via satellite That sounds like a very interesting and cool application, and I'm happy to hear that EasyXML will be part of your system Please let us know if you have any more questions, issues, or ideas for how we can make EasyXML better. Thanks, -Jim
  6. Hello Arne, Greetings from the United States and welcome to the JKI discussion forums! We're glad you've joined us Yes, I see what you're trying to do -- you wish to modify only a subset of an XML data structure (string). EasyXML does support parsing a subset of an XML data structure but the XML it generates is "1 to 1" -- the output XML string contains exactly what is in the input cluster. Modifying a subset of the XML string is a feature that we're considering for a future release. In the mean time, you might consider using the MSXML parser to poke at the value you need to change. I've written an example that modifies the baud rate in your example XML string (see attachments, below). Please, let me know if you have any questions about this example. And let me know how your project goes -- I'm happy to provide pointers for using EasyXML and/or MSXML and want to hear about your successes and issues in using XML. Thanks, -Jim Example VI (LabVIEW 8.5) Set_Baud_Rate_using_MSXML.vi Front Panel Block Diagram
  7. The trail version of EasyXML is full-featured, but will present a periodic dialog, telling you that it is a demo version. This provides you with the ability to try out the full capabilities of the software.
  8. Bob, I've added this to our FAQ, here, so that your efforts can help others who might experience this issue: Why can't I see EasyXML in the Functions palette? Thanks again for your patience in getting EasyXML installed. We're looking at ways to improve VIPM to avoid this problem, in the future. Thanks, -Jim
  9. There are a few things you'll want to check, if you can't see EasyXML in the Functions palette: Verify that VIPM's LabVIEW Version Selector is set to the same version of LabVIEW on which you're installing VIPM. Verify that you have EasyXML (jki_lib_easyxml) package installed Verify that you have the JKI Toolkits (jki_rsc_toolkits_palette) package installed Run VIPM Check the network for packages (by selecting Tools>>Check the Network for Available Packages from the menu). Find jki_rsc_toolkits_palette in the package list and install it (right click and choose install) Restart LabVIEW [*]Make sure that you restart LabVIEW after installing any packages You should now be able to see EasyXML in the palettes (as described here). See also: Where can I find the EasyXML VIs in the LabVIEW Functions palette?
  10. Hi Stian, I'm glad that worked for you. Vista is a new beast to all of us. I'll add this issue/solution to our Vista FAQ, so it can possibly help others trying to do the same thing. Thanks, -Jim
  11. Hi Stian, I see that you are running Windows Vista (from the cool aeroglass windows) While Vista is not officially supported yet by VIPM (due to some issues like the one you're seeing), the following work-around should resolve the issue: 1) close VIPM 2) run VIPM as administrator (right-click on VIPM and choose the run as administrator option) 3) doubleclick the ogp package file of the paid version of EasyXML and install it Hopefully that works for you. Please let me know how it goes. Thanks, -Jim
  12. Hi Bob, The reason that nothing happens which you click the Detailed Help button is that there is a LabVIEW bug that affects about 1 in 20 people, where HTML documentation doesn't launch from the Context Help window. I'm not sure why this is happening. You can find the documentation, here: \help\JKI\EasyXML\JKI_EasyXML.htm We also have some documentation on our website, here. Chris pointed you to a great page about how to use the Example Finder to "browse" for examples. You'll find that all the EasyXML examples are located under JKI>>EasyXML, if you browse -- this is the \examples\JKI\EasyXML folder, beneath LabVIEW. You might also want to check out the EasyXML>>Tips and Tricks discussion forum. In particular, the Generating and Parsing Scalar XML Elements with Attributes post contains some great examples of how to use EasyXML. Thanks, -Jim
  13. Hi Bob, That's great news! I'm glad you got it working. Yes, there is a lot of other very useful stuff that comes along for the ride with VIPM -- check out the OpenG functions palette for lots of great VIs. You can learn more about OpenG software, here. Thanks, -Jim
  14. Hi Bob, crelf's suggestion is a good one. Make sure that you've installed it on the same version of LabVIEW that you're trying to find it in the palettes. If that doesn't solve the problem, the most likely reason that you can't see EasyXML in the functions palette is that the jki_rsc_toolkits_palette package needs to be installed, which is one of the dependencies of the EasyXML package. Here's how you can make sure it's installed. Run VIPM Check the network for packages (by selecting Tools>>Check the Network for Available Packages from the menu). Find jki_rsc_toolkits_palette in the package list and install it (right click and choose install) Restart LabVIEW Also, make sure that all the required OpenG libraries are installed, as mentioned, in the system requirements. Please let us know if that works for you. Thanks, -Jim
  15. Keith, That's great news! I'm happy that the solution will work for you. We're looking forward to having you as a customer. Have fun at the birthday party -Jim
  16. Hi Keith, We're happy to hear that you like EasyXML Regarding your question, you will need to parse the LOCK_MASS element as a scalar string and then use LabVIEW's "Spreadsheet String to Array" function to convert the string into a 2D array of numeric data. Here's an example (below). This might not be exactly what you were hoping for, but the designers of the LOCK_MASS xml schema chose to use a spreadsheet string instead of xml elements to represent the LOCK_MASS data. Trying to support spreadsheet strings as an EasyXML data type would be very tricky. Thanks, -Jim PS - Generating and parsing scalar elements with attributes are not as obvious as other xml structures. You might want to take a look at this tip: Generating and Parsing Scalar XML Elements with Attributes. Example VI Parse_LOCK_MASS.vi Front Panel Block Diagram
  17. Sometimes, you want to explicitly state the order of XML elements. XML doesn't natively support element ordering. So, if you have XML that looks like this, you can't deterministically say that the element with "foo" data comes before element with "bar" data. <element> <data>foo</data> </element> <element> <data>bar</data> </element> <element> <data>monkey</data> </element> <element> <data>fish</data> </element> You can get around this XML limitation by explicitly adding an order/index attribute to your ordered elements. For example: <element n="1"> <data>foo</data> </element> <element n="2"> <data>bar</data> </element> <element n="3"> <data>monkey</data> </element> <element n="4"> <data>fish</data> </element> In order to work with data like this, you'll need to pre-populate the "n" attribute before you generate the XML and you'll need to post-process the "n" attribute after you parse the XML. Here's an example, that demonstrates this technique: Example VI Element_Ordering.vi Front Panel Block Diagram
  18. One of the great features in VIPM Professional is the ability to create VI Package Configurations (or VIPC files), which are a snapshot of the packages installed in a given version of LabVIEW. One question that we get a lot at JKI is: If I am using source code control, why do I need VI Package Configurations? When you keep your project files in a source code control system (such as Subversion, Visual Source Safe, Perforce, etc.), it is important to realize that the LabVIEW User Libraries (user.lib) folder is not under source code control, since it's not beneath your project folder. This means that you have no configuration management of the OpenG, 3rd party, and in-house reuse add-ons that are installed in LabVIEW. A VI Package Configuration file stores a configuration snapshot of what's installed beneath LabVIEW, so that you can easily restore that state when you are going to work on your project. When you create a VIPC file and keep it in your project folder (which is under source code control) you are effectively keeping your LabVIEW user libraries folder under source code control, on a per-project basis. This capability is the part of LabVIEW project configuration management (source code control) that's always been missing.
  19. Hi Stian, That's great! I'm happy to hear that you are a customer I'll keep you in the loop about the fix for this issue. And, that's an excellent suggestion about more descriptive error messages. We certainly have that on our road map. Thanks, -Jim
  20. Hello Stian, Thank you very much for testing EasyXML, and welcome to the discussion forums We greatly appreciate you taking the time to tell us about the issue you found and for providing a detailed description about how to reproduce the problem. I was able to reproduce it on my system and I have created a tracking number and known issue, here: Known Issue (Case 5244): Can't parse array of time stamps If you decide to purchase EasyXML, we can provide you with early access to an version of the software with a fix for this problem. Thanks again, and please let us now if you have any more issues or suggestions. -Jim
  21. Versions Affected: 1.0 Fixed in: Pending Parsing time stamp in array fails with "Error 1 occurred at (Unexpected Datatype )". For example, can't parse the following: <times> <time>1903-12-31T13:00:00.000-08:00</time> <time>1903-12-31T14:00:00.000-08:00</time> </times> This was first reported, here.
  22. Hi Daklu, Thanks for the feedback. We're happy to hear you like VIPM and OpenG Regarding the port test and error dialog, I agree that this is an area where VIPM could be greatly improved. There are a few things that we're looking into: 1) Auto-discovering LabVIEW versions, so that you don't have to browse to the EXE location on disk 2) Recommend that the connection to LabVIEW has been adjusted/tested before the user proceeds, when adding a new LabVIEW version. 3) Have a better error dialog that includes a description of how to correct the problem (as you have suggested) Regarding adding additional package information, such as release date and production status (alpha, beta, deprecated, etc.), that's an excellent idea and we're looking into it for a future release. Thanks again for the feedback. We appreciate you taking the time to tell us how we can improve VIPM. Regards, -Jim
  23. I'd be happy to chat with you more about your requirements, off-line, and see if there's any tips I might have for you. Please send me an email -- you've got my contact info
  24. Hi Travis, VIPM downloads information from a JKI server that tells it about new packages and new versions of VIPM. Are you looking to do something similar in your software? Thanks, -Jim
  25. Hi Jason, I've updated the Generating and Parsing Scalar XML Elements with Attributes tip with the List of Scalar Elements with Attributes example that you suggested. Thanks again for the great idea! Also, I've split this discussion off into a seperate thread, to clean up the original posting. Thanks, -Jim
×
×
  • Create New...

Important Information

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