Mdb Converter Serial To Ethernet

Posted on admin

Wrote in message news:c4d5b1b0-ea81-446b-ba2a-4f7ebe2811c3@l64g2000hse.googlegroups.com. We understand you. Read the spec to understand what is required to connect. However, even once you have done the hardware to be able to connect to a PC's RS232 port you will, more than likely run into the problem of the 9bit char format not being supported on a std PC serial port.

You can fudge it using the mark/space parity control but it is not very nice. Why don't you use ccTalk instead? Regards PhilW juanma.f.@gmail.com 02:11. In article, says.

Convert Serial Port Connections for Streamlined Ethernet Access Use Ethernet infrastructure for direct device communications. SEL-2890 Ethernet Transceiver Reduce Telecommunications Operating Costs Use SEL-2890 Transceivers and your Ethernet network instead of expensive leased or dial-up connections to reduce monthly operating costs. EtherNetIP / Serial - Converter EtherNetIP / Modbus - Converter: This serie of products allows to integrate a EtherNetIP network with a serial RS232, RS485 or RS422 net.On serial side, it is possible to use Modbus protocol or generic RS232/RS485/RS422 communication. The HD67590 is an EtherNetIP / Serial Converter, (Rs232, RS485 and/or RS422) and it allows you to connect an EtherNetIP network.

Juanma.- Ocultar texto de la cita - - Mostrar texto de la cita - I read a little about spec of 'ccTalk', and this is other protocolno? I need 'to talk' with a vending machine. The standard of vending machine is the MDB (i think). Are you understand me? Thanks you. Here is a USB to MDB bridge: (sorry for the spanning) Here is the protocol: is where you need to go for any info about MDC/ICP juanma.f.@gmail.com 08:07.

On 29 sep, 17:56, James Beck wrote: In article @, says. www.vending.orgiswhere you need to go for any info about MDC/ICP- Ocultar texto de la cita - - Mostrar texto de la cita - Thanks you!! I know this all, but the 'USB to MDB' is not a good solution for meshould be others solutions.

I am interesting in ccTal PhilW but i dont understand how apply this to the vending machine. If the vending machine does not speak CCTalk then there is no way to apply it at all, in this case.

MDB/ICP is the way you will have to go. CCTalk was designed more along the lines of gaming systems and MDB was designed for vending machines and the like. Not that you couldn't use CCTalk in a vending machine, but MDB was standardized for use in them (vending machines) long ago.- Ocultar texto de la cita - - Mostrar texto de la cita - Oh James Beck, i think that you have reason.

Switch

My problem is how comunicate the pc embedded with vending machine with the protocol MDB. If the unique solution the 'MDB - USB adapter'? If you sum the price that a pcembedded+adapter.

For one for machine is very expensive no? It must of having another solution, no? James Beck 11:29. In article, says.Well, if you doing a one off machine, there will never be any economy of scale. If I were doing a single machine/test station, I wouldn't balk at paying the price for the adapter.

If I were doing thousands of them I would look at doing something more task specific and cheaper. You can implement the protocol yourself with some kind of adapter for the PC and a communications library, but that would be what the specification is for. Juanma.f.@gmail.com 12:46.

On Mon, 29 Sep 2008 11:32:31 +1000, 'PhilW' wrote: wrote in message news:c4d5b1b0-ea81-446b-ba2a-4f7ebe2811c3@l64g2000hse.googlegroups.com. I'm sorry but I am not English and I speack English very bad.

My question is: How connect a PC Embedded to Vending Machine? I know that exist a protocol MDB that is used by vending machine, but this conector is different to pc conector (RS232, USB, i2c, etc).

Can I connect a PC Embedded by MDB? Anybody understand me? Thanks you! We understand you. Read the spec to understand what is required to connect. However, even once you have done the hardware to be able to connect to a PC's RS232 port you will, more than likely run into the problem of the 9bit char format not being supported on a std PC serial port.

This is the tricky part. Unless you are prepared to do very low level coding, the only thing I have found so far is some ethernet to 9bit serial converters done by Port Box in Prague. You can fudge it using the mark/space parity control but it is not very nice. This is OK for slow speeds and as long as you are able to disable the interrupts.

