Lephenixnoir
/
CalcDB
1
0
Fork 2
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity

Suggestions on protocols and transfer softwares #3

New Issue
Open
opened 2024-03-10 15:34:38 +01:00 by cake · 0 comments
cake commented 2024-03-10 15:34:38 +01:00
Copy Link

This issue regroups some issues I find with the protocols / transfer software part of the calculator definitions:

Add the following missing protocols:

  • Legacy protocol with fx-7700G header format (what I historically named CAS40 because 1 ':' packet type, 38 header bytes, and 1 checksum byte), e.g. legacy_7700
  • Legacy protocol with fx-9850G header format (what I historically named CAS50 because 1 ':' packet type, then 49 bytes), e.g. legacy_9850
  • Legacy protocol with AFX header format (what I historically named CAS100, because for the Graph 100 (well, originally, I thought "CAS50 at 2 times the speed", but fuck, headers are actually 40 bytes long)), e.g. legacy_afx
  • Protocol 7.00 screenstreaming, e.g. p7_ohp, which I've ended up distinguishing from Protocol 7.00 because different flows and packet format entirely, see https://cahuteproject.org/topics/protocols/seven-ohp.html

There may actually be another distinction on the legacy protocol for interactive only (usage of Send( and Receive( from the calc), but I'm not entirely sure for that yet.

Implementations of Protocol 7.00 over serial connections on the fx-9860G actually also handles legacy protocol with fx-9850G header format AFAIK. Should that be represented as a completely separate protocol, e.g. p7_with_legacy_9850_compat?

Should p7/p7_ohp over UMS (i.e. SCSI commands) be represented as separate protocols, i.e. p7_ums and p7_ohp_ums? For details, see https://cahuteproject.org/topics/protocols/ums.html

Also note that for the same reason, maybe p7_bulk and p7_ohp_bulk should be distinguished as well, because transfer software may implement only p7 and p7_ohp over serial and not support p7 over USB bulk.

As for transfer software:

  • FA-124 supports p7, legacy_9850 (with model selection in the UI), and I'm not sure about p7 with fallback to 9850. Not sure about p7_ohp.
  • Screen Receiver (by CASIO) supports p7_ohp and p7_ohp_ums AFAIK. The XP version may only support p7_ohp though, so it should probably be distinguished.
  • p7 supports p7 (I know, revolutionary), without 9850 compat.
  • p7screen supports p7_ohp and p7_ohp_ums
  • CaS supports legacy_9700 and legacy_9850
  • xfer9880 supports p7. You can either link https://cahuteproject.org/cli/xfer9860.html (Cahute reimplem) or https://sourceforge.net/projects/xfer9860/ (original project page).
  • Flash100 (community util for the AFX) supports legacy_afx.
This issue regroups some issues I find with the protocols / transfer software part of the calculator definitions: - Have transfer software computed from the protocols implemented by the calculator. - Add more transfer software based on historical data - For p7 transfer software, change the link to: https://cahuteproject.org/cli/p7.html - For p7screen, change the link to: https://cahuteproject.org/cli/p7screen.html - For Protocol 7.00, add a link to: https://cahuteproject.org/topics/protocols/seven.html - Maybe find a way to distinguish between protocols used on USB and serial, especially for the fx-CG which actually still uses Protocol 7.00 on serial links (yup) Add the following missing protocols: - Legacy protocol with fx-7700G header format (what I historically named CAS40 because 1 ':' packet type, 38 header bytes, and 1 checksum byte), e.g. `legacy_7700` - Legacy protocol with fx-9850G header format (what I historically named CAS50 because 1 ':' packet type, then 49 bytes), e.g. `legacy_9850` - Legacy protocol with AFX header format (what I historically named CAS100, because for the Graph 100 (well, originally, I thought "CAS50 at 2 times the speed", but fuck, headers are actually 40 bytes long)), e.g. `legacy_afx` - Protocol 7.00 screenstreaming, e.g. `p7_ohp`, which I've ended up distinguishing from Protocol 7.00 because different flows and packet format entirely, see https://cahuteproject.org/topics/protocols/seven-ohp.html There may actually be another distinction on the legacy protocol for interactive only (usage of `Send(` and `Receive(` from the calc), but I'm not entirely sure for that yet. Implementations of Protocol 7.00 over serial connections on the fx-9860G actually also handles legacy protocol with fx-9850G header format AFAIK. Should that be represented as a completely separate protocol, e.g. `p7_with_legacy_9850_compat`? Should p7/p7_ohp over UMS (i.e. SCSI commands) be represented as separate protocols, i.e. p7_ums and p7_ohp_ums? For details, see https://cahuteproject.org/topics/protocols/ums.html Also note that for the same reason, maybe p7_bulk and p7_ohp_bulk should be distinguished as well, because transfer software may implement only p7 and p7_ohp over serial and not support p7 over USB bulk. As for transfer software: - FA-124 supports p7, legacy_9850 (with model selection in the UI), and I'm not sure about p7 with fallback to 9850. Not sure about p7_ohp. - Screen Receiver (by CASIO) supports p7_ohp and p7_ohp_ums AFAIK. The XP version may only support p7_ohp though, so it should probably be distinguished. - p7 supports p7 (I know, revolutionary), *without* 9850 compat. - p7screen supports p7_ohp and p7_ohp_ums - CaS supports legacy_9700 and legacy_9850 - xfer9880 supports p7. You can either link https://cahuteproject.org/cli/xfer9860.html (Cahute reimplem) or https://sourceforge.net/projects/xfer9860/ (original project page). - Flash100 (community util for the AFX) supports legacy_afx.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Lephenixnoir/CalcDB#3
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?