S+ SAS RS232 interface schematics

[Mozart]

Here are two more.

[TZtech]

Those settings look fine although i must say its been ages since i did a setup for a tito environment with back of house server. Maybe one of ou USA techs that frequent the site can confirm ?

[Mozart]

Hello Ian. I'm making great progress, and the raspberry pi is handling like a champ. Hi CPU usage for now, but it doesn't miss a beat. It runs with an FTDI usb to serial. Very stable.

Now that Game Kings are in, I'm off to get the S+ communicating as well, via DCS port (I read the 40 page thread on this, and I'm still confused).

Correct me if I'm wrong: a simple FTDI Usb to serial TTL cable will do the trick? It looks like the interface is required only for the J82 interface, not for the DCS.

(I wish S+ had RS232's at the J82 like the GK's. So simple!)

I have seen a tito system connected directly to the DCS, but I couldn't figure the interface. It was a multi layered board... I only know its possible at this point.

[TZtech]

Thats great news - for S+/PE+ have a look at this thread - http://newlifegames.net/nlg/index.php?topic=11893.0 where I posted details on a FTDI to TTL serial. also see reply 30 in this thread. Or you could just use your current FTDI setup (USB to max 232) and build the interface or use a ebay RS232 module as described by Poppo in the thread.

What programming language are You doing your interface in ? Where You by any chance able to get stick parity operating properly using CMSPAR ?

[Mozart]

Hello Ian,

Long time, but "unforgotten!" :-) 

To answer your questions, I'm using C and FTDI D2XX interface with a FT232R chipset, and it enables mark parity and low latency comm through the API. I downloaded the Raspberry PI in their drivers page[1] and FTDI D2XX manuals[2]. Communication using J82 port is going fine so far.
However, I'm stuck on a problem. I have a few S+ machines that do not have RS232 interfaces (J82 is not RS232 compliant). I've built the posted schematics (TTL to RS232 interface) by Poppo (or Foster) and I can receive the SAS ID from the machine, but nothing gets sent. I've also tried using a simple FTDI USB to TTL (pins 9, 7, 5, 2 on the DCS), and got the same results. Receive no problem, but can't send anything. Are you aware of any detail that I may be missing? The FTDI USB-TTL appears to be a straight forward solution... 

If you need help setting up the serial port please let me know so I can post the code snipped that does that.

[1] http://www.ftdichip.com/Drivers/D2XX.htm
[2] http://www.ftdichip.com/Support/Documents/ProgramGuides/D2XX_Programmer's_Guide(FT_000071).pdf

[TZtech]

Cool - Good to know the D2XX route works - Have considered that before but never took it further. Code snippets to get this running on the Pi would be great If you are willing to share.

Ok so machine is chirping its adress ?
For S+ I recommend base SP1213. Also push your delay between polls up to 200ms. If that does not work let me know and I will dig for schematics for the DCS interface circuitry.

[poppo]

Cool - Good to know the D2XX route works - Have considered that before but never took it further. Code snippets to get this running on the Pi would be great If you are willing to share.

Ok so machine is chirping its adress ?
For S+ I recommend base SP1213. Also push your delay between polls up to 200ms. If that does not work let me know and I will dig for schematics for the DCS interface circuitry.

I've been PMing Mozart about his communication issue. I am used to a S+ where you have to supply +5V to the motherboard port. Not sure if the GK works the same way, but he has his RS232 adapter's 5v (power in) line going to the DCS port only. I'm thinking he needs to supply +5V like on the S+. But maybe the GK is different. 

[Mozart]

