digitaltrails
commented
2 months ago I doubt wayland has anything to do with it. It should not affect communicating with ttys. Although I suppose different default permissions might be applied. Anyway, you could always try switching back to X11.
I would first suspect the arduino. Isolate the Arduino from vdu_controls. Stop vdu_controls using the arduino by switching to manual ambient light input, or by shutting down vdu_controls completely. Then use cat to see what the arduino is producing, here is a healthy example:
% cat /dev/arduino
8.33
8.33
9.17
10.00
12.50
13.33
14.17
14.17
14.17Control-C the cat to get out of it.
Rarely, every few months, the arduino doesn't initialise properly on a system boot. The output from cat might contain garbage such as:
[BH1750] Device is not configured!
-2.00
[BH1750] Device is no%To fix this I have to switch vdu_controls into manual (or exit). Then I unplug the USB connection to cut the arduino's power. Then reconnect the USB and it should be OK. On my system it seems OK to do this while the system is up, but if cautious, a shutdown/power-off would do the same thing.
If the arduino is still the problem, could it be a loose wire or dry-joint. As illustrated, I use plugable pins on a breadboard, so I would replug each wire to make sure the connections are good.
Reloading the arduino's software using the arduino IDE might fix corrupted software. In my experience, that's never been necessary.
Milor123
Dear brother
I am writing to inform you that my VDU has stopped functioning properly, failing to read data from the Arduino sensor. Although I'm not sure when this issue began, it occasionally occurred previously, where the program would become stuck on 0 and restarting it would resolve the problem.
However, this issue persists and I have made no changes to the Arduino itself. The only notable modification I have made recently was switching from X11 to Wayland as my display server.
Could this be related to the transition to Wayland?
In an effort to troubleshoot the issue, I updated VDU today, deleted my personalized configuration files for the software, and also checked the Arduino console to verify if perhaps the device had malfunctioned. Additionally, I attempted changing ports, but all signs point to a peculiar error on the VDU side.
I have endeavored to revisit the steps outlined in your tutorial, including switching from using a symbolic link to the actual port. Despite my efforts, I am still unsure of the root cause of this issue and would greatly appreciate any guidance you can offer.
Please let me know if there is anything else I can provide or if you require further information to assist me in resolving this problem.
Best regards
This is the log
Please help me!! Thank u very much