Paul cspo.@hotmail.com 13:39. On Sep 29, 3:46 pm, wrote: I need to create adapter for MDB to any port (serial?) the PC. It is difficult? I know computer science, but the electronic.:( any idea? How about doing your own MDB-USB adapter using either the FT232 or related (if it can do 9-bit serial) or some more capable USB microcontroller.

You could even use a microcontroller as a bridge between 8 and 9 bit serial. What you would want to do is check microcontrollor data sheets and find one with a serial port that can be programmed to 9 bits.

Wrote in message news:73aaa712-5e75-4674-a2b2-3a62b78569a3@p25g2000hsf.googlegroups.com. An adaptor is not an easy thing to do, simply due to the fact you need to maintain the timing specifications of the MDB protocol. An adaptor that just recieves a command from the PC, re-formats it for MDB and then sends it on, waits for the response and forwards that to the PC will easily break the timing criteria of the protocol, considering that each char takes 1mS to transmit or receive. Concerning USB adaptors. Can be good providing they support, and implement the mark/space parity support correctly. However, you still have to provide low level coding to fudge the 9 bits via the mark/space parity. In addition you will be required to add timing delays to ensure the parity changes are sent over USB before transmitting the next data or parity change.

We have had success with the CP2102 from silicon Labs. It is sure however, from experience, that supporting MDB over USB is a lot more painful than a standard serial port. Another alternative is to acquire an add-on serial port that natively supports 9 data bits at the hardware level.

Not cheap, hard to find and expensive. As for the vending machine implementation, you have not said, but I conclude that YOUare building the vending machine and YOU therefore have control over the protocol to use. Unless by some specification requirement that you use MDB, I see no reason why you cannot use ccTalk. I believe the 'protocol' is purely for internal machine use, aimed at connecting all peripherals to a host controller, namely your embedded PC. Any external communications is usually by some other communications link, modem, ethernet, wifi, etc. It's simple and most importantly can be easily supported by any PC serial port, USB adaptor etc that supports the standard 8bit char length. It could be any other protocol besides, that uses the 8bit data length as well.

It's just that ccTalk is well documented, well supported and widely used. We produce products that support both MDB and ccTalk in addition to others. We much prefer ccTalk for its non requirement of the 9bit data format. Regards PhilW juanma.f.@gmail.com 01:11.

Wrote in message news:ef120646-80af-45a8-91c1-d53caeabebhsb.googlegroups.com. Ok, then you have no choice but to write low level code to fudge the 9bit char by using the mark/space parity control. You do this by programming the UART 8bit with parity, that makes the 9 bits. The parity you program to be manually controlled using the mark/space controls to simulate the ninth bit. When you sent the first byte of the message, you first make parity to be Mark, this makes effective 9th bit set = address byte. Send the address byte.

Serial To Ethernet Converter Software

You then make parity to be Space for remainder of message = 9th bit clear. To receive a reply just set to space parity and look for parity error for end of message. Since this is a fudge you will be at risk to miss-interpreting a real parity error, but that is the consequences of not having full 9 bit support in hardware. Anyhow good luck. It can be done, I know because we support it. It's just not an ideal solution. Until you really know what you doing in it's implementation, stay away from virtual serial ports over USB because they do not act the same as a standard serial port.

They move data in blocks and will not maintain the parity manipulation synchronously with the data bytes. They will need delays to allow the control commands to transfer before sending the data etc. This will slow down your effective data rate under MDB.

Also you should make an investment in a good serial coms monitor tool, that can capture and timestamp every event on the link between the host and the device. It will pay for itself easily in the time you save discovering what is really happening in the transfer. We used a tool called 'ViewComm Async' from. Such a tool is worth it's weight in gold. Regards PhilW juanma.f.@gmail.com 18:04. On Wed, 1 Oct 2008 09:42:46 +1000, 'PhilW' wrote: Ok, then you have no choice but to write low level code to fudge the 9bit char by using the mark/space parity control.

Sorry for jumping in here so far down in the thread, but to throw out another option for the OP: Add a microcontroller as the glue between the embedded PC and the MDB device. There are probably other chips but one family that I'm familiar with that could handle this easily is the Atmel AVR ATmega. These natively support 9-bit serial (in addition to the usual other formats) and, in addition, can filter on the 9th bit set (MDB address mode). Almost like they were made to support this protocol. Pick one with dual UARTS and talk to it serially, or get one with a USB peripheral and communicate with it that way. It would take a teeny bit of work but may be cleaner, in the end, than trying to dance with the parity bit.

Rich Webb Norfolk, VA PhilW 22:12. Wrote in message news:ed142d1d-3df5-40ee-8eea-d698f3fbb7be@m3g2000hsc.googlegroups.com. Juan, I think you need to read the spec. There are to many details to deal with here.

To connect to the PC you must build and interface circuit. How you do that is up to you. Sect 4 of the spec tells you all you need to know. It even gives a sample schematic.

Serial to ethernet wiring diagram

The bus is a multi drop bus, many slaves with one master. You still have not made clear which one you want to be. I know you have said you are not building the vending machine, but you also have not said what you want to be, Host or slave. Are you the host controller or are you one of the slave devices. I assume you do understand that the protocol is an internal machine protocol and that you do not talk to the machine from the outside using MDB? Anyhow, as for connecting to the PC.

Serial

Assuming you are the host, the interface you build will give an output of RS232 that you can connect to the PC. The monitor you simply insert in between the interface and the PC.

Regards PhilW PhilW 22:45. 'Rich Webb' wrote in message news:vlj5e4t6lqqprmagrakv9tp44joer11otm@4ax.com. Hi Rich, If you have look back through some of the posts I mentioned why your suggestion is not really a viable solution. It has to do with the msg response time. In Sect 3 it says that a device, or host, must respond to a msg within 5mS (5 char times).

Therefore if you place a translator in series you will probably blow that out of the water. By how much will depend on your implementation. If you simply receive the command into the translator, convert it and resend it to the device, your response time will be msg length(in chars @ 1mS each). 2 + device response time at best. With a message up to 36 bytes in length will be 72mS + device response time. See what I mean. A better way would be to receive the msg from the host and convert on the fly, retransmitting 1 char behind.

At least you may be able to reduce it down to 2mS + device response time. That only gives you a 3mS response time window in the device to meet spec. On top of that, in both the above cases, you will need to implement how you are going to talk to the PC and keep the msgs in synch without an address/msg end byte (9th bit). Am I making sense? Regards PhilW juanma.f.@gmail.com 04:13. Yup, totally.

Interesting thread;-) I wouldn't do this as a byte-wise buffer device, but rather as a higher level gateway. Implement the MDB state machine in the microprocessor to behave as the communications gateway, peripheral, or bus master as required/desired. The side facing the PC could run at a higher baud (or even over a different medium) and would not necessarily use the MDB message structure. Personally, on the side facing the PC I'd try very hard to push everything into a plain-text format. Easy to monitor and log, simple to debug, and it can be digested by lots of analysis tools without a separate binary - ASCII translator pass. Rich Webb Norfolk, VA cspo.@hotmail.com 07:01.