Yes, machine is talking (01 01 01 01...) and I receive it properly, in a terminal. But when transmitting, nothing shows in the Comm Analyzer (when testing via GK's DCS port, same results). I have the same results when using USB-TTL (ftdi) directly wired, or using a circuit posted by Poppo.

SAStest also does nothing (it keeps waiting for a response to initial sync command).

BTW, on the GK, if I switch to the rs232 port (J82), it works flawlessly. It's the DCS that's killing me.  

[Mozart]

Hello Poppo,

I will attempt to supply vcc+5 to the DCS interface from a separate power supply. I think I'm already doing this, via FTDI USB-TTL circuit (VCC pin on the ftdi interface, to the DCS pin 7), but I'll try a different route.

In fact, on the MAX232 schematics you posted (named "schematics of the year!  ) I'm receiving 13vdc from the dcs, and regulating to 5vdc before supplying it back to DCS pin 7.

I'll post results. I'm close!

[poppo]

Hello Poppo,

I will attempt to supply vcc+5 to the DCS interface from a separate power supply. I think I'm already doing this, via FTDI USB-TTL circuit (VCC pin on the ftdi interface, to the DCS pin 7), but I'll try a different route.

I'm not sure if that FTDI USB-TTL supplies the VCC or needs the VCC. Since it is USB powered, it may indeed supply 5V. However, USB has a low current rating, so I don't know if would be wise for that to be an output.

In any case, if you use a separate 5V supply for pin 7 be sure to use a common ground with everything else.  You might also have to supply 5V to that FTDI USB-TTL board on the VCC line. Of course if you have a meter, it would be easy enough to just measure what is on that line.

[Foster]

I would use the +VB in the S+ to a 7805 regulator to pin 7 in the DCS port.
+VB is available in  the SDS (J9) connector pin 2
 

[Mozart]

No go 

I've pulled the VCC line (USB-TTL to pin 7 on the DCS) and wired an external 5v power supply (2A). So... from the external power supply, VCC on DCS pin 7 and ground on DCS pin 3 (which is shorted to pin 2, according to IGT manual). Pin 2 is still connected to GND in the USB-TTL.

This way, I'm powering the DCS interface independently and have a common ground. I can still receive data (machine SAS address) but nothing transmitted (nothing shows on COMM ANALYZER). The TX LED on my USB-TTL is alive, but the vgm does not react/receive.
When I pulled the external 5v power, I stop receiving, which tells me that the interface is properly powered. 
I've tried also using a pull up resistor (750) on the SDO line as instructed by the IGT manual. RX works fine, just to rule it out.

Suggestions are welcome. I'm running out...

[poppo]

Suggestions are welcome. I'm running out...

Not sure about the GK, but is it set up to actually accept the commands? I know on the S+ there are a few different settings that need to be enabled.

[Mozart]

Not aware of anything other than Enhanced Validation and Redemption.
When I switch the primary SAS channel to 3 (rs232 port and using a straight usb-rs232), all works fine. Back to channel 2 and ttl, I only receive.

Do you know what else must be enabled? I can search for the equivalent in the KeyChip menu.

[poppo]

Not aware of anything other than Enhanced Validation and Redemption.
When I switch the primary SAS channel to 3 (rs232 port and using a straight usb-rs232), all works fine. Back to channel 2 and ttl, I only receive.

Do you know what else must be enabled? I can search for the equivalent in the KeyChip menu.

I am not familiar with the GK, only the S+.

Does your USB-TTL need the DTR tied to CTS to trasmit? Do you by any chance have a logic probe that you could put on the TX line of your TTL converter to see if it's sending anything? One thing I like about the IGT RS232-TTL board is is has LEDs so you can see that it's actually doing something.

 

[TZtech]

Posting BP schematics on new site - looks like issue may be with a gnd on pin 1.

[Mozart]

I'll check the new site...
I don't know if this USB-TTL adapter requires DTR tied to CTS, but I'll try. The TX LED on the adapter lights up, but it's on the way in. I'll try to probe it (even with a meter, to see voltage oscillating).

[Mozart]

Gnd on pin 1, I'll try that and post results.
Please post link of new site thread, so I can follow. Thanks.

[Mozart]

  I think I got the DCS port figured out... It makes little sense to me, but it works.

Here is the recipe: I'm using a USB-TTL jumpered to 5v FTDI adapter, and the only pins in use are RX, TX and GND in the adapter end, going to 5, 9 and 2 on the DCS, respectively. The power provided to the DCS port pin 7 is 13v (not 5v as my previous assumptions), so basically I loop back 13v from pin 8 to 7. I also loop agnd from pin 1 to 3, to ground the power circuit.

So communications run on 5v but the internal DCS circuit needs 13v (which it has on pin 8!!).

To figure it out, "I threw the book away" and noticed that applying 5v to the DCS would lit the DS1 (LED) slightly (pale shine) on computer tx and nothing was received on the Analyzer. So... I decided to give it more juice (out of frustration!), and voila!

I'm not sure if this is the correct way of doing this, but I have it synced since this morning and she runs fine.

Any thoughts?

[Mozart]

It's been working fine for a week now, I'm assuming it's properly wired.
Any thoughts?

[poppo]

It's been working fine for a week now, I'm assuming it's properly wired.
Any thoughts?

As long as it works and does not  then all should be good.