NextSync Release Thread

[sol_hsa]

NextSync 0.6 released

Download here: http://iki.fi/sol/zip/nextsync06.zip

More robust protocol
- Better checksums
- Packet sizes encoded in packets
- Retry only retries the latest packet, not the whole file

More robust sync app
- Flushing uart before commands
- Packet size-field based receiving instead of relying on timeouts
- Tighter data receive loop written in assembler
- Also included: syncslow, which uses default uart speed.

More robust documentation
- Including description of the protocol

Here's hoping it works better, considering I can't reproduce the issues people are seeing.

https://www.youtube.com/watch?v=QlRITRnsBfo - video of it in action

[garrylancaster]

Only done a brief test so far, but seems to work well - all files expected were transferred without requiring any retries, and with no corruption.

The only issue I've noticed is that the server terminates as soon as the first sync is complete, with the following error:

Code: Select all

2020-05-20 18:33:57 | Nothing (more) to sync
2020-05-20 18:33:57 | Packet sent: 9 bytes, payload: 5 bytes, checksums: 0, 0
2020-05-20 18:33:57 | Disconnected

2020-05-20 18:33:57 | NextSync listening to port 2048
Traceback (most recent call last):
  File "./nextsync.py", line 96, in <module>
    s.bind(("", PORT))
OSError: [Errno 98] Address already in use

I assume this means there is something like a missing unbind somewhere.

[sol_hsa]

Thanks for the report. Fix is in this version:
https://raw.githubusercontent.com/jarik ... extsync.py

[garrylancaster]

Thanks, I can confirm that fixes it for me.

I have to say this is an awesome little tool. I can now just put it in my autoexec.bas and have it update my card with my latest NextZXOS build just by pressing reset.

[sol_hsa]

NextSync 0.7 released

Download here: http://iki.fi/sol/zip/nextsync07.zip

- Server: close sockets on *nixes (including macos)
- Server: transfer speed estimate after sync is done
- Server: more warnings at startup
- Server: drive letter support via commandline options
- Client: create paths if they don't exist
- Client: speed optimizations (both visual and transfer rate)
- Client: verify and retry filenames too
- Client: guard against buffer overruns on receive
- Client: tweaked timeouts
- Client: show author url
- Client: added more comments in the source code
- Docs: more clarifications, details

This version pretty much exhausts my todo list for now, so unless something happens, this will be the last version for now.

[NML32]

Thank you, NextSync 0.7 is working great.

[sol_hsa]

Thank you, NextSync 0.7 is working great.

Glad to hear.

[chris]

This is amazing, thanks!

[Luzie]

NextSync 0.7 released

Thank you! I like it very much!

Just two things I discovered:

1) If the folder /sys/config doesn´t exist .sync seems to write config-file and prints
Setting server to:
192.168.1.58
-> C:/sys/config/nextsync.cfg
Failed to open file

-> I´ve created /sys/config folder manually and than this error "Failed to open file" was gone.

Update: See at FB, that this error was reported 2 days ago and you respond on it there:

Jari Komppa: Weird. Nextsync should be able to create the directory, but I guess it doesn't work always then.

2) Maybe a check if SpecNexts Network Interface "is configured and up" can be done. Because I run nextsync by accident on a Next without WIFI builtin (or WIFI not configured yet) and wondered why I couldn´t reach the sync-server

[sol_hsa]

1) If the folder /sys/config doesn´t exist .sync seems to write config-file and prints
Setting server to:
192.168.1.58
-> C:/sys/config/nextsync.cfg
Failed to open file

-> I´ve created /sys/config folder manually and than this error "Failed to open file" was gone.

Update: See at FB, that this error was reported 2 days ago and you respond on it there:

Jari Komppa: Weird. Nextsync should be able to create the directory, but I guess it doesn't work always then.

Ah right, that's one thing I did not re-check. Well, I've mentioned it in the docs, and the workaround is pretty simple (even if it's awkward)

2) Maybe a check if SpecNexts Network Interface "is configured and up" can be done. Because I run nextsync by accident on a Next without WIFI builtin (or WIFI not configured yet) and wondered why I couldn´t reach the sync-server

I don't actually know how to do that. But, it mentions that it can't talk to esp, and docs have troubleshooting section which asks if you have the wifi module at all..