I recently got in a FCA10 and decided to start playing around with it. There's some sparse information online about these and their special manufacture JVS commands.
Anyway, straight to the point. I've modified a JVS emulator I made to dump the internal 64K that it allows you to access. Attached are dumps with dips all off and all on (sans DIP6 which causes the MCU not to power).
I would love someone with a FCA11 and the V290 FCB to get dumps. I'm also interested in dumping the supported JVS commands.
This will allow you to dump the memory: https://github.com/GXTX/YAJVSEmu/tree/dump_70
If you pipe the output with >> you'll have a space delineated map of the memory.
As for the supported commands, if you look at the commit history of that branch you'll see `d43b43de4` which will work to dump the supported commands. Since JVS is a standard we can assume correctly by the status bytes if a command is supported or not (02 being unsupported, any other meaning it's supported and we need more params).
I really would like help with this if anyone is available and willing. The wiring is very easy to set-up, you just need a simple RS485 to USB adapter and a USB cable you're willing to lose.
RE the memory dumps: I'm not really sure what's contained in here - we obviously have copies of the JVS inputs and such but that would only take a few bytes and we have nearly 30KB of /real/ used space. We can see at 0x4000 is a list of strings that the monitor would output, at 0x9000 we see the JVS information - the board name, and what it supports, at 0xFB00 we see the datecode (1998 10/26 12:00:00). Not sure the other stuff, maybe some smarter people than me can check it out.
FCA10:
Via dumping my FCA10 I found out a couple of things, one there's a internal "monitor" that you can send commands to `FCA Monitor Ver1.00 by I.Kubota@vr.namco 1998.5.20`, no clue how you would attach to this - all of the serial lines on the MCU are used for other things. Another is that each FCA is programmed with a datecode which you can dump by sending JVS command 0x70 0x02. If you send 0x70 0x03 you'll return a bitmask of the dipswitches. In case it comes up, this FCA was pulled from a 500GP for SuperSystem32.
I've programmed what is known now in my JVS emulator: https://github.com/GXTX/YAJVSEmu/commit/286f12247bc1987cfc3fbbf4bce21cc6b5ea3350
Anyway, straight to the point. I've modified a JVS emulator I made to dump the internal 64K that it allows you to access. Attached are dumps with dips all off and all on (sans DIP6 which causes the MCU not to power).
I would love someone with a FCA11 and the V290 FCB to get dumps. I'm also interested in dumping the supported JVS commands.
This will allow you to dump the memory: https://github.com/GXTX/YAJVSEmu/tree/dump_70
If you pipe the output with >> you'll have a space delineated map of the memory.
As for the supported commands, if you look at the commit history of that branch you'll see `d43b43de4` which will work to dump the supported commands. Since JVS is a standard we can assume correctly by the status bytes if a command is supported or not (02 being unsupported, any other meaning it's supported and we need more params).
I really would like help with this if anyone is available and willing. The wiring is very easy to set-up, you just need a simple RS485 to USB adapter and a USB cable you're willing to lose.
RE the memory dumps: I'm not really sure what's contained in here - we obviously have copies of the JVS inputs and such but that would only take a few bytes and we have nearly 30KB of /real/ used space. We can see at 0x4000 is a list of strings that the monitor would output, at 0x9000 we see the JVS information - the board name, and what it supports, at 0xFB00 we see the datecode (1998 10/26 12:00:00). Not sure the other stuff, maybe some smarter people than me can check it out.

FCA10:
Via dumping my FCA10 I found out a couple of things, one there's a internal "monitor" that you can send commands to `FCA Monitor Ver1.00 by I.Kubota@vr.namco 1998.5.20`, no clue how you would attach to this - all of the serial lines on the MCU are used for other things. Another is that each FCA is programmed with a datecode which you can dump by sending JVS command 0x70 0x02. If you send 0x70 0x03 you'll return a bitmask of the dipswitches. In case it comes up, this FCA was pulled from a 500GP for SuperSystem32.
I've programmed what is known now in my JVS emulator: https://github.com/GXTX/YAJVSEmu/commit/286f12247bc1987cfc3fbbf4bce21cc6b5ea3350