On Sep 30, 7:42 pm, 'PhilW' wrote: Anyhow good luck. It can be done, I know because we support it. It's just not an ideal solution. Until you really know what you doing in it's implementation, stay away from virtual serial ports over USB because they do not act the same as a standard serial port. They move data in blocks and will not maintain the parity manipulation synchronously with the data bytes.

I don't think one should try to do the parity trick with a virtual serial port. However, some of the USB serial chips may be flexible enough to implement a 9-bit mode without resorting the parity trick. Alternatively, some of the USB-capable microcontrollers certainly are. And then there's the possibility of a parallel interface chip, and a small CPLD. None of these would be presented to the host PC as a serial port, but instead as a custom interface. Wrote in message news:dbf851fb-651e-4c99-ac11-561f5a9b8e54@l64g2000hse.googlegroups.com. leer m�s �- Ocultar texto de la cita - regards.

Hi Juan, Yes it is possible, but everything I mentioned previously remains the same. To be honest we have not looked at Section 8, we are mainly involved in coin/note validation. However, nothing else changes. The device you want to build is still just a device that must meet the standard MDB interface specification. Connection to the MDB bus for you as a device is much simpler than that of a host.

You can get away with a couple of opto couplers, just like in the sample schematic in that section 4. You would be for eg slave 1. PhilW PhilW 15:35.

