Most recent activity
-
- 39 comments
- 13,494 views
-
@Gordon I've attached the partial output from a trace() after the error occurred. This time it manifested itself in some debug code. Basically a i++ became i,+ but again in the same function.
(just noticed i<a.length also became k<a.length)The error is on line 917 of the file. I did a trace before the error occurred and the code was correct (I thought Closure may be corrupting something but that doesn't seem to be the case.)
I have no issues giving you the code but it would take a lot of setup to get it running (you would need an ILI9341 with touch & wiz5500io). Maybe there is something else I could try before that?
I'm unsure about the trace command - would it be worth doing a trace immediately before the error, then immediately after and doing a diff on them to see if there are more corruptions?
(I copied the trace output from the console, is there a better way - maybe a simple dos command to redirect the output from a com port to a file after ECHO trace() > COM5 ?)
I can reproduce the error in about 5 seconds of loading the program - basically a few clicks of the buttons on my ILI9341.
I tried to reproduce the error with less code but haven't managed to yet.
Hopefully i haven't done anything stupid since I don't want to waste your time!
EDIT: Just ran it again - this time:
Uncaught Error: Field or method does not already exist, and can't create it on undefined at line 1 col 48 ...i=0;i<a.length;i++)console.lpg(a.charCodeAt(i));return{x:a.c... ^
log became lpg. The error always seems to be 1 character out.
-
I've tried the latest 1v72 but identical error.I can consistently reproduce the error even after a reset & reload and after adding debug code, its always in the same block of code but it is slightly different each time. I honestly cant see anything wrong with the code (but I've been confident about that before yet wrong!!)
I'll try to investigate a bit more tonight.
-
Hi
All of a sudden I'm getting random code corruption/errors such as this:
Uncaught Error: Field or method does not already exist, and can't create it on undefined at line 1 col 64 ...deAt(1)+a.charCodeAt(2),w:a.charCodeBt(3),h:a.charCodeAt(4),..
As can be seen one of the charCodeAt statements has become charCodeBt !!!
Another example:
at line 1 col 26 {return{x:a.charCodeAt(0+,y:a.charCodeAt(1)+a.charCodeAt(2),...
The closing bracket has become a + symbol.
Maybe its just how the error is being displayed but I don't think so.
I happen to remember someone else having similar issues - was there ever a solution?
-
- 12 comments
- 6,701 views
-
I thought it would be fine since the pump is only 100W but I hadn't really considered the impact of an inductive load. The specs for the relay are:
General purpose 2 A, 240 VAC
Tungsten 1 A, 240 VAC
Motor 1.60 FLA/8.60 LRA, 240 VACI don't understand the FLA/LRA bit at all (I'm sure google knows!)
Maybe I should consider standard relays - I actually thought solid state would be better since the motor may produce arching at the contacts - I'm not sure if standard circulating pumps have snubbers (if that is the correct term).
The idea of using 5v is appreciated - I didn't know that could be done.
I could obviously just try things out and see how it works out but the last thing I want to do is fire up the boiler with no water circulating (I was considering putting a flow switch in so that the boiler would only turn on if water was circulating) but they are difficult to come across/expensive:
http://uk.farnell.com/gentech-international/fs-05/flow-switch-brass-ac-10bar/dp/1006768
EDIT: Just wondering - has anyone bought from China, I've been a bit dubious but are the sellers usually reliable (even if delivery is a bit slow)?
I've a 2nd wiznet so as a start I will swap them tonight, I'll also remove the solid state relay unit (which was switching a 240v 40w bulb but is not connected to the power supply at present). I've got a display without touch so could also swap that in.
One odd observation - I added some extra code last night to try and move the offending function into a different memory location but the error still occurs in the same place yet the code its now about 100 lines further down the trace. I thought the error may have occurred somewhere else.