v4 Driver Usbmon bidi communication

@Tom Tran (WICLOUD CORPORATION)

Thanks alot for your quick response.

1. Yes they are named and referenced correctly in my INF and .ini file

.ini:

[BidiFiles]
BidiUSBFile=DeviceBidi.xml
BidiUSBJSFile=DeviceBidi.js

.inf:

[DriverFiles] 
DeviceBidi.xml DeviceBidi.js    
[SourceDisksFiles] 
DeviceBidi.xml = 1 DeviceBidi.js = 1

2 & 3 : Yes they are copied properly.

     flq:           Copying 'C:\Users\name\AppData\Local\Temp\{e9da6035-a931-e448-a424-530237408438}\DeviceBidi.js' to 'C:\Windows\System32\DriverStore\Temp\{e03633bd-3caf-c043-ba76-7bb968f16faf}\DeviceBidi.js'.
     flq:           Copying 'C:\Users\name\AppData\Local\Temp\{e9da6035-a931-e448-a424-530237408438}\DeviceBidi.xml' to 'C:\Windows\System32\DriverStore\Temp\{e03633bd-3caf-c043-ba76-7bb968f16faf}\DeviceBidi.xml'.

4: In the Event view, i donot see any logs related to Bidi:

Thank you

Hi @Ahmad, Farooq ,

Thanks for the quick update.

Could you please try one more quick test before checking the USB Read / Write part?

Please temporarily simplify getSchemas() like this:

function getSchemas(scriptContext, printerStream, schemaRequests, printerBidiSchemaResponses) {
    scriptContext.Log("getSchemas called. Count=" + schemaRequests.length);

    for (var i = 0; i < schemaRequests.length; i++) {
        scriptContext.Log("schemaRequest[" + i + "]=" + schemaRequests[i]);

        printerBidiSchemaResponses.AddStringValue("\\Printer.DeviceInfo:FirmwareVersion", "1.0.0");
        printerBidiSchemaResponses.AddStringValue("\\Printer.Status:DeviceState", "Ready");
        printerBidiSchemaResponses.AddStringValue("\\Printer.Status:StateReason", "None");
    }

    return 0;
}

After changing this, please reinstall the driver, then open the printer properties or print a test page and check the PrintService Admin and Operational logs again.

Also, please note the Bidi path format used above:

"\\Printer.Status:DeviceState"

For Bidi values, please use : before the value name, instead of:

"\\Printer.Status.DeviceState"

If getSchemas called appears in the logs, please share that log entry and the schemaRequest[...] values shown there. If it still does not appear, please also share any PrintService error entries from the same test.

@Tom Tran (WICLOUD CORPORATION)

I did the following steps:

1. updated the getSchemas as you mentioned.
2. compiled and Signed the driver again
3. Uninstalled the old driver
4. Install the new driver
5. Stop and start the spooler
6. Added printer again and sent a print job to the printer

But still no bidi logs appeared in the logs.

Thank you

Hi @Farooq Ahmad ,

Thanks for testing this.

One important point: changing getSchemas() and then sending a print job may not fully confirm whether getSchemas() is being called. getSchemas() is used for Bidi GET queries, while a normal print job can go through a different USBMon path.

Could you please try one focused test next?

Please trigger a Bidi GET query or property refresh for one of these paths:

\Printer.DeviceInfo:FirmwareVersion
\Printer.Status:DeviceState
\Printer.Status:StateReason

The colon before the final value name is important.

If the Bidi GET path is reaching the script, I would expect this test to help trigger the log from your simplified getSchemas() function.

Also, please confirm whether USB Bidi JavaScript debugging is enabled.

Registry key:

HKLM\SYSTEM\CurrentControlSet\Control\Print

DWORD value:

EnableJavaScriptDebugging = 1

After setting this value, please restart the Print Spooler service and run the same Bidi GET/property refresh test again.

If getSchemas called still does not appear, please share any PrintService Admin or Operational error entries from the same test.

One more thing worth checking is whether the printer queue is using the expected USB port. From elevated PowerShell, please run:

Get-Printer -Name "<printer name>" | Format-List Name,DriverName,PortName

Then use the PortName from that output here:

Get-PrinterPort -Name "<port name>" | Format-List *

If the Bidi GET test still does not trigger getSchemas(), this may point to something before the USB Read / Write logic, such as the queue/port binding or the Bidi file association for this installed queue.

@Tom Tran (WICLOUD CORPORATION)

Thanks for your response. Upon restarting the spooler i got linked to debugging. Here is the error i got:

Thank you.

Best Regards,

Farooq