Wrote in message news:da3e7bf3-6a2c-4159-8f92-fe328ec201e4@k7g2000hsd.googlegroups.com. On Sep 30, 7:42 pm, 'PhilW' wrote: Anyhow good luck. It can be done, I know because we support it.

It's just not an ideal solution. Until you really know what you doing in it's implementation, stay away from virtual serial ports over USB because they do not act the same as a standard serial port. They move data in blocks and will not maintain the parity manipulation synchronously with the data bytes. I don't think one should try to do the parity trick with a virtual serial port.

However, some of the USB serial chips may be flexible enough to implement a 9-bit mode without resorting the parity trick. Alternatively, some of the USB-capable microcontrollers certainly are. And then there's the possibility of a parallel interface chip, and a small CPLD.

None of these would be presented to the host PC as a serial port, but instead as a custom interface. Hi, I'm not aware of any USB chips that support full 9 bit mode. Probably for a couple of reasons (off the top of my head). They are designed emulate a PC serial port, the CDC spec does not really support it. The CDC spec is rather broad in its possible applications, but the section that is utilised for virtual serial ports is based on the modem type interface. As far as I'm aware modems don't use 9bit.

Even though some USB-capable chips are able to support 9bit serial, supporting it through the USB is another question. PhilW juanma.f.@gmail.com 09:10. On 2 oct, 00:30, 'PhilW' wrote: Hi JuanYes it is possible, but everything I mentioned previously remains the same. To be honest we have not looked at Section 8, we are mainly involved in coin/note validation. However, nothing else changes. The device you want to build is still just a device that must meet the standard MDB interface specification. Connection to the MDB bus for you as a device is much simpler than that of a host.

You can get away with a couple of opto couplers, just like in the sample schematic in that section 4. You would be for eg slave 1. PhilW PhilW, Have you anyone schematic to make a adapter MDB to RS232 or any pc port (usb, rj45, etc.)?? Juanma.f.@gmail.com 17:29. However, some of the USB serial chips may be flexible enough to implement a 9-bit mode without resorting the parity trick. Alternatively, some of the USB-capable microcontrollers certainly are. I'm not aware of any USB chips that support full 9 bit mode.

Even though some USB-capable chips are able to support 9bit serial, supporting it through the USB is another question. I'm unsure if there are affordable off-the-shelf USB to 9 bit adapters (Black Box probably has an adapter for $$$). Atmel AVR and Microchip PIC chips (such as the PIC18F14K50, PIC18F66J50 as featured in the October 2008 Circuit Cellar magazine) have 9 bit UARTS and USB 2.0 on chip, but require your own programming.

Manufacturer's Application Notes and user support might give you all the building blocks, perhaps entire programs to handle the problem.

Click to expand.Oh, I see that you understand me I need to create adapter for MDB to any port (serial?) the PC. It is difficult?

I know computer science, but the electronic. An adaptor is not an easy thing to do, simply due to the fact you need to maintain the timing specifications of the MDB protocol. An adaptor that just recieves a command from the PC, re-formats it for MDB and then sends it on, waits for the response and forwards that to the PC will easily break the timing criteria of the protocol, considering that each char takes 1mS to transmit or receive. Concerning USB adaptors. Can be good providing they support, and implement the mark/space parity support correctly.

However, you still have to provide low level coding to fudge the 9 bits via the mark/space parity. In addition you will be required to add timing delays to ensure the parity changes are sent over USB before transmitting the next data or parity change.

We have had success with the CP2102 from silicon Labs. It is sure however, from experience, that supporting MDB over USB is a lot more painful than a standard serial port. Another alternative is to acquire an add-on serial port that natively supports 9 data bits at the hardware level. Not cheap, hard to find and expensive. As for the vending machine implementation, you have not said, but I conclude that YOUare building the vending machine and YOU therefore have control over the protocol to use. Unless by some specification requirement that you use MDB, I see no reason why you cannot use ccTalk.

I believe the 'protocol' is purely for internal machine use, aimed at connecting all peripherals to a host controller, namely your embedded PC. Any external communications is usually by some other communications link, modem, ethernet, wifi, etc. It's simple and most importantly can be easily supported by any PC serial port, USB adaptor etc that supports the standard 8bit char length. It could be any other protocol besides, that uses the 8bit data length as well.

