RigPi2 + G-800DXA + ERC-Mini #rigpi2 #rotor #ercmini


Fernando .
 

My current set up is:
IC-7300: PORT USB0
Rotor: G-800DXA
Interface: ERC-MINI PORT USB0

Goal: Try to make the rotor work using RigPi.

Any rotor combination settings I use, the radio simply does not connect. All tests were done in the Settings Advance tab.

I tried:
Rotor: Yaesu, Models GS-232A, GS-232B, Baud Rate: 9600, 4800.
Rotor: Hy-Gain Model: DCU-1 Baud Rate: 9600, 4800.

When I execute the rotctl and manually run a command it gives: "move: error = Feature not available"

Any advice? 

logs:
pi@rigpi2:~ $ sudo rotctl -m 403 -r /dev/ttyUSB1 -vvvvv
rotctl Hamlib 4.1~git
Last commit was from indeterminate source revision.
Report bugs to <hamlib-developer@...>
 
rot_init called
initrots4_rotorez called
rot_register (401)
rot_register (402)
rot_register (403)
rot_register (404)
rot_register (405)
rotorez_rot_init called
set_conf: called
rot_open called
serial_open called
serial_setup called
serial_setup: tcgetattr
serial_setup: cfmakeraw
serial_setup: cfsetispeed=4800,0x000c
serial_setup: cfsetospeed=4800,0x000c
serial_setup: data_bits=8
serial_setup: parity=0
serial_setup: tcsetattr TCSANOW
serial_flush called
serial_flush: tcflush
Opened rot model 403, 'DCU-1/DCU-1X'
Backend version: 20100823.0, Status: Stable
 
 
otator command: M
rotctl_parse: input_line: M
Direction: 2
Speed: 1
rot_move called
move: error = Feature not available
 
---
pi@rigpi2:~ $ more /var/log/rigpi-rotor.log
2021-05-13 18:08:53 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:08:53 rotor: 0 connection attempt
rotor port: /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_D3078UZC-if00-port0
rotor ID: 601
rotor Name: GS-232A
rotor Baud: -s 9600
rotor Stop: 1
 
pi@rigpi2:~ $ tail -f /var/log/rigpi-rotor.log
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:08:53 rotor: 0 connection attempt
rotor port: /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_D3078UZC-if00-port0
rotor ID: 601
rotor Name: GS-232A
rotor Baud: -s 9600
rotor Stop: 1
 
tail: /var/log/rigpi-rotor.log: file truncated
2021-05-13 18:10:52 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:10:52 rotor: 0 connection attempt
rotor port: /dev/ttyUSB1
rotor ID: 601
rotor Name: GS-232A
rotor Baud: -s 4800
rotor Stop: 1
 
tail: /var/log/rigpi-rotor.log: file truncated
2021-05-13 18:12:17 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:12:17 rotor: 0 connection attempt
rotor port: /dev/ttyUSB1
rotor ID: 603
rotor Name: GS-232B
rotor Baud: -s 4800
rotor Stop: 1
 
tail: /var/log/rigpi-rotor.log: file truncated
2021-05-13 18:13:25 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:13:25 rotor: 0 connection attempt
rotor port: /dev/ttyUSB1
rotor ID: 403
rotor Name: DCU-1/DCU-1X
rotor Baud: -s 9600
rotor Stop: 1
 
tail: /var/log/rigpi-rotor.log: file truncated
2021-05-13 18:14:09 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:14:09 rotor: 0 connection attempt
rotor port: /dev/ttyUSB1
rotor ID: 403
rotor Name: DCU-1/DCU-1X
rotor Baud: -s 4800
rotor Stop: 1
 
tail: /var/log/rigpi-rotor.log: file truncated
2021-05-13 18:14:51 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:14:51 rotor: 0 connection attempt
rotor port: /dev/ttyUSB1
rotor ID: 403
rotor Name: DCU-1/DCU-1X
rotor Baud: -s 19200
rotor Stop: 1
 
tail: /var/log/rigpi-rotor.log: file truncated
2021-05-13 18:26:07 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:26:07 rotor: 0 connection attempt
rotor port: /dev/ttyUSB1
rotor ID: 603
rotor Name: GS-232B
rotor Baud: -s 9600
rotor Stop: 1
 
tail: /var/log/rigpi-rotor.log: file truncated
2021-05-13 18:27:15 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:27:15 rotor: 0 connection attempt
rotor port: /dev/ttyUSB1
rotor ID: 601
rotor Name: GS-232A
rotor Baud: -s 9600
rotor Stop: 1
 







 


Glenn VE9GJ
 

Hi Fernando

When you try rotctl manually did you try the "p" command?  For my RotorEz controller I need to use p to get pos and P 180 0 to set a pos.

73

Glenn VE9GJ


On 2021-05-13 22:38, Fernando . wrote:

My current set up is:
IC-7300: PORT USB0
Rotor: G-800DXA
Interface: ERC-MINI PORT USB0

