Q:
I have got a problem this morning. When I start PTC04, I found that the offset of 'Supply Drv +35/2'is always '-40'.In this case, I can get no output of pps in the 'measure' mode. During 'system check', all the 'Internal Supplies' seems all right.
Then, I can not operate on the 90316BAD with a message 'the voltage is too low'. I wonder what happen to my PTC04? It is all right yesterday. How can I get back a right voltage?
|
A:
Your explanation shows that the progrmmer and calibration is ok. Also for the "Supply Drv +35/2" it is normal that the offset is -40.
The message you get sounds more to the external supply. The PTC works between 24V and 48V but the different projects are requesting different minimums. With a 48V supply, everything should work. With 24V, some device might give the message that it's not sufficient
|
Q:
I am trying to find a more complete list of commands for the MLX90614 Evaluation Board software.
At present, I have two MLX90614s plugged into the one board, at addresses 0x05A and 0x05B. The supplied the Configurator software can see both sensors, and I can access each sensor, measure data etc. (so all working as expected). I am also able to obtain this data using the MLX90614 Configurator Console Utility using, for example, the command, “rr 0x06” (eg. to obtain the die temperature).
Now, one thing I have noticed is that when I switch between each sensor (using the device list in the GUI), the console utility window displays the message “Slave address set to 0x05A” – however, there does not seem to be an actual command to change the active device in the Console Utility! So, my question is, where can I find a complete list of commands for the Console Utility?
|
A:
When you start the console and type: list
You should see a list of all available commands.
Please NOTE that some of the commands can be harmful for you DUT or the EVB from SW point of view so you better be sure what are you doing before attempting to change settings.
The command you're mentioned is SA.
|
Q:
Yup, SA is indeed the command I was looking for so thanks for that! =) Although, for some reason 'list' (or 'List' or 'LIST') doesn't do anything - the console just gives me an error!
But it's not serious, because SA is the command I really needed...
|
A:
I guess you have and old version of the SW.
I suggest to download the latest version from our web site following the link.
http://www.melexis.com/general/general/EVB90615_686.aspx
Please note that this SW supports both MLX90614 and MLX90615.
|
Q:
I am using the demo board MLX90601 with the MLX90601C.
After installing the software, I can't get the USB to recognize the part.
It says it is not connected / can't find part. The computer system shows that the board is not connected.
Suggestions?
|
Q:
I think the problem is caused by drivers. I sent you by mail a SW with the USB drivers that I know as working.
Please accept my apology for the tremendous delay and the problems you experienced!
|
Q:
I just got the DVK90109. It has power and I think I'm trying to communicate with a functioning COM2 port. It won't respond to even a Version request.
What can I be doing wrong?
|
A:
If you are using COM2, you may use the right part of the RS232 User Interface. Please be sure the corresponding COM port is open by clicking the button "OpenComX" and configured to br9600 by clicking on the "Setupcom" button (at the Bottom). After configuring the corresponding COM port, you have to load the list of command by clicking on the "ReadFileComX" button.
Please note that the left or the right part of the RS232 User Interface should be used according to the COM port (left for COM1 and right for COM2).
You could also try to use COM1.
|
Q:
i wanted to know how to communicate with EVB90121 from microcontroller.so i need source code for DVK90121. I have purchase DVK90121 yet I still cant figure out how to communicate from my microcontroller to EVB90121
|
A:
Source code for Atmel microcontroler is available through UT121 in the tab Source in the menu.
If you do not have this tab, please update the UT121 by selecting Update now in the Option tab.
|
Q:
The UT121 software contains two Inventory with mask functions in ISO15693 Dual Sub-carrier:
Inventory xxxxxxx1 - Iso15 07010101 crc slot 16 wait 2
Inventory xxxxxxx0 - Iso15 07010100 crc slot 16 wait 2
I am trying to make an Inventory without mask function in ISO15693 Dual Sub-carrier. The following function gives a response but it's not working:
Inventory xxxxxxxx - Iso15 07010000 crc slot 16 wait 2
What would be the working function?
|
Q:
I want to have this function working for speed issues. I am presently reading 3 chips in 750ms (using both inventory functions). If I remove the "wait 2" statement for both function, I am reading 3 chips in 281ms.
I am developping a pcb for a casino application and those delays are way too big. Is there a register setting better than "6001000DBFEFFBFE7BDF1F7E00" speed wise? Can we get the eval board to work at a higher baud rate, example 115200 baud? Any other ideas to speed up the inventory process?
|
A:
we have double checked by reading the ISO15693 standard.
If a mask-length 00 is used there should be no mask bytes. So, the command should be ISO15 070100 crc slot 16
|
Q:
I work with the DVK90121 and try to understand the sourcecode of the Atmel.
But I can´t find some functions (e.g. SysComInit()). The prototypes are listed in syscom.h but there isn´t an associated syscom.
|
A:
The Syscom.h header file declares a specific function written in assembler used to access to the code memory of the microcontroller. This function is not provided in the firmware example, as it is too specific and doesn't help for the development of the customer's application.
|
Q:
We have been working with RFID at 13.56Mhz for 3 years and we think MLX90121 is a very interesting product.
We are now starting a new electronic RFID reader development probably with your chip.
We are getting samples and DVK90121 but in order to simplify the development we would like to know if it is possible to get the firmware of the ATMega128 microcontroller of DVK90121 board.
We use usually this microcontroller and your help would be grateful for our purposes.
|
A:
No problem. We have just released a new version of the software which allows automatic update, and with a password, automatic download of the source code. Contact us through your local sales representative for details.
|
Q:
The 14443A and B works fine, I can select a command and repeatedly send. But once I do this on any of the 15693 single carrier command, after it send out one command it hangs. The window will show as no device, I have to power cycle the melexis board. Please help as I virtually can not do anything.
|
A:
As I understood, you are able to perform at least one comumincation with the ISO14443 and ISO15693 transponders. But, as soon as you try to send the ISO15693 ASK command repetitely, the progam hangs-up and is not able to detect the DVK90121 anymore.
I think it is a firmware problem otherwise you will see the same problem in each mode. So the only think that I can suggest now is to make an update in the UT131 software to be sure that you get the last version of the firmware.
|
Q:
I buy two DVK90121 and I'd like to communicate thru them with NFC protocol... but I don't find the software to do it...
|
A:
The DVK90121 allows you communicate with a transponder using basic ISO commands (ISO15693 and ISO14443). The NFC protocol at 212kbit/s as presented in the corresponding application note is not supported by the development kit. For that, you will need to write the firmware by yourself.
Please note that only the NFC at 212kbit/s (Felica protocol) is supported by the MLX90121. The others modes (106kbit/s, 424kbit/s and 848kbit/s) will not be able to implemented with this device.
|
Q:
The NFC file transfer described in the application note was actually the reason I purchased 2 development kits. Is there a possibility to obtain the code so I can at least repeat the experiment described in the application note ? Unsupported code should be fine since I don't need to tweak data rates, protocol etc...
|
Q:
About the source code for the firmware in the DVK90121?
Does the DKV90121 to include files with the source code ?
If not, Is it possible to get this source code after the purchase ? Is there some aditional cost in this case?
|
A:
The firmware of our development kit DVK90121 can be delivered on demand using the user interface software UT121.
Please note that this firmware is delivered as an example only and therefore, we will not provide any support on it. Moreover, we cannot guarantee that this software will fit in your application and will be plug and play. You will need to write the firmware of the MLX90121 according to your application.
Please contact us through your local sales representative.
|
Q:
i wanted to know how to communicate with EVB90121 from microcontroller.so i need source code for DVK90121.
|
A:
the source code of the DVK90121 is provided with the development kit only . Therefore, to have access to this source code example, you have to get a DVK90121.
Please let contact us through your local sales rep when you have such a development kit, and then we will send you the access file and the procedure to download the source code.
|
Q:
Actually we have purchased the development kit.The details are as follows
Universal Development board DVKRFID(2002)
Evaluation board EVB90121(1067)
13.56Mhz PCB Antenna ANT1_0(1046).
|
A:
Contact us through your local sales rep and we will send the needed access file and the procedure to download the firmware example.
|
Q:
i want Source code(not bin or Hex file),it may be C language or assembly.Because i am facing problem to communicate with our RFID application so if i know how you have communicated with the kit from Atmega32 then i can proceed my further development.
|
A:
Contact us throus your local a sales and the file will be sent to you that will give you access to the source code in C language.
|
Q:
I recently purchased four DVK90121 and I can see the source code using the UT121 software that came with the CD. But, I cannot copy the code to my workspace. I want to test some features especially the "Direct Transmission/Reception" by modifying the MLX90121 registers. Please let me know how I can get access to the C language code. I have the necessary JTAG and other dev platform for Atmega 128.
|
A:
Through UT121, you should have access to a window which shows all C source code
Select the code you need to copy with: Shift+arrow
Copy the code with: Ctrl+Insert
Past it with : Shift + Insert
|
Q:
I would like to know if it is possible to program the DVK90121 development kit. We want the development kit to interpret the read tags and produce some specific out commands dependant on the group of tags existing on the read range.
If this is possible, which development tools do we need?
|
A:
With the DVK90121, it is possible to build you own commands by combining different ISO commands.
The DVK90121 uses a ATMEGA CPU. You will then need the Atmel development tools and the source code of the program running on the DVK90121.
Then we need more information about your application.
|
Q:
Is the source code readily available?
|
A:
The source code can be provided on request once you have purshased the DVK90121.
|
Q:
I think I found a quite important "error" in your EVB90121 layout: As I am using a "non"-Standard-antenna (but with Impedance matching to 50 Ohms) I had to use the external envelope detector as described in your Application notes.
But then I found out that the voltage supply at pin VDD is quite noisy because there you use it as a common pin for the output stage, the digital section and the analog receiver section.
I did a few simulations with a "real" X7R-cap. and found out that due to its limited RF-ability a ripple voltage of appr. 50-100mV peak-peak cannot be suppressed in the actual layout.
If no separate decoupling of VDD occurs at the external envelope detector I found out that the ripple at the RX pin causes wrong "1"-signals at the DOUT pin.
I suggest to use the VK200 choke only to decouple the output stage and connect the other supply lines directly to the output of the voltage regulators; maybe separated by their own L-C-combination.
|
Q:
The X7R-cap-simulations refer to the VK200-choke and the blocking caps at VDD. The tantalum caps are ignored as they are not able to handle frequencies >10kHz in a satisfying way.
|
Q:
How does the EVB7122 evaluation board work if the modulation is FSK?
|
A:
The TH7122 supports both ASK and FSK.
|
Q:
The EVB7122 comes in several different variants, depending on which frequency you want. Are these freq's fixed, or can I still use any freq between 300 and 915MHz with these evaluation boards?
|
A:
The evaluation board works at one of these fix frequencies 315, 433, 868 or 915MHz.
Even if the device MLX7122 handles the frequency range from 300 to 915Mhz, the matching networks on the evaluation board have to be fine tuned according to the chosen frequency.
|
Q:
I have to design a transceiver at 170MHz. I got a EVB7122 board and put on the VCO an external varactor diode (BBY53) to get this output frequency.
When I try to increase the TXPOWER from P1 to P2 the voltage on Pin 23 (LF) is going to zero and so the output frequency change. Then I changed the VCOCUR to the highest. After that it works. But then I changed from P2 to P3 and I have the same problem.
Can you please help me what is to do that the Output frequency is constant at every TXPOWER mode?
|
A:
Check the tuning voltage on pin 23. It is probably close to 0V. The VCO capacitance changes slightly with VCO current and output power. If it is close to the limit, it will loose lock with different settings. I can send you a schematic for my board which tunes 160-174MHz if you would like it.
|
Q:
I am unable to change the transmit frequency of the evb7122 eval board with the melexis software. I'm using 5 volt VCC and my parallel port output high level is 5v. A logic analyser on the sclk, sdata, adn sden lines show valid timing.
|
Q:
(oops, I hit the enter key too soon) Any Signal on the board that must be set up other than the spi interface to set or change the output frequency? Am I missing something. So far, all I've done is applied power and connected the spi cable. I can see the RO osc. start and I can generate an output at the sma connector. I cannot seem to change the output frequency.
|
Q:
I had a bad scope probe, it was ringing. have been able to move the frequency around now. I now have the LO working on my board.
|
Q:
Can you tell me where I can buy the EVB7122X-433-FSK-C evaluation board? I have not been able to locate it from distributors or the online store here.
|
A:
Thank you for your interest in Melexis' products. To be ablo to help you, I need your contact details.
Could you please forward me those?
|
Q:
Thank you for your interest in Melexis RF products. We will need to work with you directly to get your order placed. Please contact your local sales representative to begin the process
|
Q:
I have just received the EVB90109 & EVB90121 boards. I have installed the UT121 software and it updated itself to this:
Lib Mosaique; Release 1.5 (version: 1.5)
Lib Ut121Ban; Release 2.14 (version: 2.14_0)
Lib Ut121Main; Release 2.22 (version: 2.22)
Lib Ut121Update; Release 2.1 (version: 2.1)
Fw Ut121Firmware; Release 1.9 (version: 1.9, Build SoftDist/Atmel 2005.10.10/2005.10.10)
I am sending the Root->ISO15693->ISO15693 Dual Sub-carrier->Inventory xxxxxxx0 command and I always get this result:
Iso15 07010100 crc slot 16 wait 2 ->
<- OK - Command has been sent
<- TAG NoResp
<- TAG NoResp
<- TAG NoResp
<- TAG NoResp
<- TAG NoResp
<- TAG NoResp
<- TAG NoResp
|
A:
First of all, thanks for your interest in our products.
One preliminary question: If TAG supports RSB (ReadSingleBlock) command, does it answer on it?
The difference between Inventory xx0 and xx1:
for xx0 -> Iso15 07010100 crc slot 16 wait 2
for xx1 -> Iso15 07010101 crc slot 16 wait 2
We made just 2 examples for inventory commands, for LSB=0 and LSB=1. If you need more complex algorithm to obtain all UIDs, you must consult ISO15693 standard.
|
Q:
Tags support RSB but are not responding to the command.
If the first inventory command is for LSB=0 and the second is for LSB=1 then every tags should have responded to either one of the two commands, right? Both inventory command always return TAG NoResp!
Could I have jumper descriptions for the two boards (defaults)?
|
A:
Maybe the registers settings of the MLX90121 is not correct. Can you please send me the registers configuration that you have for every modes (ISO15693 ASK and FSK, ISO14443 A and B)? You will see the registers settings if you click on the "R" button on the top of the UT121 software (this is explain in the DVK90121 user manual).
|
Q:
I have just started the program to look at the registers. The software updated itself and reflashed the firmware. I tried the inventory again and it worked! Looks like the latest software/firmware update did the trick... I can now read tags so my problem is closed.
|
Q:
I´ve got the Evaluation Board for the MLX90121(EVB90121) and use it to send power to my custom-built sensor-tag circuit and to recieve the data. The senor-tag modulates the field by ASK with a subcarrier (423kHz).
I run the EVB in direct reception mode.
Now the problem...
On the Dout line are some "peaks" appearing without having any modulation on the 13,56MHz field. And the sensor-tag is out of range.
The "peaks" are comming more or less periodical.
I´ve tried to shield the antenna. Without any result. Disconnecting the antenna doesn´t show any effect either.
|
A:
According to the direct mode used, the gain of the analog chain can be quite high (direct FM mode). Therefore, some spikes will appear on DOUT and you will have to detect the presence of your transponder by detecting its start of frame or equivalent symbol (spikes will never appear during the reception of the transponder's load modulation).
The best way to reduce these spikes is to use the same register’s configuration as for the ISO15693 ASK (please refer to the datasheet page 22). This will configure the device in AM direct mode with a minimum gain of the analog chain.
Another thing can be the noise introduces by the VDD line. Therefore, please try to change the power supply block of the EVB90121 to see if it is better.
|
Q:
I recalculated the values for the input impedance and found that at 50 ohms the argument of the impedance shows an angle of -71°. I thought the impedance should be ohmic?
|
A:
The impedance of the antenna provided with the EVB90121 should be 50-ohm resistive at 13.56MHz with a quality factor of about 15.
The matching circuit can be adjusted with the timer capacitor C1.
|
Q:
Can I get information about the antenna which is part of the EVB90121? Where can I get it? What is the correct product number?
|
A:
The antenna of the EVB90121 is not available as a product. For further assistance, contact your Melaxis sales representative who can arrange applications assistance
|
Q:
We are currently designing antenna for 13.56MHz applications. The PCB antenna, supplied with the EVB90121, has a 0-50pf where the antenna can be tuned to 50ohms. We have noticed that the cirquit can not be tuned to a pure resistive impedance, but 50ohms either primary capacitive or primary inductive impedance. Which tuning of 50ohms gives the best match for the output on the EVB ?
Another question regarding the Q of the antenna. I've calced the Q to about 40 (takeing account for the parralel resistance of 1.8k and the series resistance of the inductor) but you mention that it's surpossed to be around 14 - how is the Q surpossed to be calculated ?
|
A:
The matching network of the RFID antenna provided with the DVK90121 is calculated to provide a 50-ohms resistive impedance at 13.56MHz. The 5 to 50pF adjustable capacitor is on the PCB only to fine adjust the variations of the tune capacitors. The antenna will be matched when a clear sinus of 10Vpp will be seen at the output of the EVB90121 (TP: Vant).
The quality factor of the antenna must be calculated using the current flowing though the inductance loop (3dB bandwidth at 13.56MHz). In this case, the calculations take also care about the matching network. The quality factor has been measured in transmission using a network analyzer.
|
Q:
Where can I get the complete list of ISO 15693 protocal commands?
|
A:
The complete list of protocol commands of the ISO/IEC 15693 are available through the ISO web site. The following links will bring you to the different parts of the protocol:
http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=30995
http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=39695
http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=31428
|
Q:
I need to measure the response time in reading a 15693 tag. How can I do it using the demo MLX90121 firmware?
|
A:
The response time between the request from the reader and the answer from the tag is specified in the ISO standard. There is no dedicated function to measure it in the demo 90121 firmware. As the Firmware is provided in C code with our development tools, it is easy to develop such a function.
|
Q:
If no sub carrier is sent the DOUT pin randomly sets HIGH and LOW, sometimes for less than 500ns, sometimes longer thant 5us. I am not able to detect a Start bit to start Majority voting.
Now what´s the problem with the IC? I took great care that the input on the RX pin matches your examples in the Application note "Support of different modulation modes" at page 8.
|
A:
This problem depends on the protocol used.
ISO15693 single subcarrier: DOUT must be stable and should not switch. If it does, you should try to modify the level of the comparator. If it doesn't help, contact us.
ISO14443A: DOUT must be stable and should not switch. If it does, you should try to modify the level of the comparator. If it doesn't help, contact us.
ISO14443B: For this protocol, MLX90121 require the use of a different internal decoder. In this case, SW filtering is necessary.
In order to help you, a software library is available in our development kit DVK90121. You will find example of implementation for all previously mentioned protocol. You will find more information on the document FW90121: "firmware for MLX90121 based reader"
The DVK90121 is available through our sales channel: www.melexis.com/contact.asp
|
Q:
I am using the EVB90121 with a power supply of 3V and measured a current consumption from 0,7mA (power down) to 100mA (transmitter on).
The MLX90121 datasheet specifies values between 0,1µA and 45mA so I am a little bit surprised about the high values I measured. Are they usual?
By the way, I used the antenna, which as included in the board.
|
A:
It seems to power consumption you have measured is for a power supply of 5Volt. Did you switch the jumper J3 to the position 2-3 (power supply selection)?
The power consumption in active mode (Field ON) is mainly due to the class-E power amplifier. Of course it may vary according to the tolerances of the external components (pull-up inductors, matching network, ...) but, should remain within the typical values of 80mA for 5Volts and 45mA for 3Volts.
In standby mode, please do not forget the power supply diodes D1 and D2 which consume some current (typically 0.7mA). To measure the real consumption of the device, you may have to disconnect the resistors R1 and R2.
|
Q:
Now that I knew my measured values were incorrect I made an new measurement. I problably forgot to change the jumper at my first measurement, because now I got the rigt values.
But the current consumption thoug is very variable, if you change the matching capacitances C1. But in the rigt position for communication I measured 2µA in standby mode, 0,96mA in low power mode and 46mA in transmission mode, so I am happy.
|
A:
By changing C1, you modify the load directly connected to the power supply and it has a direct impact on the power consumption.
|
Q:
I am using the PTC04 and the MPT to program a MLX90251 FA sensor. I am able to start the User Interface MLX90251 FA. I am also able to switch to the UI MLX90251 CC. When I do ReadEEprom for an FA-sensor, there is an error message: "This device is not recognized. The Software is unable to program this device". Could you please tell me how to solve this problem.
|
A:
First of al: Never use software for the MLX90251CC with samples of the MLX90251FA or visa versa. If you program devices with the wrong software you can make them unusable.
After Read EEPROM the software will check the EEPROM contend is valid or not. If EEPROM contend is not valid, the software returns an error message.
An unrecognised device is usually the cause of a bad connection between the PTC04 and the device. Check your connections. Perform a measure by ROM to check the IDD and the output of the device.
You can find more details on this topic in the document FAQ_PTC04. You can find this document on the CD delivered with the PTC04 or on softdist.
|
Q:
I have some problem to program your MLX90316 for my apps. Just SPI serial communication I needed. Could you show me the simple way or method to use SPI com?
|
A:
To program the Melexis MLX90316 it is necessary to have a Melexis PTC04 Programmer. The device can not be simply programmed via SPI. It requires specific hardware and software to safely access and set the various options.
Please contact your local Sales Representative for a quote and delivery on the necessary hardware.
|
Q:
How I can turn off warning "Current calibration has expired". Is there any DLL function regarding this warning?
|
A:
The function CheckSetup(bQuiet As Boolean), will search for a PTC-04 and also includes checking of communication channel validity, hardware revisions and specific parameters, software revisions as well as setting device specific parameters.
In case a check failed, the result will be a popup message if parameter bquit = false, or the returned value will be an error message without the popup if bquit = true and can then be validated with your software. Switching off some tests is not an option.
Please check the MPT_DEVELOPER_REFERENCE.HLP for more details.
What you can do is change the "next calibration date" that is stored in the EEPROM of the PTC-04. If you move the date 1 year, then the warning will also only come in 1 year.
Please note that every measurement tool should be calibrated on regular bases to guarantee good accuracy. Please check PTC04_UI for more details.
|
Q:
I am getting a fail indication for the PTC-04 when I test it. The BIN code is 311 and the TEST Main ID Serial Number is indicated. Also, I need a pinout description of the application connector on the rear of the PTC-04 (15-pin dsub).
|
A:
The HardWare ID in the EEPROM has been modified or corrupted. If this is the only error, the programmer should work OK.
You can repair it; select the "Configuration" button in the PTC-04 User Interface. The HW ID field should contain something like "03050007". This should be the same as the "Unit" number on the side of the programmer. You can modify the field and save it.
You can find the DB-15 pinout on the CD:
PTC04\Daughter_Board\Documentation\Ptc04_DB_Hall01_DataSheet.pdf
|
Q:
Question: I get this error when I try to read from the device: "PTC-04 received from the chip ACK/ERR=FFh while writing to address 0072h"
|
A:
Answer: Please refer to the "Get_Started_With_MLX90316.pdf" document.
This error usually indicates that there is a problem with the connection between the MLX90316 device and the PTC04 device connector.
On the CD, delivered with the PTC04, there is a document called "Get_Started_With_MLX90316.pdf".
STEP 1: Please check that all 4 requirements, described on page 1 of the document, are fulfilled.
STEP 2: Check your connection with the diagram on page 2 of the document.
STEP 3: To verify that the connections are OK: start the MPT UI of the 90316, go to the measurement screen of the UI and select Vout, Idd and Vdd.
For un-programmed 90316 parts the Vout = 7...8%, Idd = 6...10mA, Vdd=5V.
The "Get_Started_With_MLX90316" document can also be found on softdist, or on:
http://www.melexis.com
|
Q:
What is the installation procedure of the PTC04?
|
A:
Answer: for the installation procedure of the PTC04, please refer to the document: Installation_Guide_PTC04.pdf
This document can be found on the CD delivered with the PTC04 or at http://www.melexis.com
In a nutshell:
IMPORTANT: ALL INSTALLATIONS HAVE TO BE DONE WITH ADMINISTRATOR RIGHTS.
This means you need to have full access on your PC.
For the installation of the software, the PTC04 does NOT have to be connected to the PC. This is only necessary when you install the USB of the PTC04. If you want to use the USB of the PTC04, follow the procedure described in the chapter: Hardware: Question: How do I install the USB? You can install the USB before or after you install the software of the PTC04.
Installation from CD:
If you are installing the package from the CD, please follow the instructions
STEP 1: Start Autorun program from the CD.
STEP 2: Select the device you want to install. This will install the whole package. This means: if you select a MLX device, for example the MLX90251, all packages that are needed for the MLX90251 will be installed including the PTC04 modules. In this case it is not needed to select the PTC04 module afterwards.
STEP 3: Press Next > to install the module.
STEP 4: Select “I accept the agreement. And press
STEP 5: Next >
STEP 6: Press install.
STEP 7: Press Finish to complete the installation.
This procedure (step 3 – 6) is repeated for each module of the package automatically.
Installation from Package:
If you are not installing the package from the CD, please follow these instructions:
STEP 1: Put all software modules, except for the firmware, into one directory. The location of the directory on your PC is not important.
There are 6 software modules:
• 2 modules for the MLX product: (xxxxx = Melexis product number.)
o MLXxxxxx user interface (UI_0xxxxxAAMLX.exe)
o MLXxxxxx PSF (PSF0xxxxxAAMLX.exe)
For example:
MLX90251 user interface (UI_090251AAMLX.exe)
MLX90251 PSF (PSF090251AAMLX.exe)
• 2 modules for the PTC04:
o PTC04 user interface (UI_0PTC04AAMLX.exe)
o PTC04 PSF (PSF0PTC04AAMLX.exe)
• The MPT and the Melexis updater:
o MPT application (MPTApp.exe)
o Melexis Updater (MelexisUpdaterSetup.exe) - optional, the installation can be omitted. If this file is not in the directory, a warning is given and the installation is skipped.
STEP 2: Run the installation of the user interface (UI_0xxxxxAAMLX.exe).
For example: UI_090251AAMLX.exe.
This will install all other needed modules of the packages. The module is only installed if the previous installation has a lower revision number.
STEP 3: Press Next > to install the module.
STEP 4: Select “I accept the agreement. And press Next >
STEP 5: Press install.
STEP 6: Press Finish to complete the installation.
This procedure (step 3 – 6) is repeated for each module of the package automatically.
|
Q:
PTC04 cannot be recognized using “Search All” button of MPT.
|
A:
In order to run PTC04 user interface under MPT it is necessary to double-click on it under the workspace tree.
Figure 1: MPT
The software will search again the system for connected PTC04 programmer and will come up with a new dialog asking for manual selection of a serial port.
Figure 2: Comport selection
Select the correct port and click on “OK” button. Then PTC04 user interface must be active.
There are mainly two reasons leading to a similar malfunction:
1. An incompatible firmware has been uploaded into the PTC04 programmer. In such a case, please follow the instructions for Question: How do I upload the firmware of the PTC-04 starting from Step 2.
2. PTC04 main ID parameters have been overwritten. In such a case perform the following steps:
2.1. Click on “Firmware Commander” button
2.2. From the menu select System->MainID
2.3. Click on “Load” button.
2.4. Check if VID = 1001 and PID = 24832. If one of them is different correct it. Make sure that “HW Name” is “PTC04” as shown above.
2.5. Click on “Save” button. Wait 1-2 seconds until the data is written to the device.
2.6. Click again on “Load” button to ensure the data is correctly written.
Once both possible reasons are successfully fixed, you can try to do “Search All” again.
If the problem still exists, please contact Melexis support for further instructions.
|
Q:
When I try to connect with the PTC04 I get a warning message: “Daughter board is not recognized as PTC04-DB-xxxxxx. Do you wish to continue?”
|
A:
It is not advised to continue without proper verification of the Daughter Board that is plugged in the PTC04 Main Board.
STEP 1
If the plugged in Daughter Board is not of the required type, the software will not work properly.
The name of the DB plugged in the PTC04 MB can be verified with the UI of the PTC04.
If the type of DB doesn’t match with the required DB, it has to be replaced with the correct one.
STEP 1: Press on the “Configuration” Button in the User Interface PTC-04 window.
STEP 2: Press the “Load” Button on the Daughter Board Description window.
STEP 3: Verify if the HW Name matches with the requirements.
IMPORTANT: Do not change any other parameter of the Main Board Description. They are used by the software to identify the PTC04 as valid HW.
|
Q:
How do I install the USB?
|
A:
for the installation procedure of the USB, please refer to the document: Installation_Guide_USB.pdf
The installation procedure of the USB is described in the “Installation_Guide_USB.pdf” document. This document can be found on the CD delivered with the PTC04 or at http://www.melexis.com
In a nutshell:
STEP 1: Connect the PTC04 With the USB Port.
STEP 2: When the PTC04 programmer is plugged into the USB, Windows will ask automatically for a driver. Go to Step 6
STEP 3: If MS Windows doesn’t ask for a driver, go to the control panel of windows and select “System”.
STEP 4: In the window System Properties select “Device Manager”
STEP 5: Go to the Universal Serial Bus controllers at the bottom of the Device Manager window. Click with the right mouse button on the USB port with the exclamation mark “Melexis PTC04 universal programmer”. Select “update driver”.
STEP 6: Select “Install from a list or specific location” In the Hardware Update Wizard.
STEP 7: Press Next >
STEP 8: Select “Don’t search. I will choose the driver to install”.
STEP 9: Press Next >
STEP 10: Press “Have Disk”
STEP 11: Browse…
STEP 12: Go to ..:\CD_PTC04\PTC04\USB_Driver\FTDI_USB_VCP and select FTDIBUS.INF.
STEP 13: Press Open…
STEP 14: Press “OK”
STEP 15: Next >
STEP 16: If this message is shown press “Continue Anyway”
STEP 17: Finish…
STEP 18: After the USB driver is installed. A second USB ? Serial driver is installed automatically.
Also for this Windows will request a driver. Go to step 6.
STEP 19: If MS Windows doesn’t ask for a driver, go to the control panel of windows and select “System”.
STEP 20: In the window System Properties select “Device Manager”
STEP 21: Go to the Ports (COM <P) in the middle of the Device Manager window. Click with the right mouse button on the USB port with the exclamation mark “Melexis PTC04 USB Serial Port”. Select “update driver”. The rest of the procedure is identical. Got to step 6.
|
Q:
How do I upload the firmware of the PTC-04
|
A:
for instructions on how to upload the firmware of the PTC04, please refer to the document: PTC04_UI.pdf
This PTC04_UI.pdf document can be found on the CD delivered with the PTC04 or at:
http://www.melexis.com
In a nutshell:
The firmware loader is needed in order to upload new or other firmware into the PTC-04 programmer.
For most MLX products there is a specific firmware, PSF and UI for the PTC-04 programmer. Therefore it is important to have the correct firmware loaded in the PTC-04 programmer.
At start-up the PSF layer checks the ID and revision of the firmware that is loaded in the PTC-04. If the firmware doesn’t support the MLX product of the PSF, the PSF layer returns an error message.
In such a case you have to upload the correct firmware:
STEP 1: Start the User Interface of the PTC-04
STEP 2: Press the button Upload firmware
STEP 3: Select the firmware needed for your MLX product.
The firmware filename is called ptc04_mlx*****_firmware.hex or fir******aamlx.hex.
The marks ***** stand for the MLX product name.
For ex.: ptc04_mlx90251_firmware.hex or fir090264aamlx.hex.
Once the file is opened, the firmware is loaded in to the PTC-04 programmer. Afterwards the software verifies if the upload was done correctly.
|
Q:
Do I need a header file in order to use the DLL with C++?
|
A:
Every DLL has a built–in type library, which fully describes the objects and their interfaces implemented by the DLL. Every compiler, which supports ActiveX, is able to read this type information. In C++, the directive #import reads the specified type library and generates header file with definitions. This header file is also automatically included so you do not have to do #include for it.
Example:
#import "C:\Program Files\Melexis\MPT\MLX90316\MLX90316PSF.dll"
Imports MLX90316PSF type library and includes the generated header file.
|
Q:
I found some methods and properties which are not documented in the PSF0PTC04AAMLX.pdf. I need information about these methods and properties.
|
A:
the functions are described in the MPT_Development_Reference.HLP
These functions are indeed not described in the PTC04 PSF documentation. The functions are described in the MPT help file: MPT_Development_Reference.HLP. You can find the help file on the CD delivered with the PTC04, on softdist in the dir:..\PTC04_CD\Tools\MPT or on http://www.melexis.com
|
Q:
Error on RUN of PTC04 VB example Code
I have set up the code (in VB6) provided on page 8 of the "MLX90251 Product Specific Functions Software Library" programming guide. However when I try to run the program it errors on the following line: MsgBox (Dev.Name & " device found on " & Dev.Channel.Name) with the following message: "Object doesn't support this property or method" I have also adapted the code to VB.net and it errors at the same line: MsgBox(Dev.Name & " device found on " & Dev.Channel) but gives the following error message: "Attempted to read or write protected memory.”
|
A:
Public Dev As MLX90251PSFDevice
The function should work, but you need to make sure that "Dev" is linked to the 90251PSF. “Dev” is not declared on page 8 of the PSF documentation, but it is mandatory: It should be a global variable:
Public Dev As MLX90251PSFDevice
|
Q:
Warning message PTC04: Current calibration has expired
|
A:
for instructions on how to calibrate the PTC04, please refer to the document: User_Manual_Calibration_Software_PTC04.pdf
The instructions on how to calibrate the PTC04 and what is needed for the calibration are described in the “User_Manual_Calibration_Software_PTC04.pdf” document. This document can be found on the CD delivered with the PTC04, on softdist or at http://www.melexis.com
To preserve the accuracy of the PTC04, Melexis recommends checking the tolerance of the PTC04 once a year.
The PSF of the PTC04 has a Method “CheckSetup”. This method checks if the environment is supported by this object. This usually includes checking of communication channel validity, hardware revisions and specific parameters, software revisions as well as setting device specific parameters.
Also the calibration date of the PTC04 is checked by this method. If the calibration due date is exceeded, a warning message is given. This function is described in the MPT_Development_Reference.HLP. You can find the help file on the CD delivered with the PTC04, on softdist in the dir: ..\PTC04_CD\Tools\MPT or on http://www.melexis.com
When you do not use the PTC04 for your analogue measurements or when the PTC04 is used for programming Melexis devices with a digital output: The accuracy of the PTC04 is less critical for the calibration of MLX device.
However: it can have an impact on the communication with the MLX device over the lifetime of the PTC04.
The calibration of the PTC04 is not only done on the ADC. Also the DAC of the PTC04 is calibrated. The DAC is used to control the 4 PPS’s, Programmable Power Supplies, of the PTC04 programmer.
Most of the PTC protocols use the PPS’s to set the levels needed for the communication between the PTC04 and the MLX device. Some PTC protocols also use the ADC to read the response of the MLX device.
Although it is less critical: These types of PTC protocols require a well maintained PTC04 programmer to ensure a good communication between the PTC04 and the MLX device over the lifetime of the PTC04 programmer.
Postpone the calibration due date:
To postpone the calibration check of the PTC04, one can move the Next calibration date to a later date. The Next Calibration date is stored in the EEPROM of the PTC04 and can be accessed with the configuration tool of the PTC04 UI.
STEP 1: Press on the “Configuration” Button in the User Interface PTC-04 window.
Figure 6: PTC04 UI
STEP 2: First Press the “Load” Button on the Main Board Description window.
STEP 3: Modify the next calibration date to a later date.
STEP 4: Press the “Save” button.
IMPORTANT: Do not change any other parameter of the Main Board Description. They are used by the software to identify the PTC04 as valid HW.
Figure 7: Main Board Description.
|
Q:
I keep getting this error when I try to read from the device, and I have tried changing to another device, but still the same error.
"PTC-04 recieved from the chip ACK/ERR=FFh while writing to adress 0072h"
|
A:
1) On the CD there is a document called "getting started". Please check that all 4 requirements are fulfilled.
2) Please check your connection with the diagram on page 2.
3) To verify that the connections are OK, go to the measurement screen and select Vout , Idd and Vdd. For unprogrammed 90316 the Vout = 7..8%, Idd = 6..10mA, Vdd=5V.
Normally by now the problem should be solved.
|
Q:
Hi! 1, I'm using a PTC-04 programmer and it says: "Current calibration has expired" and I can't read the contents of the EEProm.
From what I heard I need a file named "MPT_DEVELOPER_REFERENCE.HLP" , but I don't have it. Please send me if you can!
2, And send me some basic initialization script if you have for the PTC-04 under MATLAB or Excel!
|
A:
The message "calibration date has expired"is just a warning. You should still be able to read the eeprom.
The file "MPT_DEVELOPER_REFERENCE.HLP" is on the cd PTC-04 / TOOLS / MPT / Documentation/...
There are also examples written in Excel / VB , see CD PTC-04 / projectnr / soft / application / excel
|
Q:
I want to use the PTC-04 via COM interface from MATLAB.
I found some methods and properties which are not documented in the PSF0PTC04AAMLX.pdf. I need imformation about these methods and properties.
Missing method documentationS (based on the latest downloadable version of PSF0PTC04AAMLX.pdf):
Activate = void Activate(handle, Variant)
CheckRevision = [bool, SafeArray
Pointer(Variant), int32] CheckRevision(handle, SafeArray Pointer(Variant), int32, Variant(Optional))
CheckSetup = void CheckSetup(handle, bool)
Destroy = void Destroy(handle, bool)
Free = void Free(handle, Variant(Optional))
GetAssetName = string GetAssetName(handle)
GetModuleRevision = [int32, int32]
GetModuleRevision(handle)
Load = void Load(handle, handle)
OnMessage = void OnMessage(handle, int32, Variant, handle)
Reset = void Reset(handle, Variant(Optional))
Save = void Save(handle, handle)
SetPortF = char SetPortF(handle, char, char)
Uninit = void Uninit(handle)
Missing property documentations (based on the latest downloadable version of PSF0PTC04AAMLX.pdf):
Connected
HasUI
|
A:
These functions are indeed not described in the PTC04 PSF documentation.
The functions are described in the MPT help file: MPT_Development_Reference.HLP. You can find the help file on softdist in the dir: ..\PTC04_CD\Tools\MPT
The function, SetPortF = char SetPortF(handle, char, char), is an internal Melexis function.
To control Port F, use the function: SetDBIO(unsigned char Data);
|
Q:
I installed Melexis programmable toolbox, with PTC04UI and MLX90251UI.
I tried to program a 90251F device, but the program answer is: 'Firmware is not recognized as 90251'
We have read in a previous discussion that by default the software is configured for the '90251CC' and that in order to change the devices we should modify the .ini file. Is it still correct?
At second point, in the Application note of PTC04-DBHall (Apr 04) shows the connector layout in a wrong way. It seems to be pin-changed (1-8, 2-7 and so on).
|
A:
For most MLX products there is a specific firmware, PSF and UI for the PTC-04 programmer. Therefore it is important to have the correct firmware loaded in the PTC-04 programmer.
At start-up the PSF layer checks the ID and revision of the firmware that is loaded in the PTC-04. If the firmware doesn’t support the MLX product of the PSF, the PSF layer returns an error message.
In such a case you have to upload the correct firmware:
Start the PTC04UI and press the upload firmware button ( or firmware commander) to upload the "ptc04_mlx90251_firmware.hex".
|
Q:
My company purchased PTC04 programmer tool with Hall sensor 90251 from your Melexis three month ago. The "Melexis Programmable Toolbox" (User Interface Software) can not find the PTC04 programmer hardware any more. When I use the menu selection Tools->Search Devices->All, a warning box pops up which shows that "No Melexis Devices were found during Scan". But When I used this tool before, it could find the devices very easily.
I have checked my operations. Power is on and connection Cable is linked. I have tried two kinds of cables.At first, I use RS232 cable, it did not work. Then I tried USB Cable. Computer could recognize the PTC04 hardware and installed the driver for it. But, in the "Melexis Programmable Toolbox" software, I still can not find the devices.
|
A:
When the MPT is started, the software automatically scans for the PTC-04 on all ports and reads the ID + Firmware version. If this fails you get the error "No Melexis Devices were found...". In your case it sound like the firmware is corrupted and does not fit with the requirements. You should try to reload the firmware and check for the “Main ID". Please use the following procedure:
- Switch OFF PTC-04 and connect RS232
- Start MPT
- Start user interface PTC-04. Press "Do not connect" in case you get a warning.
- Click on "Firmware commander"
- Switch ON PTC-04. Green LED will be ON
- Select Communication / connect / communications Port ( com x)
- Select Communication / Upload firmware and select the “ptc04_mlx90251_firmware.hex" from CD
- Select System / Main ID and click "Load". Verify the "contents of this hardware" with the "default". If it matches then the problem is solved. If it does not match click on "save defaults" and then click "load" again. If the contents still does not match the default then most likely the PTC-04 is damaged and should be send back to Melexis.
|
A:
|
Q:
I have purchased a new PTC04 programmer and I also have an older version PTC04. Now I have a problem when I use the new PTC04. I use PTC04 USB port to connect PC but it pops up a message windows "Unable to connect to a PTC04 programmer. User interface will be started in no-active mode. Reason: Communication error-time out." I use my old PTC04 set to connect this PC via USB port. It works fine. I re-installed PTC04 tools software and driver. It also can not connect to PC. Replaced with old PTC04. It also works fine. What happened?
|
A:
The windows USB driver needs to be installed before the Melexis software can recognize the PTC-04. This needs to be done for every USB device. Please check in the control panel / device manager if the hardware is recognized as PTC-04. Normally the first time you connect the PTC-04, windows should give a message "new hardware found” and install the driver.
- If possible try the RS232 connector and check if the new PTC-04 is OK.
|
Q:
I want to use the PCT04 as a pattern generator. The PSF0PTC04AAMLX.pdf file does not specify the units of time for the parameter "Value". what is the unit time?
The datasheet of the ptc04 refers to the instructionset of the ptc04. This is document is not to be fond on the cd delivered with the PTC04. where can i get this document?
|
A:
The pattern generator is using timings with a time unitof microseconds. The range is from 10 to 65535 so it results in 10us to 65ms.
Note:
The fact that the pattern generator is driving the Analog high current supplies, is limitting the speed. It make no sens to use signals faster then 10us
|
Q:
Where can I can get demo program for LabView "demo_90316_PTC04.vi"?
|
A:
There is a Labview example available on the CD PTC-04. Please check the directory:
CD_PTC04\MLX90316\Soft\application\labview
The example program demo90316BAD.exe was a development version, and only available as executable.
|
Q:
I am trying to set up VB code to interface with the PTC04 programmer so that I can create a custom programming HMI in VB.
I have set up the code (in VB6) provided on page 8 of the "MLX90251 Product Specific Functions Software Library" programming guide. However when I try to run the program it errors on the following line:
MsgBox (Dev.Name & " device found on " & Dev.Channel.Name)
with the following message:
"Object doesn't support this property or method"
I have also adapted the code to VB.net and it errors at the same line:
MsgBox(Dev.Name & " device found on " & Dev.Channel)
but gives the following error message:
"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
Does anybody have any insight into this problem.
|
A:
The function should work, but you need to make sure that "Dev"is linked to the 90251PSF.is not written on pag 8, but mandatory:
Public Dev As MLX90251PSFDevice
|
Q:
The PTC04_DB_Hall01_DataSheet.pdf document shows that 2 measurement instruments could be connected to the PTC-04 programmer at the same time. I use a safety-critical sensor with dual MLX90251. Can I communicate with the two chips without changing the connections from one sensor to the other? Device selector does nothing.
|
A:
The second connection on the PTC04_DB_HALL01 is only used for the MLX90277. It can not be used with the MLX90251.
The device selector is a software switch. It allows you to handle more than one device with the software. There are 16 virtual devices available. Every virtual device corresponds to a single die with separate cache for the EEPROM, independent Solver settings and Solver parameters.
The hardware switch has to be done externally by a MUX or relay.
Please check the topic: "MLX90251 and PTC04" for additional information and maybe an alternative solution to your question.
|