rakusan2 / frc-nt-client Goto Github PK

This would be super helpful for when we no longer want to receive updates from a listener.

Connecting to a robot from a new project crashes with an error about 50% of the time and point's to
index.js:83 or index.js:50
let val = TypesFrom[entry.typeID](buf, off);
I am using the FRC Custom dashboard to connect.

I keep getting errors when trying to connect to a robot about 50% of the time.
The error points to the known message list, and the 0x00 keep alive message not being one of them (thus throwing this error).

{ buf: <Buffer 00> }
{ con: true,
err:
Error: Unknown Message Type - 0x00
at Client.read (C:\Users\adamj\Development\FRC-6800-2018-code\FRCDashboard\node_modules\wpilib-nt-client\index.js:335:19)
at Socket.client.on.data (C:\Users\adamj\Development\FRC-6800-2018-code\FRCDashboard\node_modules\wpilib-nt-client\index.js:253:26)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at readableAddChunk (_stream_readable.js:178:18)
at Socket.Readable.push (_stream_readable.js:136:10)
at TCP.onread (net.js:560:20) }

Hey, great work on the library! It seems that this has a lot of issues when used on bots that are 2019-2020
Is there any fix?

Hello,
I'm trying to incorporate the use of this library into one of my project and there is one thing that I don't understand - how do I connect to a specific NetworkTable?
In my team's code we use a number of different tables (ImageProcessing, Preferences Etc) and I need to connect to different tables depending on the situations.

Thank you for your time

When attempting the basic

ntClient.start((con, err) => {
    console.log({con, err});
    if (!con)
      throw err;
    }
  );

it throws

Uncaught TypeError: this.aliveTimer.unref is not a function
    at Client.write (/home/tyler/Programming/FRCDashboard/node_modules/wpilib-nt-client/index.js:452)
    at aliveTimer.setTimeout (/home/tyler/Programming/FRCDashboard/node_modules/wpilib-nt-client/index.js:451)

Meaning that for some reason, even though this.aliveTimer is always initialized via setTimeout it is not a Timeout.
Any ideas?

Would it be possible to add a callback parameter to stop which would fire once the connection stops?

In this example, the NetworkTable will only get the first assigned value and will not be able to update afterwards. I believe this has something to do with this line
but I am not exactly sure why. Help would be appreciated.

I have this little bit of code:

ipc.on('disconnect', event => {
  console.log('disconnecting...')
  client.stop()
  if(client.isConnected()) {
    client.destroy()
  }
  console.log(client.isConnected())
  event.reply('disconnected')
})

The callback is called and the log is logged, but the client still is connected or trying to connect.