Goal: Try to make the rotor work using RigPi.

Any rotor combination settings I use, the radio simply does not connect. All tests were done in the Settings Advance tab.

I tried:
Rotor: Yaesu, Models GS-232A, GS-232B, Baud Rate: 9600, 4800.
Rotor: Hy-Gain Model: DCU-1 Baud Rate: 9600, 4800.

When I execute the rotctl and manually run a command it gives: "move: error = Feature not available"

Any advice? 

logs:
pi@rigpi2:~ $ sudo rotctl -m 403 -r /dev/ttyUSB1 -vvvvv
rotctl Hamlib 4.1~git
Last commit was from indeterminate source revision.
Report bugs to <hamlib-developer@...>
 
rot_init called
initrots4_rotorez called
rot_register (401)
rot_register (402)
rot_register (403)
rot_register (404)
rot_register (405)
rotorez_rot_init called
set_conf: called
rot_open called
serial_open called
serial_setup called
serial_setup: tcgetattr
serial_setup: cfmakeraw
serial_setup: cfsetispeed=4800,0x000c
serial_setup: cfsetospeed=4800,0x000c
serial_setup: data_bits=8
serial_setup: parity=0
serial_setup: tcsetattr TCSANOW
serial_flush called
serial_flush: tcflush
Opened rot model 403, 'DCU-1/DCU-1X'
Backend version: 20100823.0, Status: Stable
 
 
otator command: M
rotctl_parse: input_line: M
Direction: 2
Speed: 1
rot_move called
move: error = Feature not available
 
---
pi@rigpi2:~ $ more /var/log/rigpi-rotor.log
2021-05-13 18:08:53 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:08:53 rotor: 0 connection attempt
rotor port: /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_D3078UZC-if00-port0
rotor ID: 601
rotor Name: GS-232A
rotor Baud: -s 9600
rotor Stop: 1
 
pi@rigpi2:~ $ tail -f /var/log/rigpi-rotor.log
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:08:53 rotor: 0 connection attempt
rotor port: /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_D3078UZC-if00-port0
rotor ID: 601
rotor Name: GS-232A
rotor Baud: -s 9600
rotor Stop: 1
 
tail: /var/log/rigpi-rotor.log: file truncated
2021-05-13 18:10:52 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:10:52 rotor: 0 connection attempt
rotor port: /dev/ttyUSB1
rotor ID: 601
rotor Name: GS-232A
rotor Baud: -s 4800
rotor Stop: 1
 
tail: /var/log/rigpi-rotor.log: file truncated
2021-05-13 18:12:17 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:12:17 rotor: 0 connection attempt
rotor port: /dev/ttyUSB1
rotor ID: 603
rotor Name: GS-232B
rotor Baud: -s 4800
rotor Stop: 1
 
tail: /var/log/rigpi-rotor.log: file truncated
2021-05-13 18:13:25 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:13:25 rotor: 0 connection attempt
rotor port: /dev/ttyUSB1
rotor ID: 403
rotor Name: DCU-1/DCU-1X
rotor Baud: -s 9600
rotor Stop: 1
 
tail: /var/log/rigpi-rotor.log: file truncated
2021-05-13 18:14:09 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:14:09 rotor: 0 connection attempt
rotor port: /dev/ttyUSB1
rotor ID: 403
rotor Name: DCU-1/DCU-1X
rotor Baud: -s 4800
rotor Stop: 1
 
tail: /var/log/rigpi-rotor.log: file truncated
2021-05-13 18:14:51 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:14:51 rotor: 0 connection attempt
rotor port: /dev/ttyUSB1
rotor ID: 403
rotor Name: DCU-1/DCU-1X
rotor Baud: -s 19200
rotor Stop: 1
 
tail: /var/log/rigpi-rotor.log: file truncated
2021-05-13 18:26:07 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:26:07 rotor: 0 connection attempt
rotor port: /dev/ttyUSB1
rotor ID: 603
rotor Name: GS-232B
rotor Baud: -s 9600
rotor Stop: 1
 
tail: /var/log/rigpi-rotor.log: file truncated
2021-05-13 18:27:15 
 
RIGPI ROTOR DIAGNOSTIC LOG
 
2021-05-13 18:27:15 rotor: 0 connection attempt
rotor port: /dev/ttyUSB1
rotor ID: 601
rotor Name: GS-232A
rotor Baud: -s 9600
rotor Stop: 1
 







 



Loic SM5VFE
 

Hi Fernando

Yaesu G1000 rotor works very well with RigPi. Baudrate is 9600. Does RigPi find the rotor USB port? Regards from Loic SM5VFE


Fernando .
 

yes. The RigPi2 finds the USB port correctly. I've tried using Baud rate at 9600. are you using the ERCMini? which rotor and model are you using?


Loic SM5VFE
 

Hi Fernando
I use G1000 rotor  and CG RTC 200 serial to usb box. Radio and rotor must have different ports.
I use RS232B 9600 baud

Regards from Loic SM5VFE