Created attachment 139686 [details] debug log Hi, I noticed that the most recent commit to the ublox plugin (3e469e7b8055a0a11abc8304ec44c3df39e74d3d, "u-blox: don't run quick AT procedure if READY_DELAY not configured") has broken my ublox L200. If I revert this commit and plugin the device, it registers correctly. But with this commit, I instead get the attached log (from running with the --debug option) and ModemManager gives up without setting up the device. Notably, this occurs only if you do the following: - Start ModemManager without the device plugged in - Then plugin the device If instead, you plugin the device and *then* start ModemManager, then everything works OK. This is on Debian Stretch.
Update: This actually isn't caused by that commit; sorry for the confusion. Looks like this is an issue both with and without the commit.
What's the PID of the device? Can you edit "/lib/udev/rules.d/77-mm-ublox-port-types.rules" and add the following line: ATTRS{idVendor}=="1546", ATTRS{idProduct}=="<PID>", ENV{ID_MM_UBLOX_PORT_READY_DELAY}="20" And then: $ sudo udevadm control --reload $ sudo udevadm trigger And recheck.
Yep, I'll check this when I'm back in front of the hardware tomorrow.
Your suggestion was correct; it was just missing a rules entry for the L2. martin@columbia:~/ModemManager$ lsusb | grep U-Blox Bus 003 Device 092: ID 1546:1146 U-Blox AG Adding this line to the rules file fixes it: ATTRS{idVendor}=="1546", ATTRS{idProduct}=="1146", ENV{ID_MM_UBLOX_PORT_READY_DELAY}="20"
Note that depending on its networking configuration, the L2 can register as several different USB IDs: 1141, 1143, and 1146: https://www.u-blox.com/sites/default/files/TOBY-L2-MPCI-L2_SysIntegrManual_%28UBX-13004618%29.pdf (page 43)
Hey, before we add those udev rules... could you gather debug logs for me from ModemManager when trying to reproduce the problem and the udev rules are added? See https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/ Need to understand whether just a timeout is needed, or if the modem really sends the +READY URC
Created attachment 139837 [details] debug log
Hey, thanks for the debug log. So the TOBY-L200 doesn't send any +READY URC, but it still needs at least 9s (per your log) to show the AT capable parser. Let's go on and apply the udev tag in the same way, even if no +READY URC is sent, it will just be as if we wait 20s before going on.
Fixed in git master, will be included in MM 1.8
Thanks! 20 seconds also agrees with the suggestion in the datasheet for how long to wait, so that's likely a good value to pick. Small note: this behavior (and the USB ID) is the same on both the Toby L200 and L201 (I tested them both), so your comment in the udev rules should probably include both of them, just to prevent confusion.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.