I want to ask some help info regarding the USB component
1- If I change the VID/PID and vendor names and generate the driver in the Properties panel and then add the generated inf file to the supplied driver package as below and install the driver will the new device be known by windows
P1.jpg (61.61 KiB) Viewed 5862 times
Changing these properties (below)
P2.jpg (53.1 KiB) Viewed 5862 times
will it show up here with the new properties
P3.jpg (34.02 KiB) Viewed 5862 times
I am also thinking for testing to use a Labview project can I use the Miac DLL for LV with no license issues from MATRIX or technical issue
I tried generating the inf file for the Custom driver as shown in the wiki may be I am justr to old howver I cannot select Yes for generating the driver ,
if I select the "Yes" property it immidialtly goes to no again ,
If I compile the project I have no inf file .
In my understanding from the Wiki after the generation of the inf file the property will automatically go to "No" however this is working in reverse with me
Please help!
I tried generating the inf file for the Custom driver as shown in the wiki may be I am justr to old howver I cannot select Yes for generating the driver ,
if I select the "Yes" property it immidialtly goes to no again ,
If I compile the project I have no inf file .
In my understanding from the Wiki after the generation of the inf file the property will automatically go to "No" however this is working in reverse with me
Hi Peter,
I've just tried this and it seems to be working ok. Changing "Generate Driver" to "yes" will create a .inf file in the same location as the .fcfx project file and then the "yes" will flip back to "no". Changing this property causes the .inf file to be created, and not compiling the project.
FYI: it is done this way because (currently) there is no way to have a button press event for a component property. What we do instead is detect that this property changes to "yes" and then this triggers the event as if a button has been pressed. The component then automatically flips the property back to "no" once the event has been actioned.
Regarding the "timeout" issue, this seems to be a bug and hopefully Ben will fix this soon.
Thank you so much,
I was looking in the directory looking for an filename.inf extenion and did not see one but after your reply pulling me out of this endless loop
I found the filename that is showed in the Properties I guess it this one I will try it now
Hi Steve,
I have replaced the mm_mchpusb file in the driver files from the wiki and try to run the exe for my win10 64 bit machine and I get the following error
the error is in German it means the" DPInst.exe can not be executed on this Operating system " Sorry of all the trouble I am causing