10-16-2018 12:46 PM
I made a VI to record CAN data. It ran fine in the full development software. I wanted to share the software with someone so I created an exe. It doesn't seem to be running properly when run as an exe. I first selected the correct COM port, and I've updated the device firmware in MAX. I made sure that XNET was installed, first run-time, then we tried the full XNET, and also that the database file was transferred to their machine as well. I also updated MAX. When I try to change database files, even though it was built with the correct one as default, none of the options take me anywhere. Nothing happens when I click on them, and when I run the exe, I see no data. It runs but it's not seeing what it should. I checked it in bus monitor and that worked fine.
10-17-2018 10:06 AM
That list of databases comes from the XNet Database Editor. On your development system if you run the XNet Database Editor, you can go to File >> Manage Aliases and you'll see all the aliases and the file paths to the databases used.
On a new computer there is no databases setup, and no aliases made. You either need to setup a database and alias on this new machine, or you need to programatically invoke the import of a database so it shows up in your list. In your situation it is probably just easiest to select Browse for Database File... and select the same file you have on your development machine.
If you want to get fancy you can include the database in your EXE so it is included in the build. And then during startup you can use the XNet Add Alias function, to add the database.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
10-18-2018 09:58 AM
I did include the database file with the build. That didn't work. I then just added the database file onto the second computer's desktop and thought I could select that file with the "Browse for Database File...", but that along with any of the items in the drop down list had no affect. I would click on them and nothing would happen.
10-18-2018 10:18 AM
Ahh okay in that case the XNet Database Editor isn't installed. Could you find it in the start menu on the second computer? I'm guessing you can't but it is in on the first computer. In that case you need to install it, and it can be done a couple ways. First you could download the full XNet install (here is XNet 18.0) and install it. Or when you make your installer, have it include the full XNet not just the runtime engine for it. When selecting additional installers you have the option to only include runtime engine stuff. If you turned that off, and manually selected XNet you can choose to include the full XNet which includes the database editor. Image below.
Also including the database in your application isn't enough. What you really need to do is include it and then on first run import it using the database tools. But in this case it might just be easier to install XNet, and add the database manually.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
10-26-2018 08:56 AM - edited 10-26-2018 09:22 AM
I'm currently experiencing the same issue. Built the application and deployed it to a new target. But in my database selector, clicking on any of the options - Browse, New, Edit, Manage - does nothing. I've already installed the full NI-XNET (not the runtime), and it's still not working - and I've deployed to 3 different PCs now. (2) Win7, (1) Win10, and not a single one is working.
EDIT: I found that while I installed the XNET full program, if it doesn't install any of the development tools, it doesn't install the database editor or any of the other required tools, and installs just the XNET Runtime. It is absolutely absurd that I must deploy the development portion of XNET to allow users simply to select which database to use.
10-26-2018 10:02 AM
Did you try any of the other suggests I made which don't require the full install? The Database API should work in the runtime so programatically importing a database should work and then the drop down will show the databases that have been imported. Honestly the other solution of including the full as an additional installer is all I've done since discovering that the Database Editor isn't included in the runtime only version.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord