Does exist a standard protocol for network printers? Some network printers require the installation of drivers to be used... Is there some network printer that can be used without installing additional drivers? After all, when we connect the network cable from the laptop to the router, we do not need to install drivers (any operating system already includes the driver).
Are there any open source projects related to protocols for communication with a network printer?
The standard protocols are the LPD or IPP protocols.
If you need to talk to a printer over the network, you can either attach it to a device that translates packets into USB/LPT commands, or attach it to a linux/windows PC and print through an LPD service running on that OS.
IPP Everywhere tries to be what you are asking for.
A PWG standard that allows personal computers and mobile devices to find and print to networked and USB printers without using vendor-specific software.
Related
I'm trying to write a Cisco CDP protocol driver for Windows IoT core running on Raspberry Pi. This will allow me to register the installed location of the device with an upstream server.
To do this, I attempted to use the sample NDISPROT example as part of the Windows DDK Samples. This failed because the project is seemingly inherently incompatible with Windows IoT (specifically ARM)
What I need to do is write a protocol handler that operates on raw Ethernet packets as CDP is built on 802.2 LLC which is very different than 802.3. To do this, on Windows, I would write an NDIS 6.x protocol driver, cache the latest CDP frame from each source, then use DeviceIOControl() to communicate with the device to download the latest CDP packets or upload formatted CDP packets.
Is there a boilerplate driver I could use to do the same on Windows IOT Core?
Unfortunately there's not a way to install NDIS protocol drivers onto Windows IoT Core right now. (The OS doesn't understand the INF dialect used by netcfg.)
This feature is on our backlog. You can help raise its priority by sending feedback directly to Microsoft (either via the feedback hub, forums, or by emailing the IoT team directly).
I'm trying to set up a Wi-Fi repeater on Ubuntu PC or embedded Linux with Wi-Fi dongles, using one dongle at a time. Drivers and firmwares for dongles are done and worked on my PC/embedded board for AP mode and station mode. Then what can I do next?
In my thought, I have to simulate 2 interfaces with only 1 dongle. Than run Hostapd on a interface, run wpa_supplicant on another interface. Is that a workable method? If yes, how can I "create" 2 interface with 1 dongle, say, wlan0/wlan1 or wlan0.1/wlan0.2 or something like that?
Is the whole scenario workable just through some operation about interface and system, or the scenario MUST be supported by driver of dongles, if driver doesn't provide this scenario, then it is impossible?
I tried it on Ralink Soc before(it's called ap-client mode by Ralink). On Ralink platform with its own SDK including Linux source and Wi-Fi drivers, it is done by iwpriv commands. There are interfaces call "apcli0" to work in station mode and "ra0" work in AP mode, but there is only 1 physical Wi-Fi interface built-in in Ralink Soc. It works just fine but I'm not using Ralink Soc now. Is that feature also available for other dongles?
After working on driver compiling, I got some idea.
The chip I'm using supports "dual mac" feature, and the driver must support this feature.
If the driver is successfully compiled, inserted and the dongle is plugged in, there will be 2 interfaces coming out, for example, wlan0 and wlan1. Therefore I can configure one interface as AP and another interface as station.
So the key point is the chip and driver must support dual mac feature.
I want to write a program which will "lock" a computer to a user determined wireless network.
It should automatically establish and maintain the connection with the specified network
Other networks should be hidden and/or inaccessible while the program is running
Should be compatible with Windows XP - 8
Should work for all wireless cards
Could I create an NDIS filter driver or NDIS intermediate driver for this? Which one is a better option? Also, the MSDN documentation I linked does not seem to provide good information about how to actually write the driver, where can I find that?
I'm developing a virtual printer to accept print jobs and route them to real printers in a LAN. I'm hoping to create a postscript printer to act as a shared virtual printer to accept print jobs from the LAN, I hope to develop it through ghostscript and redmon.
If you can please let me know any online resources, examples or any tutorials on hows to create a postscript printer on windows 7.
Thank you very much, please let me know if you know anything.
It will be easier to use an existing PostScript printer driver (such as a generic one provided with Windows), and then instead create a port monitor. You will need to use the Windows Driver Development Kit (freely available) in order to create a port monitor. Once you have created your port monitor, you can install a printer using any driver, but tell it to communicate via a port that your monitor will intercept.
You will end up getting the exact data that would have been sent directly to the printer had it been configured to use an IP or other port instead of your port. For example, you can create a port called “ZERONE:” which is monitored by a port monitor called “Zerone Port Monitor”.
MSDN has a sample for a port monitor that interacts with infrared devices, although it will give you an idea on what you need to do so that you can communicate with other devices on a network.
Alternatively, and perhaps more hackishly, you can create a port called “C:\doc.prn”, and any document that is printed will be saved as PostScript to “C:\doc.prn” (provided that the printer driver is a PostScript driver).
I am very enthusiastic in writing device drivers for a microcontroller(like PIC, Atmel etc).
Since I am a newbie in this controller-coding-area I just want to know whether writing device drivers for controller is same as we write for linux( or any other OS) ?
Also can anyone suggest some online device driver building tutorial for the same ..?
Thanks,
If you are thinking about developing the device drivers to interface your device with a host computer (probably using USB), then most of the microcontrollers nowadays implement default classes that rely on native drivers.
A concrete example:
If you use a PIC18F4555, you can use the regular HID (human interface device) windows driver to communicate with your microcontroller (given you implemented it correctly). No need to develop any driver.
Writing a device driver for an MCU is a pretty far cry from writing it for a OS. Most MCUs won't have an OS running on them at all. You'll generally end up writing some low level Interrupt Service Routines (ISRs) and filling up buffers, that your application software will end up emptying. You don't have to fit into any device driver paradigm that an O/S has defined. You basically have to read the datasheet for the device you are wanting to interface with and read and write to its memory over whatever interface it might use (e.g. SPI, I2C, UART, etc.). Ultimately the device driver ought to provide intuitive function calls to the application software.
If you are using AVR MCU like atmega then you can use vusb (https://www.obdev.at/products/vusb/index.html) for those MCU that don't have any HID and handles the interrupts by connecting D+ and D- pins of the USB to digital I/O ports of the MCU.
The atmegaU2 packages have their own USB communication ports and HID.