Home · Page index

OC32-FAQ_en

1. I am currently using the OM32serial. Can I add the OC32 to it and use them together ?
2. Can I use the OC32 to control not only servo's but also signals and lightbulbs?
3. I already have a (number of) OM32-serial module(s) connected to my PC, controlled by Koploper. What is the best way to connect the OC32?
4. What is the most convenient way to connect the OC32 to a UCCI?
5. In my miniature world I have both trains and (MCC) cars. Can I use the OC32 for both?
6. Do I always need a U485 with an OC32?
7. In Koploper I can only configure an OM32serial. Can the OC32 actually work with Koploper?
8. If I buy a U485+OC32, can I extend that with extra OM32's later?

1. I am currently using the OM32serial. Can I add the OC32 to it and use them together ?

Yes. In operational mode the OC32 uses the OM32 communication protocol, so the OM32 and OC32 can be used together/ The OM32 and OC32 modules share the same address space so the OM32 and OC32 addresses have to be non-overlapping.

2. Can I use the OC32 to control not only servo's but also signals and lightbulbs?

Yes. The OC32 can do everything an OM32 can and more. You can define per output what to do with it. Roughly speaking, there are 2 restrictions:

3. I already have a (number of) OM32-serial module(s) connected to my PC, controlled by Koploper. What is the best way to connect the OC32?

The easiest way is to connect the OC32 in the same way as the OM32, so via the RS232 interface of the OC32. In this way the OC32 is connected in parallel with the OM32 module(s). You can then operate and configure the OC32 with OC32Config.
The only feature that won't be possible then is updating the OC32 firmware. If you want to do that then you have to connect the OC32 to the PC via a USB-RS485 converter (e.g. the U485).
As an alternative you can connect both OC32's and OM32's to your PC via the U485. You have to provide your OM32's with an RS485 driver IC though. If your OM32's are positioned close together (max. 1 meter) tthen you need to provide only one OM32 with RS485 and cascade the rest (see OM32 manual 2.0).

4. What is the most convenient way to connect the OC32 to a UCCI?

Option 1: (The desired default configuration in these cases)
Connect the UCCI to your PC via USB or RS232 and connect the OC32 (possibly together with OM32's) to the UCCI via RS232. During normal operation you then have only 1 connection between your PC and "the track". In Koploper and OM32Config you have to choose "Dinamo" as the OM32 Com-port. Install an RS485 cable between your OC32's and connect the U485 to it. The cable you roll up and stack it somewhere under your track. Only when you need to configure the OC32's with OC32Config or when you want to upgrade the OC32's with the bootloader do you need to plug the U485 in your PC, configure what you want and disconnect again.

Option 2:
Connect the UCCI via USB and connect the OC32 (possibly together with OM32's) via the U485.
There is then no connection between UCCI and Ox32. You therefore need 2 cables between your PC and "the track". This will work for both configuration of the OC32 and for operation mode. In Koploper you then have to choose a seperate com port for the OC32 (the U485). In OM32Config you DON'T choose for "via Dinamo", because after all you have connected the OM32 and OC32 directly. Be aware: If you also use OM32's, then they have to be provided with an RS485 driver.
The advantage of option 2 to option 1 then is that you don't have to make additional connections if you want to configure the OC32. The disadvantage is that during normal operation you have 2 connections with your track and that have to provide any OM32's with an RS485 driver.

5. In my miniature world I have both trains and (MCC) cars. Can I use the OC32 for both?

Yes, even better, you can use the OC32 simultaneously for the control of components related with both your trains and your cars. In the figure below (click for a larger picture) you will find a possible setup when using 2 Koploper databases on 1 PC, using Dinamo/MCC for your cars and using any other digital system for your trains.

We use the double interface of the OC32. The functions belonging to the trains are controlled by Koploper via the U485 interface. The functions belonging to the cars are controlled via the UCCI. Be aware: The OC32 listens to commands on both interfaces, but you have to see to it that these commands are not conflicting with each other, with other words: the OC32 outputs that you use in your train-database you can't use in your car-database and vice-versa. Koploper won't pay attention to that, because Koploper doesn't know at all that the OC32's connected to both interfaces are in fact the same modules. You therefore have to keep track of this yourself.

6. Do I always need a U485 with an OC32?

No. The OC32 is controllable via RS232 or TTL, so in exactly the same way as the OM32. You can also configure the OC32 via RS232, however, at the moment this has to be a direct connection. So: at this moment you can not configure the OC32 with OC32Config if it is connected to an RM-U or UCCI. Configuring is only possible if you connect the OC32 directly to a com-port of your PC or to a USB-converter.
Updating firmware works only via U485. Beware of the fact that in the future there probably will be many updates with new features. If you want to make use of them then a U485 will be very handy.

7. In Koploper I can only configure an OM32serial. Can the OC32 actually work with Koploper?

Yes. Koploper sees the OC32 as a OM32. The extra commands that the OC32 needs will be provided to Koploper via the OM32 configuration file. Since Koploper doesn't really know what these commands are doing and simply executes them, this mechanism is therefore very flexible and the additional OC32 commands can be added in a simple way.

8. If I buy a U485+OC32, can I extend that with extra OM32's later?

Yes, but only when you have provided all OM32's with an RS485 receiver. Does it concern new OM32's, then such an OM32 with RS485 receiver has almost the same price as an OC32, so that configuration is notvery useful.

The U485 is a USB-RS485 converter. The normalOM32 only understands RS232 and the OC32 is not a converter from RS485 to RS232. The considered configuration PC->U485->OC32->OM32-OM32-OM32-.. is therefore "wishful thinking" and will not work.

For good order: you can add an OC32 to an existing system in which OM32's are used (see question 1) or connect to a system that can control OM32's (such as an RM-U, RM-H or UCCI).

If the functionality of the OM32 does fit your purpose then of course you still can create the normal setup with standard OM32's (do you want to connect that to a USB-port, then you have to do that with a standard USB-RS232 converter, for sale in the well equipped computer retail shops).