How can I "force" the driver station to use a custom IP. And where is the IP?
Alex Spataru
@alex-spataru
Hello
On the bottom right corner of the main window, there is a button that allows you to open the settings window, in which there is the option to set a custom robot address
You can obtain the robot IP by pinging it on terminal or opening the WebDashboard in your browser
Rishab Swift
@RishabSwift
I found the IP address in the WebDashboard, and I entered it here: http://imgur.com/a/NkqCX Still having no communiation
Rishab Swift
@RishabSwift
Please help me. Do you know what may be causing this? On windows it's working perfectly fine. Thanks a lot!
Alex Spataru
@alex-spataru
It may sound strange, but click the close button to apply the settings
Rishab Swift
@RishabSwift
Sorry I have done that. I just opened it again to take a screenshot.
Alex Spataru
@alex-spataru
Alright, can you ensure that no one else is connected to the robot?
The robot only connects to one DS at a time
Oh, you inputted the IP on the radio field
In
Rishab Swift
@RishabSwift
Hello, I can confirm that no one else is connected to the robot.
I can connect in SmartDashboard perfectly fine
Alex Spataru
@alex-spataru
Try to input the IP on the robot field, not on the custom radio field
Rishab Swift
@RishabSwift
WOW THANKS! But the same issue is happening. It is disconnecting every second...
It's connected now but disconnecting every few seconds or so
Thanks! I'll check the video a little later, since I'm using my mobile data
Rishab Swift
@RishabSwift
That's fine. The video just shows the robot disconnecting and connecting to the driver station. However, this time though, it stays connected for way longer than it did in the previous version.
05:13.1 DEBUG Robot code status set to DS::CodeStatus(kCodeRunning) 05:13.1 DEBUG Robot communication status set to DS::CommStatus(kCommsWorking)
The kCodeRunning and stuff seems to be the most repetitive thing in the log
Alex Spataru
@alex-spataru
Yeah, it's like the QDS or the robot drops the connection as soon as the first packets arrive
I'll try to send you a build of the latest code when I have access to a Wi-Fi access point
Rishab Swift
@RishabSwift
Ok awesome man. Thanks a lot for your help. I really appreciate it.
I will be waiting! Our team is working hard in the build season!
To anyone interested I just submitted a patch upstream to Solus to update the QDriverStation in the repo to the latest version. As long as they don't find a problem with the patch it should be in the unstable repo soon. https://dev.solus-project.com/T2222
Alex Spataru
@alex-spataru
Thanks for the update!
Rishab Swift
@RishabSwift
Hey, just to let you know that it's working perfectly fine
Thanks a lot for the update!
Alex Spataru
@alex-spataru
@RishabSwift Glad that the issue was solved!
I have just released another version of the QDriverStation to fix an issue in which SDL joystick inputs where not detected. I highly recommend everyone to update as soon as possible!
Rishab Swift
@RishabSwift
Hey, @alex-spataru
The buttons begin at 0 in the Q driver station but 1 in PC driver stations
So the bottom Mapping is different for PC and Mac.. Is there a way you can fix this??
Alex Spataru
@alex-spataru
I think that it's possible to use a Mac OS utility to remap the joysticks
The QDriverStation reads the joystick mappings from SDL, while the official FRC Driver Station uses Xinput, which results in the different mappings