DueUI Compatibility issues with RRF/DSF 3.5

gtj0

There are some issues related to RRF/DSF 3.5 that I'm currently working on. Right now, you can't run DueUI on an DSF based printer because the way DueUI detects whether you're in DSF or Standalone mode is by trying to issue an "rr_connect" command. That used to fail when the printer was in DSF mode but now succeeds and returns a JSON response so DueUI thinks it's instandalone mode when it isn't. Fix in progress.

stuartofmt

@gtj0

Hi,
I'm confused, blind, or both ... well, I'm often confused

I too, in my projects check for rr_connect to detect standalone and if that fails, I try /machine/connect to detect SBC.

I've looked at the various release notes (and googled etc) but cannot see anything about rr_connect being implemented for SBC in 3.5. Can you point me to the reference?

In any case, what about reversing the order i.e. check for /machine/connect first and then, if it fails, check for rr_connect.

... or do you have a cunning plan ?

chrishamm

@stuartofmt See here:

- Added rr_ compatibility layer to DuetWebServer (HTTP calls in standalone mode)

@gtj0 DSF adds isEmulated: true to the rr_connect JSON response, which is checked by DWC on connect. If that key/value pair is present, the connection attempt is aborted and the next connector (for DSF) tries to establish a connection using the other API.

stuartofmt

@chrishamm said in DueUI Compatibility issues with RRF/DSF 3.5:

@stuartofmt See here:
- Added rr_ compatibility layer to DuetWebServer (HTTP calls in standalone mode)
@gtj0 DSF adds isEmulated: true to the rr_connect JSON response, which is checked by DWC on connect. If that key/value pair is present, the connection attempt is aborted and the next connector (for DSF) tries to establish a connection using the other API.

So logically (with minimum code changes) - something like:

Try connecting with rr_connect
   If isEmulated: true:
       treat as invalid connection attempt
  Try connecting with /machine/connect
         get session key etc

gtj0

Yep, I got it sorted. Also had to add the call to /machine/connect to get the sessionKey and add it to all requests and to the websocket open.

stuartofmt

@gtj0

Have you release an updated version ?

gtj0

@stuartofmt said in DueUI Compatibility issues with RRF/DSF 3.5:

@gtj0

Have you release an updated version ?

Oy. I fixed it but then forgot to release it. Another victory for ADHD.

Will get it published today.

gtj0

@gtj0 said in DueUI Compatibility issues with RRF/DSF 3.5:

@stuartofmt said in DueUI Compatibility issues with RRF/DSF 3.5:

@gtj0

Have you release an updated version ?

Oy. I fixed it but then forgot to release it. Another victory for ADHD.

Will get it published today.

Done. Sorry for the delay.

stuartofmt

@gtj0
If it's any consolation ... err ... what was I going to say?