There will be soon firmware for this character OLED too, available for purchase in EU:
Winstar WEH001602A Ecran Oled 16x2 blanc HD44780 - Audiophonics
You would still need to purchase SPI to I2C module though:
10pcs IIC I2C TWI SPI Serial Interface Board Port For arduno 1602 2004 LCD LCD1602 Adapter Plate LCD Adapter Converter Module|Connectors| - AliExpress
Winstar WEH001602A Ecran Oled 16x2 blanc HD44780 - Audiophonics
You would still need to purchase SPI to I2C module though:
10pcs IIC I2C TWI SPI Serial Interface Board Port For arduno 1602 2004 LCD LCD1602 Adapter Plate LCD Adapter Converter Module|Connectors| - AliExpress
Neb,
I did a little googling on avrdude and there appears to be a freeware distribution of the program that is independent of arduino that could be adapted to your distribution. My concern was that following the directions and/or examples you provided with your .hex distribution the new version could not be installed. Given that your product seems to fall into that grey area between a commercial product and DYI group buy, I would expect better documentation and/or software tools to be provided.
Regards,
Roy
I did a little googling on avrdude and there appears to be a freeware distribution of the program that is independent of arduino that could be adapted to your distribution. My concern was that following the directions and/or examples you provided with your .hex distribution the new version could not be installed. Given that your product seems to fall into that grey area between a commercial product and DYI group buy, I would expect better documentation and/or software tools to be provided.
Regards,
Roy
I hear you. I have tested firmware upload on a virgin win10 vm and it does fail without libusb0.dll. Adding this file fixed the issue, could it be that simple? I don't know, but now I included this dll in the firmware folder.
Right channel low output / calibration issue?
Hi,
I've just built up this board and am having issues with a very low output on the right channel. Seems to be almost no output until I turn the volume to max, which then outputs the full signal.
I had no errors in initial startup and all the LDRs measure similarly between 30-50R (I've replaced them all just to make sure but no change).
I've run calibration several times with all the prerequisites met (bias, parameters etc), but the issue persists.
Any ideas as to what could be causing this?
Appreciate any help, Cheers
Hi,
I've just built up this board and am having issues with a very low output on the right channel. Seems to be almost no output until I turn the volume to max, which then outputs the full signal.
I had no errors in initial startup and all the LDRs measure similarly between 30-50R (I've replaced them all just to make sure but no change).
I've run calibration several times with all the prerequisites met (bias, parameters etc), but the issue persists.
Any ideas as to what could be causing this?
Appreciate any help, Cheers
Any new build should be checked for:
1) soldering errors
2) component value errors
If one channel is ok, compare it to non working one with multimeter. Can the BIAS be adjusted for all LDRs?
1) soldering errors
2) component value errors
If one channel is ok, compare it to non working one with multimeter. Can the BIAS be adjusted for all LDRs?
Hi,
I've checked all values and continuity, they're the same on both channels. Relays and mosfets seem to be operating fine. Added a cap to c30 just in case. Also went over all the solder points with an iron again to make sure.
I can adjust bias for all LDR's to 700-800k. They drift a bit between calibrations but stay within the 600-850k range.
Calibration seems to slow down considerably between shunt steps 6-11 (takes around 10 minutes, total calibration time around 18 mins) then speeds back up. TX LED on the nano also turns on and stays green when i select volume level 50 (where i get full output from the defective channel).. not sure if this means anything.
I've checked all values and continuity, they're the same on both channels. Relays and mosfets seem to be operating fine. Added a cap to c30 just in case. Also went over all the solder points with an iron again to make sure.
I can adjust bias for all LDR's to 700-800k. They drift a bit between calibrations but stay within the 600-850k range.
Calibration seems to slow down considerably between shunt steps 6-11 (takes around 10 minutes, total calibration time around 18 mins) then speeds back up. TX LED on the nano also turns on and stays green when i select volume level 50 (where i get full output from the defective channel).. not sure if this means anything.
Hi, is it possible to replace ir codes so we are not stuck to apple remote? Especially on off button that is long press is problematic for implementation to homeassistant.
thanks
thanks
Neb,
I am attempting to calibrate a MK II board and getting an error message that doesn’t seem related to the problem. This board is from your first production run (without C30 and the four output power supply). The board comes up in the configuration menu. After adjusting the bias, measuring all LDRs and setting values I run configuration. During self-test I receive the following error message:
Error 10
LSE to Low
Adjust RT1
I attempted readjustment several times without a change in result. In all cases the measured values were within the appropriate range. Since I had found RT1 to be a little flaky during adjustment, I replaced it with no change in results. I then went on and changed the op amp and the LDR. I also reworked the solder around all three relays on the right side and reworked all the solder joints in the circuits around LSE. Still no change in behavior.
Could you suggest any other area that might produce this error message? Everything seems to be working properly and measures properly until it gets to calibration.
Initially, I did have problems with display instability using one of your recommended boards (wide.hk). I tried two different displays. This happened on both my MK II boards. Interestingly, it doesn't happen at all or my two Mk I boards using the same display. I resolved the issue by placing a 680 uF cap in the 5V and ground holes on the right-hand side. I had the same behavior with both boards. The other board I was able to put in production without issue, so I don't necessarily believe the issue has anything to do with display instability. I do find it a bit problematic however, that the displays that are stable on the mark I boards have issues on the mark II boards.
Any ideas?
Regards,
Roy
I am attempting to calibrate a MK II board and getting an error message that doesn’t seem related to the problem. This board is from your first production run (without C30 and the four output power supply). The board comes up in the configuration menu. After adjusting the bias, measuring all LDRs and setting values I run configuration. During self-test I receive the following error message:
Error 10
LSE to Low
Adjust RT1
I attempted readjustment several times without a change in result. In all cases the measured values were within the appropriate range. Since I had found RT1 to be a little flaky during adjustment, I replaced it with no change in results. I then went on and changed the op amp and the LDR. I also reworked the solder around all three relays on the right side and reworked all the solder joints in the circuits around LSE. Still no change in behavior.
Could you suggest any other area that might produce this error message? Everything seems to be working properly and measures properly until it gets to calibration.
Initially, I did have problems with display instability using one of your recommended boards (wide.hk). I tried two different displays. This happened on both my MK II boards. Interestingly, it doesn't happen at all or my two Mk I boards using the same display. I resolved the issue by placing a 680 uF cap in the 5V and ground holes on the right-hand side. I had the same behavior with both boards. The other board I was able to put in production without issue, so I don't necessarily believe the issue has anything to do with display instability. I do find it a bit problematic however, that the displays that are stable on the mark I boards have issues on the mark II boards.
Any ideas?
Regards,
Roy
It's very possible that error is not related to the problem. Errors are used to provide insight about adjustments and power related issues for fully working boards, and not for troubleshooting hardware related errors.
When the error is displayed, what is the resistance value of respective LDR?
When the error is displayed, what is the resistance value of respective LDR?
Neb,
With regards to this error message:
Error 10
LSE to Low
Adjust RT1
I have two boards, one that works properly and one that receives the error message running configuration.
Checked LDR resistance on my problem board and the one that ran configuration correctly. On the problem board that boots to the configuration menu, all LDRs measure approximately 20 to 25R higher than their “normal” values at startup. On the “good” board, that boots to standby, the LDRs, when put directly into configuration mode, are all in the multi-K range. I do not think that necessarily means anything since they have different starting conditions.
On the problem board, if I go to the “Measure LDR” menu first, the LDRs remain at 20-25R higher than normal; however, if I switch to the “Measure Bias” menu and then switch back to the “Measure LDR” menu, the LDRs are at their “normal” value.
There is one anomaly on the problem board that I think is relevant. On the LDR that generates the error message (LSE) the bias value does not change with warmup. I set it to around 700K and it stays there. The other 7 LRDs, work their way down from about 1 to 1.5M to their adjusted value of approximately 700K. They decline and reach general stability in around 10-15 minutes but will still go down another 100K in the next 45 minutes. To me that seems like a defective active component in the circuit around the problem LDR, but I have already replaced the FDV301N for that LDR.
Does this give you anything to work with?
Thanks,
Roy
With regards to this error message:
Error 10
LSE to Low
Adjust RT1
I have two boards, one that works properly and one that receives the error message running configuration.
Checked LDR resistance on my problem board and the one that ran configuration correctly. On the problem board that boots to the configuration menu, all LDRs measure approximately 20 to 25R higher than their “normal” values at startup. On the “good” board, that boots to standby, the LDRs, when put directly into configuration mode, are all in the multi-K range. I do not think that necessarily means anything since they have different starting conditions.
On the problem board, if I go to the “Measure LDR” menu first, the LDRs remain at 20-25R higher than normal; however, if I switch to the “Measure Bias” menu and then switch back to the “Measure LDR” menu, the LDRs are at their “normal” value.
There is one anomaly on the problem board that I think is relevant. On the LDR that generates the error message (LSE) the bias value does not change with warmup. I set it to around 700K and it stays there. The other 7 LRDs, work their way down from about 1 to 1.5M to their adjusted value of approximately 700K. They decline and reach general stability in around 10-15 minutes but will still go down another 100K in the next 45 minutes. To me that seems like a defective active component in the circuit around the problem LDR, but I have already replaced the FDV301N for that LDR.
Does this give you anything to work with?
Thanks,
Roy
Source code is now posted to my google drive folder.
It's not just a simple matter of having a source code, you will need to know how to compile it. You need minicore lib for a start:
https://mcudude.github.io/MiniCore/package_MCUdude_MiniCore_index.json
Then you need to modify boards file to connect to UART1 instead of UART0 (default), since my arduino boards are using UART1.
I will not be around to offer help with this, you need to do your homework.
It's not just a simple matter of having a source code, you will need to know how to compile it. You need minicore lib for a start:
https://mcudude.github.io/MiniCore/package_MCUdude_MiniCore_index.json
Then you need to modify boards file to connect to UART1 instead of UART0 (default), since my arduino boards are using UART1.
I will not be around to offer help with this, you need to do your homework.
Folks, v1.19 with dual encoder support has a broken calibration. No idea how yet, since it's the same calib routine as in 1.17, could be related to interrupts for second encoder. Use v1.17 for now.
With another lockdown in sight, it's a good time for upgrades🙂 I have one fully completed MkI version for sale with character OLED, going for the price of parts, preferably to EU destinations.