×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

DIYMall and GPUSB Skipping

  • Posts: 389
  • Thank you received: 15
Hello,

DMESG shows the DIYMall USB GPS GLO/NOSS device as attached to Serial 0. Lssub enumerates this device as an attached USB device. I have specific rule for this device called out.

The driver GBUSB looks at the device and says SKIPPING. What must this device need in rules or Astroberry config to be recognized by GPUSB?

I have a similar discussion in EKOS. But this is centers on AstroBerry and RPI 3B+.
4 years 8 months ago #41372

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

This link is to the device. The details on how to talk with the device are provided.

www.diymalls.com/VK172-Gmouse-GPS-Module

The site says the device is RPI ready. It does work and is USB 2.0 only. A software package is described on this site.
4 years 8 months ago #41426

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

What steps are necessary for RS232 devices?

I have an AstroEQ device. It is an RS232 device. I did not have any issue setting the AstroEQ up.

AstroBerry sees the UBlox device and assigns the appropriate port. GPUSB enumerates the Vender ID. The log says skipping the Ublox.

For the AstroEQ, AstroBerry sets up a RS232 communication. With Ublox, I am not finding RS232 communication artifacts.

This might be Bluetooth RS232 vs all other RS232. I am going to see if rules to push the dance of the RS232 devices.

Any research on RPI and number of devices possible is fruitless. The available ttyACM* is just 00 and 01. I am going to test values in Rules.
4 years 8 months ago #41456

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

I have more information to share with this site. I used Log Viewer to get this information. I think I see why this is being skipped.

Jul 28 20:31:39 astroberry kernel: [ 5638.530880] usb 1-1.2: new full-speed USB device number 6 using dwc_otg
Jul 28 20:31:39 astroberry kernel: [ 5638.663322] usb 1-1.2: New USB device found, idVendor=1546, idProduct=01a7
Jul 28 20:31:39 astroberry kernel: [ 5638.663338] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 28 20:31:39 astroberry kernel: [ 5638.663347] usb 1-1.2: Product: u-blox 7 - GPS/GNSS Receiver
Jul 28 20:31:39 astroberry kernel: [ 5638.663356] usb 1-1.2: Manufacturer: u-blox AG - www.u-blox.com
Jul 28 20:31:39 astroberry kernel: [ 5638.664469] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
Jul 28 20:31:39 astroberry mtp-probe: checking bus 1, device 6: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2"
Jul 28 20:31:39 astroberry mtp-probe: bus: 1, device: 6 was not an MTP device
Jul 28 20:31:39 astroberry upowerd[1390]: unhandled action 'bind' on /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.1
Jul 28 20:31:39 astroberry upowerd[1390]: unhandled action 'bind' on /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.0
Jul 28 20:31:39 astroberry systemd[1]: Starting Manage ttyACM0 for GPS daemon...
Jul 28 20:31:39 astroberry upowerd[1390]: unhandled action 'bind' on /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2
Jul 28 20:31:39 astroberry systemd[1]: Started Manage ttyACM0 for GPS daemon.
Jul 28 20:31:50 astroberry ModemManager[599]: <info> [device /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2] creating modem with plugin 'u-blox' and '1' ports
Jul 28 20:31:50 astroberry ModemManager[599]: <warn> Could not grab port (tty/ttyACM0): 'Cannot add port 'tty/ttyACM0', unhandled serial type'
Jul 28 20:31:50 astroberry ModemManager[599]: <warn> Couldn't create modem for device '/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2': Failed to find primary AT port
4 years 7 months ago #41476

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

It appears that I am at a standstill with the RPI 3B+ and AstroBerry. Neither will accept this GPS device contrary to the vendor and a well written HOW-TO.

The following is the syslog after a reboot about GPSD. The GPSD rule was edited to include the Vendor DIYMall and its device. In fact, the rule for GPSD is very simple. Adding a rule in /lib/udev/rules.d does not change anything. INDI_GPSD does not see GPSD rules. GPUSB does not look at GPSD rules.

This is the output using KSTARS device manager. **** is the device enumerated but ignored.

2019-07-30T17:27:32: listening to port 7625 on fd 3
FIFO: start indi_gpusb -n "GPUSB"
With name: GPUSB
FIFO: Starting driver indi_gpusb
2019-07-30T17:27:32: Driver indi_gpusb: pid=2636 rfd=4 wfd=7 efd=8
2019-07-30T17:27:32: Client 5: new arrival from 127.0.0.1:59498 - welcome!
2019-07-30T17:27:37: Driver indi_gpusb: Skipping device 04d8/000a
*****2019-07-30T17:27:37: Driver indi_gpusb: Skipping device 1546/01a7******
2019-07-30T17:27:37: Driver indi_gpusb: Skipping device 1618/0941
2019-07-30T17:27:37: Driver indi_gpusb: Skipping device 125f/db8a
2019-07-30T17:27:37: Driver indi_gpusb: Skipping device 1a40/0101
2019-07-30T17:27:37: Driver indi_gpusb: Skipping device 045e/001d
2019-07-30T17:27:37: Driver indi_gpusb: Skipping device 0451/1446
2019-07-30T17:27:37: Driver indi_gpusb: Skipping device 04f2/0939
2019-07-30T17:27:37: Driver indi_gpusb: Skipping device 1a40/0101
2019-07-30T17:27:37: Driver indi_gpusb: Skipping device 0424/7800
2019-07-30T17:27:37: Driver indi_gpusb: Skipping device 0424/2514
2019-07-30T17:27:37: Driver indi_gpusb: Skipping device 0424/2514
2019-07-30T17:27:37: Driver indi_gpusb: Skipping device 1d6b/0002
2019-07-30T17:27:37: Driver indi_gpusb: Error: No GPUSB device found