It's just that ccTalk is well documented, well supported and widely used. We produce products that support both MDB and ccTalk in addition to others. We much prefer ccTalk for its non requirement of the 9bit data format. Regards PhilW.

Oh, I see that you understand me I need to create adapter for MDB to any port (serial?) the PC. It is difficult? I know computer science, but the electronic. An adaptor is not an easy thing to do, simply due to the fact you need to maintain the timing specifications of the MDB protocol. An adaptor that just recieves a command from the PC, re-formats it for MDB and then sends it on, waits for the response and forwards that to the PC will easily break the timing criteria of the protocol, considering that each char takes 1mS to transmit or receive. Concerning USB adaptors. Can be good providing they support, and implement the mark/space parity support correctly.

However, you still have to provide low level coding to fudge the 9 bits via the mark/space parity. In addition you will be required to add timing delays to ensure the parity changes are sent over USB before transmitting the next data or parity change. We have had success with the CP2102 from silicon Labs. It is sure however, from experience, that supporting MDB over USB is a lot more painful than a standard serial port. Another alternative is to acquire an add-on serial port that natively supports 9 data bits at the hardware level. Not cheap, hard to find and expensive.

As for the vending machine implementation, you have not said, but I conclude that YOUare building the vending machine and YOU therefore have control over the protocol to use. Unless by some specification requirement that you use MDB, I see no reason why you cannot use ccTalk. I believe the 'protocol' is purely for internal machine use, aimed at connecting all peripherals to a host controller, namely your embedded PC. Any external communications is usually by some other communications link, modem, ethernet, wifi, etc. It's simple and most importantly can be easily supported by any PC serial port, USB adaptor etc that supports the standard 8bit char length.

It could be any other protocol besides, that uses the 8bit data length as well. It's just that ccTalk is well documented, well supported and widely used. We produce products that support both MDB and ccTalk in addition to others. We much prefer ccTalk for its non requirement of the 9bit data format. Regards PhilW- Ocultar texto de la cita -Mostrar texto de la cita. Click to expand.Ok, then you have no choice but to write low level code to fudge the 9bit char by using the mark/space parity control. You do this by programming the UART 8bit with parity, that makes the 9 bits.

The parity you program to be manually controlled using the mark/space controls to simulate the ninth bit. When you sent the first byte of the message, you first make parity to be Mark, this makes effective 9th bit set = address byte.

Send the address byte. You then make parity to be Space for remainder of message = 9th bit clear. To receive a reply just set to space parity and look for parity error for end of message. Since this is a fudge you will be at risk to miss-interpreting a real parity error, but that is the consequences of not having full 9 bit support in hardware. Anyhow good luck. It can be done, I know because we support it.

It's just not an ideal solution. Until you really know what you doing in it's implementation, stay away from virtual serial ports over USB because they do not act the same as a standard serial port. They move data in blocks and will not maintain the parity manipulation synchronously with the data bytes. They will need delays to allow the control commands to transfer before sending the data etc. This will slow down your effective data rate under MDB. Also you should make an investment in a good serial coms monitor tool, that can capture and timestamp every event on the link between the host and the device. It will pay for itself easily in the time you save discovering what is really happening in the transfer.

We used a tool called 'ViewComm Async' from. Such a tool is worth it's weight in gold. Regards PhilW. Click to expand.Sorry for jumping in here so far down in the thread, but to throw out another option for the OP: Add a microcontroller as the glue between the embedded PC and the MDB device. There are probably other chips but one family that I'm familiar with that could handle this easily is the Atmel AVR ATmega. These natively support 9-bit serial (in addition to the usual other formats) and, in addition, can filter on the 9th bit set (MDB address mode).

Almost like they were made to support this protocol. Pick one with dual UARTS and talk to it serially, or get one with a USB peripheral and communicate with it that way. It would take a teeny bit of work but may be cleaner, in the end, than trying to dance with the parity bit. Click to expand.Oh, I think that I understand you. But, I have a question. How connect MDB to Serial Port, for use the monitor tool??

Juan, I think you need to read the spec. There are to many details to deal with here. To connect to the PC you must build and interface circuit. How you do that is up to you. Sect 4 of the spec tells you all you need to know.

It even gives a sample schematic. The bus is a multi drop bus, many slaves with one master.

