Raspberry Pi 4B Touchscreen Industrial Controller
Budget: $250 – $750 USD
I need a Raspberry Pi 4B setup to act as a touchscreen controller for industrial machines.
Requirements include:
- Interfacing with vendor-specific touch screen hardware
Ideal Skills and Experience:
- Experience with Raspberry Pi
- Proficiency in touchscreen interface development
- Knowledge of industrial machine control systems
- Familiarity with radio communication protocols
Please provide relevant experience in your bids.
Hey All, this is the 4th time I'm reposting this project. Please don't bid without reading the requirements and checking the attached mitm dump!
Project brief:
I need the raspberry pi to act as touch screen emulator, matching the hardware of the dump (attached).
And to be able to accept coordinates for x,y click.
Project details:
I've been trying to crack this for 10 days now, with multiple freelancers and the help of multiple AI tools.
Here is the main issue - if the raspberry pi acts as HID device, the host machine expects calibrated values (after touch screen calibration). While in normal case, hardware controller connected to the host, after calibration the touch screen controller keep sending raw x,y coordinates and the host does the calibration on its own. HID device works, but since the screen is in portrait mode, using only the bottom 1/3 of it for touch area, the coordinates shift from x1,y1 (top left) to x1,y1 (bottom right) and the touch area ends at 3-4000pt while the touchscreen raw coordinates range between 2 and 62k.
For everything to work, I need exact match:
bDeviceClass: 0x00 (not 0x03 HID)
bInterfaceClass: 0xFF (Vendor Specific)
and all the rest that's in the mitm dump.
The dump was captured using raw-gadget and usb-proxy. It confirms that raw-gadget can put the OTG port in mode compatible of communicating with the host, the right way. usb-proxy (GitHub AristoChen/usb-proxy) does not support capture/replay mode, so I can't confirm if it'd be a valid way to solve the task.
Please contact me for clarifications before making your offer, questions like "what's your budget" will be blocked!
Requirements include:
- Interfacing with vendor-specific touch screen hardware
Ideal Skills and Experience:
- Experience with Raspberry Pi
- Proficiency in touchscreen interface development
- Knowledge of industrial machine control systems
- Familiarity with radio communication protocols
Please provide relevant experience in your bids.
Hey All, this is the 4th time I'm reposting this project. Please don't bid without reading the requirements and checking the attached mitm dump!
Project brief:
I need the raspberry pi to act as touch screen emulator, matching the hardware of the dump (attached).
And to be able to accept coordinates for x,y click.
Project details:
I've been trying to crack this for 10 days now, with multiple freelancers and the help of multiple AI tools.
Here is the main issue - if the raspberry pi acts as HID device, the host machine expects calibrated values (after touch screen calibration). While in normal case, hardware controller connected to the host, after calibration the touch screen controller keep sending raw x,y coordinates and the host does the calibration on its own. HID device works, but since the screen is in portrait mode, using only the bottom 1/3 of it for touch area, the coordinates shift from x1,y1 (top left) to x1,y1 (bottom right) and the touch area ends at 3-4000pt while the touchscreen raw coordinates range between 2 and 62k.
For everything to work, I need exact match:
bDeviceClass: 0x00 (not 0x03 HID)
bInterfaceClass: 0xFF (Vendor Specific)
and all the rest that's in the mitm dump.
The dump was captured using raw-gadget and usb-proxy. It confirms that raw-gadget can put the OTG port in mode compatible of communicating with the host, the right way. usb-proxy (GitHub AristoChen/usb-proxy) does not support capture/replay mode, so I can't confirm if it'd be a valid way to solve the task.
Please contact me for clarifications before making your offer, questions like "what's your budget" will be blocked!