Editing GPSD and pushing it to look at the assigned port by SETSERIAL shows that GPSD is not looking at the rules.

Jul 30 13:06:31 astroberry systemd[1]: Created slice system-gpsdctl.slice.
Jul 30 13:06:31 astroberry gpsd[711]: gpsd:ERROR: SER: /dev/ttyAMA0 already opened by another process
Jul 30 13:06:31 astroberry gpsd[711]: gpsd:ERROR: initial GPS device /dev/ttyAMA0 open failed
Jul 30 13:11:25 astroberry gpsd[711]: gpsd:ERROR: SER: device open of /dev/ttyAMA0 failed: Device or resource busy - retrying read-only
Jul 30 13:11:25 astroberry gpsd[711]: gpsd:ERROR: SER: read-only device open of /dev/ttyAMA0 failed: Device or resource busy
Jul 30 13:11:25 astroberry gpsd[711]: gpsd:ERROR: /dev/ttyAMA0: device activation failed.
Jul 30 13:11:25 astroberry gpsd[711]: gpsd:ERROR: /dev/ttyAMA0: activation failed, freeing device

ModemManager is worthless in this dance. I removed it. Old posts are the results of web searches for errors. They show the same errors that I was getting. The applet cannot create a modem out of a GPS nor a Tom Carpenter AstroEQ. It just can't. Despite setting up rules to IGNORE or NOT PROBE, ModemManager errors out anyway. Less noise in the logs.

LSUSB and dmesg | grep tty show that everything is connected and working.
astroberry@astroberry:~$ dmesg | grep tty
[ 0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1600 bcm2708_fb.fbheight=900 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[ 0.000143] console [tty1] enabled
[ 0.567066] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[ 7.491594] cdc_acm 1-1.3.4.3:1.0: ttyACM0: USB ACM device # DIYMall USB device
[ 7.492742] cdc_acm 1-1.3.4.4:1.0: ttyACM1: USB ACM device # AstroEQ USB device

Why nothing in KSTARS sees this configuration is baffling me. In EQMount, I can set the tty device. In INDI_GPSD and INDI_GPUSB, I cannot set up the tty. With the AstroBerry GPSD not working, I am unable to confirm that INDI_GPSD is not seeing the GPSD. Neither INDI devices have logging.

ALL evidence shows the USB and RPI are enumerating devices correctly. AstroBerry, INDI, and KSTARS are not seeing the setup. What is missing?
Last edit: 4 years 7 months ago by John Robison.
4 years 7 months ago #41547

Please Log in or Create an account to join the conversation.

  • Posts: 298
  • Thank you received: 46

Replied by Markku on topic DIYMall and GPUSB Skipping

Hi,

Let's see if we get any closer to a solution and rule out a basic problem, I don't have a GPS device or astroberry but I hope this will help a bit.

If you have the GPS connected and run command : ls -l /dev/ttyAMA0
What output do you get ?? you should get something like : crw-rw-rw- 1 root dialout 188, 0 jul 30 21:33 /dev/ttyAMA0

Then run command : groups
What do you get ?? you should get something like : maxer adm dialout cdrom sudo dip plugdev lpadmin sambashare

Make sure that the groupname, in this case "dialout" matches the output of both commands.

Let's see what results you get.

Cs,
/Markku
4 years 7 months ago #41548

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello Markku,

Thank you for your reply and welcome to my world. Well, I reviewed my "evidence" on GPSD and found the issue. I now have GPSD linked to INDI_GPSD. KSTARS now is aware that it is no longer in Poland. LOL.

How I became aware of the problem was when I was attempting Polar Alignment via EKOS. It would not resolve because its starting point is in Poland. I am not by any KSTARS known site. I do have my GPS site listed in the KSTARS DB. At that night, I was in Poland according to KSTARS.

Now for another clear night. I am looking for the opportunity to Polar Align with EKOS.
4 years 7 months ago #41550

Please Log in or Create an account to join the conversation.

  • Posts: 298
  • Thank you received: 46

Replied by Markku on topic DIYMall and GPUSB Skipping

Great that you have resolved the problem :)

Have a great evening!!
/Markku
4 years 7 months ago #41551

Please Log in or Create an account to join the conversation.

  • Posts: 983
  • Thank you received: 375
You don't need GPS to set your location. The primary functionality to handle it is located in KStars/Settings/Geographic.
However if you want to use your GPS you need to remember to set it up correctly in KStars/Settings/Configure KStars/INDI - look at Time and Location section and select GPS updates KStars.
BTW. these has nothing to do with Astroberry per se, it's very normal and that's how KStars/Ekos work.
Clear skies!
4 years 7 months ago #42496

Please Log in or Create an account to join the conversation.

Moderators: Radek Kaczorek
Time to create page: 0.904 seconds