You still have not made clear which one you want to be. I know you have said you are not building the vending machine, but you also have not said what you want to be, Host or slave.

Are you the host controller or are you one of the slave devices. I assume you do understand that the protocol is an internal machine protocol and that you do not talk to the machine from the outside using MDB? Anyhow, as for connecting to the PC.

Assuming you are the host, the interface you build will give an output of RS232 that you can connect to the PC. The monitor you simply insert in between the interface and the PC. Regards PhilW. Sorry for jumping in here so far down in the thread, but to throw out another option for the OP: Add a microcontroller as the glue between the embedded PC and the MDB device.

There are probably other chips but one family that I'm familiar with that could handle this easily is the Atmel AVR ATmega. These natively support 9-bit serial (in addition to the usual other formats) and, in addition, can filter on the 9th bit set (MDB address mode). Almost like they were made to support this protocol.

Pick one with dual UARTS and talk to it serially, or get one with a USB peripheral and communicate with it that way. It would take a teeny bit of work but may be cleaner, in the end, than trying to dance with the parity bit. Click to expand.

Hi Rich, If you have look back through some of the posts I mentioned why your suggestion is not really a viable solution. It has to do with the msg response time. In Sect 3 it says that a device, or host, must respond to a msg within 5mS (5 char times). Therefore if you place a translator in series you will probably blow that out of the water. By how much will depend on your implementation.

If you simply receive the command into the translator, convert it and resend it to the device, your response time will be msg length(in chars @ 1mS each). 2 + device response time at best.

With a message up to 36 bytes in length will be 72mS + device response time. See what I mean. A better way would be to receive the msg from the host and convert on the fly, retransmitting 1 char behind. At least you may be able to reduce it down to 2mS + device response time. That only gives you a 3mS response time window in the device to meet spec. On top of that, in both the above cases, you will need to implement how you are going to talk to the PC and keep the msgs in synch without an address/msg end byte (9th bit).

Am I making sense? Regards PhilW. Oh, I think that I understand you. But, I have a question. How connect MDB to Serial Port, for use the monitor tool?? Juan, I think you need to read the spec.

There are to many details to deal with here. To connect to the PC you must build and interface circuit. How you do that is up to you. Sect 4 of the spec tells you all you need to know. It even gives a sample schematic. The bus is a multi drop bus, many slaves with one master.

You still have not made clear which one you want to be. I know you have said you are not building the vending machine, but you also have not said what you want to be, Host or slave. Are you the host controller or are you oneof the slave devices. I assume you do understand that the protocol is an internal machine protocol and that you do not talk to the machine from the outside using MDB? Anyhow, as for connecting to the PC.

Assuming you are the host, the interface you build will give an output of RS232 that you can connect to the PC. The monitor you simply insert in between the interface and the PC. Regards PhilW. Hi Rich, If you have look back through some of the posts I mentioned why your suggestion is not really a viable solution. It has to do with the msg response time. In Sect 3 it says that a device, or host, must respond to a msg within 5mS (5 char times).

Therefore if you place a translator in series you will probably blow that out of the water. By how much will depend on your implementation. If you simply receive the command into the translator, convert it and resend it to the device, your response time will be msg length(in chars @ 1mS each). 2 + device response time at best. With a message up to 36 bytes in length will be 72mS + device response time. See what I mean.

A better way would be to receive the msg from the host and convert on the fly, retransmitting 1 char behind. At least you may be able to reduce it down to 2mS + device response time. That only gives you a 3mS response time window in the device to meet spec. On top of that, in both the above cases, you will need to implement how you are going to talk to the PC and keep the msgs in synch without an address/msg end byte (9th bit). Am I making sense? Click to expand.Yup, totally. Interesting thread;-) I wouldn't do this as a byte-wise buffer device, but rather as a higher level gateway.

Mdb Converter Serial To Ethernet Cable

Implement the MDB state machine in the microprocessor to behave as the communications gateway, peripheral, or bus master as required/desired. The side facing the PC could run at a higher baud (or even over a different medium) and would not necessarily use the MDB message structure.

Serial To Ethernet Server

Personally, on the side facing the PC I'd try very hard to push everything into a plain-text format. Easy to monitor and log, simple to debug, and it can be digested by lots of analysis tools without a separate binary - ASCII translator pass.