FAQ Topcon Electronics
I can not install Projektor Tool on my Window PC. What can I do?
Please run the program from the Windows console (cmd.exe). There will probably be an error message that points to the problem. Often it is a memory problem. Java is configured to allocate 2 GB of RAM for the Projektor Tool. You can change this value. Go open the file *Projektor_Install_Path*\toolchain-1_12_1\etc\toolchain-1_12_1.conf and in line 43, change the parameter -J-Xmx2048m to -J-Xmx1024m This could solve the problem.
I have a terminal with CoDeSys and would like to work with the PClient toolchain now. What should I do on the terminal side?
Just install the PClient with the normal update procedure. Codesys will be removed with this. If you want to work with Codesys again, you can re-install it.
Is it possible to shorten the startup time of the terminal?
The starting time of the terminal is caused by the 32 bit system involved that is similar to a normal PC. Therefore it is not possible to shorten it directly. But it is definitely possible to make the process more suitable using the power management. This contains two variables: @PWR_TimeToSleepMode defines the time in seconds after which the terminal should go into sleep mode (maximum is 2332800 s - 27 days); @PWR_TimeToPowerOff defines the time after which the terminal should switch off completely (maximum is 2332800 s - 27 days).
How can I adjust Power Management settings?
The power management settings can only be configured using variables from the Power Modes group (Index 0x2030). Using these variables, the timeouts can be configured (when going into sleep mode and when switching off completely) and what components shall be switched on/off when entering low power mode. See the PClient variable table for details of each variable (in the folder \manuals\software of the Toolchain download packet). PLEASE NOTE: The configuration file /opt/etc/pm_state.conf is not considered anymore. Only the settings made with the variables will apply.
How can I execute actions when entering different Power Modes?
Power Management variables are available. Please refer to the variable table. PLEASE NOTE: The maximum value for a setting is 27 days. The devices support four power modes:
- Off: The device is completely off, no power is consumed
- On: The device is fully running
- LowPower: Ignition pin was pulled. The device switches off configured modules and tries consumes less power.
- Sleep: When the device is in LowPower mode and a timeout expires, the device enters sleep mode. In this mode only the RAM is supplied with power. Power con-sumption is very low.
Three events are defined for the project to which actions can be assigned: OnPowerOn, OnLowPower and OnSleep. Actions can be assigned to the se events by clicking on the project name in the project tree and then select "Events" in the property pane. The OnPowerOn Event is executed as soon as the device wakes up from sleep mode or from LowPower mode (Ignition is plugged in again). The OnLowPower event is executed as soon as the ignition is pulled. The OnSleep event currently gets executed as soon as the device wakes up from sleep mode (before the OnPowerOn event). This may change in future so that the event is executed as soon as sleep mode is entered. To each of these events one of the following actions can be assigned:
- Execute Script
- Set Value
Some ideas for what these events can be useful:
- Jump to the home (start) page when entering LowPower mode by setting the Page ID to variable @ProjektCurrentPage.
- Initialize variables with default values.
- Mimic the same behavior like a cold boot when the device returns from LowPower or Sleep Mode.
By using a script, the above mentioned ideas can be combined.
How can I show a special screen with progress bar while the project is loaded?
How can I use the beeper in my project?
How to change Encoder rotate direction?
It is possible to change the navigation direction, but it is a bit complicated. It is not a setting you can make in the Projektor Tool. The navigation direction is a configuration parameter of the PClient. To change this you need to edit the actual pclient installation file. You probably know that from an update process. The file name you're looking for is user.tar.gz. You can open this file on the PC using e.g. 7zip. Go to \user.tar.gz\user.tar\pclient\bin\. There you will see several files with the extension .conf. Now you need to choose the correct file. If you have an A3 Eco, use the file a3e.conf. If you use the standard device (with keys and encoder) in landscape mode, use a3s.conf, if you use the A3s in portrait mode, use a3sp.conf.
Now, drag and drop the appropriate conf file e.g. on your desktop. Edit it with an editor, like Notepad ++.
Now add the following line in the section "opus-config": standardNavigationDirection = false;
Save the file, and drag and drop it back from the desktop into 7ip. 7zip will ask if the file should be integrated and you say yes.
Now close 7zip, and it will ask you if you want to update the archive. Say yes again.
Now you have changed the configuration. One more thing to do. As you probably know, all update files come with an extra .md5 file which includes an md5 checksum so that the copied files can be validated in the installation process. Since you have changed the file, you need to update the md5 checksum file. Then you can update the PClient on the device with this changed PClient file.
How can I calibrate the touchscreen of my device?
How to connect OPUS with PC correctly?
There are following point that should be correct configured to setup the connection:
- Make sure that you have the same software level on both your PC and your device.
- Make sure that the ethernet port on the device is working. On the serial console, type ifconfig �a to see all communication ports. You should see an eth0 port with an IP 192.168.135.6 by default. If you don't, write the following commands:
ifconfig eth0 down
ifconfig eth0 192.168.135.6
- Make sure that the PC is in the same subnet as your device (e.g. if the device has 192.168.135.6, set your PC to 192.168.135.xyz)
- Try pinging your device from the PC ("ping 192.168.135.6" on the Windows command line)
- In Codesys, go to Tools -> Options -> Device editor and check "Use classic communication page"
- Make sure that the device description version in Codesys matches the Codesys runtime version. If unsure, update the device description on the PC again.
- In the communications / connection page, set the Filter from "Target ID" to "None"
- Stop and restart the Codesys gateway in the system tray (lower right side, the symbol is a gray square with the front quarter being red)
Which USB-Ethernet adapter are supported by OPUS hardware?
There are drivers for the following chipsets installed:
- ASIX AX88xxx based
- SMSC LAN95XX based
- MosChip MCS7830 based
We always recommend and worked very well over the years with this one:
- LogiLink UA0025C USB 2.0 to Fast Ethernet Adapter