Hi Arado and wolfi,

First, I tried the focus an mount driver and not works. Many trys but only works on a PC (Ubuntu mate, like a local)
Arado, I'll try it this evening. Is to say: remove all the rules on rules. d directory. And create a new one but this time with the suggestions that you did it. On this new rule file I add a kernel, subsystem, (by USB or tty?) and then... What more? Similar like I posted some interventions before?
Thanks for your help.
Pep

Hello,

I am puzzled why deleting all rules is required. The next update will replace the missing, maybe. This why I create specific rules for specific hardware.

Other drivers might be necessary. Be sure to check your device list before deleting everything.

Let us know whether it was the GPS deamon

Hello

I do believe ttyUSB0 = ttyS0 which is the console terminal. This is why ttyACM is the better choice.

Hy to every body,

I tried, this weekend, a lot of test, include a script of AstroPi3 for generate a correct rules file. But continuos not work.
But this script only works for usb/ttyusb*, you suggest that could be that onstep use an other type of device? (like ttyS* or ttyAM*...)
For other hand I checked if, direct, to connect on PC (by Linux) works, and works perfectly.
Then I think that the problem cames from the raspi4 (4gb), i seems remember that raspi4 4gb are not completely stable yet, and obviously the kstart /indi doesn't works well.
Today I want to check on raspi3B and Rasoi3B+, and look what happens?
Thanks for all your support,

Pep

Hi Arado,
May I ask you send an exemple of the rules of ttyACM would have to create it? (kernel I'd use, subsystem, add, dventor,... All the thinks that you believe that is necessary)
Thanks,
Pep

hi pep!
well - ttySx is he standard UART, the old style miniDIN 9 COM1 port hardly to be found on any computer anymore (the pi still ha it via dedicated GPIO pins, but no direct connector). the ttyACMx thing - well - i don't think that this is the problem as your cp2102/9 hooks up to ttyUSB0. maybe a try with the pi3+ might shed more light on that problem ...
yours wolfi

Hello,

This is my rule for my GPS. My USB GPS always took the default ttyACM0 driver. This left out the AstroEQ. AstroEQ is a the motor driver similar to the OneStep. I use ttyACM by incremental use as allowed by the OS. I could not find a use case for ttyUSB within RPI. All other references were for i386 or AMD64 systems. Windows uses COM for its uses. The OS sets this up for RS232 ports. COM is similar to ttyACM. The RPI OS uses ttyACM for needy devices of asynchronous communications.

Hi Arado,
Then you suggest I do a rules file like:
SUBSYSTEMS=="usb", ACTION=="add", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="0001", MODE="0666", SYMLINK+="OnStep"
but change usb for ttyACM.? and left like next:
SUBSYSTEMS=="ttyACM", ACTION=="add", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="0001", MODE="0666", SYMLINK+="OnStep"ç
Is necessary to add someone other parameter on the rules file for this case (Kernel, run, ...)?
Someone knows how to change (if it's possible) the serial of the device?
Thanks,
Pep

Hi guys,

A little bit light on my live... I executed "sudo lsof /dev/ttyUSB0" (this returns all the devices or process runs on the ttyUSB0. And the answer is:

sudo lsof /dev/ttyUSB0
[sudo] contrasenya per a astroberry:
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1001/gvfs
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
gpsd 1297 gpsd 8u CHR 188,0 0t0 22412 /dev/ttyUSB0

Then I understand that I need to KILL this device. Someone should help me to do it?
Thanks a lot,
Pep

Hello Pep.

Somehow, the file that I gave is not reflected by this reply. Look carefully at these commands.

# 1546:01a7 U-BLOX AG
ATTRS{idVendor}=="1546",ATTRS{idProduct}=="01a7", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="1546",ATTRS{idProduct}=="01a7", ENV{MTP_NO_PROBE}="1"
KERNEL=="ttyACM*",SUBSYSTEM =="tty",ATTRS{idVendor}=="1546",ATTRS{idProduct}=="01a7",ATTRS{iProduct}=="u-blox 7 - GPS/GNSS Receiver",SYMLINK+="UBGPS",MODE:="0666"

The stuff following KERNEL== is "t t y A C M * ". Notice the "*" at the end of the ttyACM. The udevadm command KERNEL is required to initiate access to the kernel. I do not like extra noise in my syslog. The preceding commands are to not do MTP and MobileManager probes against this specific device. Yes. this device is a GPS device.

For RPI, use ttyACM. For x386 and AMD64 Linux (non Ubuntu Mate/Raspbian), you do use ttyUSB. I have not seen a single RPI reference to use ttyUSB.

Hi Cicera,
I see a lot of Linux passing by which I honestly don't understand much of.....
This is my experience:
I have an EQDrive system on my G11 that mimics a Skywatcher mount and so is usable with EQmod.
Worked perfectly with Windows but with Stellarmate I ran into a problem when starting EKOS:

[WARNING] Port /dev/ttyUSB0 is already used by another driver or process.
[WARNING] Communication with /dev/ttyUSB0 @ 9600 failed. Starting Auto Search...

After some talk with Jasem :
"I'm starting to suspect that something else is interfering with it. Maybe the GPS daemon? in dmesg it was shown pps0
Try to disable gpsd:
sudo systemctl stop gpsd gpsd.socket"

That was it! EQDrive now worked on Stellarmate RPi !
But the problem returned so the final solution:
Now totally disabled the gpsd deamon. Edited the /etc/default/gpsd script and made:

START_DEAMON="false"
USBAUTO="false"
and also put # in front of the rest...

Since then I use it without a glitch

Cheers, Arnold