1. Forum
  3. Search

Advanced Search

Search Results (Searched for: )

  • BaxEDM
  • BaxEDM's Avatar
16 Oct 2024 09:09
Replied by BaxEDM on topic motion.adaptive-feed range problem

motion.adaptive-feed range problem

Category: Advanced Configuration

Took a different work around / approach. Instead of requiring my customers to set a max expected feedrate in their G-code, my new feedback control will require them to always set the feedrate to F1000. This is then the highest feedrate used for retractions. My feed control component then does the scaling stuff and estimating the optimal FRO value. This works nicely.

I did run into show stopper performance issues after switching to 2.9.3 and bookworm, I'll start a new topic for that.
  • Aciera
  • Aciera's Avatar
16 Oct 2024 09:04
Replied by Aciera on topic Time to revisit coolant mapping of M-codes in Linuxcnc

Time to revisit coolant mapping of M-codes in Linuxcnc

Category: General LinuxCNC Questions

The issue at hand, the lack of NML commands is a problem that requires a lot of extra effort for every retrofit that could be solve once and be done with.


Just to give you an idea of what you may be up against (there is likely a fair bit more):
./src/emc/task/emccanon.cc:2344:void FLOOD_OFF()
./src/emc/task/emccanon.cc:2346:    EMC_COOLANT_FLOOD_OFF flood_off_msg;
./src/emc/task/emccanon.cc:2353:void FLOOD_ON()
./src/emc/task/emccanon.cc:2355:    EMC_COOLANT_FLOOD_ON flood_on_msg;
./src/emc/task/emccanon.cc:2811:int GET_EXTERNAL_FLOOD()
./src/emc/task/taskclass.cc:646:    EMC_COOLANT_FLOOD_ON floodOnMsg;
./src/emc/task/taskclass.cc:655:    EMC_COOLANT_FLOOD_OFF floodOffMsg;
./src/emc/task/emctaskmain.cc:938:	    case EMC_COOLANT_FLOOD_ON_TYPE:
./src/emc/task/emctaskmain.cc:939:	    case EMC_COOLANT_FLOOD_OFF_TYPE:
./src/emc/task/emctaskmain.cc:1051:		case EMC_COOLANT_FLOOD_ON_TYPE:
./src/emc/task/emctaskmain.cc:1052:		case EMC_COOLANT_FLOOD_OFF_TYPE:
./src/emc/task/emctaskmain.cc:1164:                case EMC_COOLANT_FLOOD_ON_TYPE:
./src/emc/task/emctaskmain.cc:1165:                case EMC_COOLANT_FLOOD_OFF_TYPE:
./src/emc/task/emctaskmain.cc:1228:		case EMC_COOLANT_FLOOD_ON_TYPE:
./src/emc/task/emctaskmain.cc:1229:		case EMC_COOLANT_FLOOD_OFF_TYPE:
./src/emc/task/emctaskmain.cc:1323:                case EMC_COOLANT_FLOOD_ON_TYPE:
./src/emc/task/emctaskmain.cc:1324:                case EMC_COOLANT_FLOOD_OFF_TYPE:
./src/emc/task/emctaskmain.cc:1393:	    case EMC_COOLANT_FLOOD_ON_TYPE:
./src/emc/task/emctaskmain.cc:1394:	    case EMC_COOLANT_FLOOD_OFF_TYPE:
./src/emc/task/emctaskmain.cc:1541:    case EMC_COOLANT_FLOOD_ON_TYPE:
./src/emc/task/emctaskmain.cc:1542:    case EMC_COOLANT_FLOOD_OFF_TYPE:
./src/emc/task/emctaskmain.cc:2048:    case EMC_COOLANT_FLOOD_ON_TYPE:
./src/emc/task/emctaskmain.cc:2052:    case EMC_COOLANT_FLOOD_OFF_TYPE:
./src/emc/task/emctaskmain.cc:2474:    case EMC_COOLANT_FLOOD_ON_TYPE:
./src/emc/task/emctaskmain.cc:2475:    case EMC_COOLANT_FLOOD_OFF_TYPE:
./src/emc/canterp/canterp.cc:29:  11 N0080  FLOOD_OFF()
./src/emc/canterp/canterp.cc:374:    if (!strcmp(the_command_name, "FLOOD_OFF")) {
./src/emc/canterp/canterp.cc:375:	FLOOD_OFF();
./src/emc/canterp/canterp.cc:384:    if (!strcmp(the_command_name, "FLOOD_ON")) {
./src/emc/canterp/canterp.cc:385:	FLOOD_ON();
./src/emc/rs274ngc/rs274ngc_pre.cc:2036:  _setup.flood = GET_EXTERNAL_FLOOD();
./src/emc/rs274ngc/rs274ngc_pre.cc:2198:        tag.flags[GM_FLAG_MIST] ? 7 : tag.flags[GM_FLAG_FLOOD] ? -1 : 9;
./src/emc/rs274ngc/rs274ngc_pre.cc:2200:        tag.flags[GM_FLAG_FLOOD] ? 8 : -1;
./src/emc/rs274ngc/interp_convert.cc:3537:      enqueue_FLOOD_ON();
./src/emc/rs274ngc/interp_convert.cc:3542:      enqueue_FLOOD_OFF();
./src/emc/rs274ngc/interp_convert.cc:4552:9. Coolant is turned off (like M9)                    - FLOOD_OFF & MIST_OFF
./src/emc/rs274ngc/interp_convert.cc:4679:      FLOOD_OFF();
./src/emc/rs274ngc/interp_namedparams.cc:79:    NP_FLOOD,
./src/emc/rs274ngc/interp_namedparams.cc:625:    case NP_FLOOD: // flood
./src/emc/rs274ngc/interp_namedparams.cc:911:  init_readonly_param("_flood", NP_FLOOD, PA_USE_LOOKUP);
./src/emc/rs274ngc/interp_queue.hh:19:                                QMIST_ON, QMIST_OFF, QFLOOD_ON, QFLOOD_OFF,
./src/emc/rs274ngc/interp_queue.hh:114:void enqueue_FLOOD_ON(void);
./src/emc/rs274ngc/interp_queue.hh:115:void enqueue_FLOOD_OFF(void);
./src/emc/rs274ngc/interp_queue.cc:132:void enqueue_FLOOD_ON(void) {
./src/emc/rs274ngc/interp_queue.cc:135:        FLOOD_ON();
./src/emc/rs274ngc/interp_queue.cc:139:    q.type = QFLOOD_ON;
./src/emc/rs274ngc/interp_queue.cc:144:void enqueue_FLOOD_OFF(void) {
./src/emc/rs274ngc/interp_queue.cc:147:        FLOOD_OFF();
./src/emc/rs274ngc/interp_queue.cc:151:    q.type = QFLOOD_OFF;
./src/emc/rs274ngc/interp_queue.cc:507:        case QFLOOD_ON:
./src/emc/rs274ngc/interp_queue.cc:509:            FLOOD_ON();
./src/emc/rs274ngc/interp_queue.cc:511:        case QFLOOD_OFF:
./src/emc/rs274ngc/interp_queue.cc:513:            FLOOD_OFF();
./src/emc/rs274ngc/gcodemodule.cc:460:void FLOOD_OFF() {}
./src/emc/rs274ngc/gcodemodule.cc:462:void FLOOD_ON() {}
./src/emc/rs274ngc/gcodemodule.cc:583:int GET_EXTERNAL_FLOOD() { return 0; }
./src/emc/rs274ngc/interp_write.cc:317:    state.flags[GM_FLAG_FLOOD] = (settings->flood);
./src/emc/rs274ngc/canonmodule.cc:123:    def("FLOOD_OFF",&FLOOD_OFF);
./src/emc/rs274ngc/canonmodule.cc:124:    def("FLOOD_ON",&FLOOD_ON);
./src/emc/rs274ngc/canonmodule.cc:134:    def("GET_EXTERNAL_FLOOD",&GET_EXTERNAL_FLOOD);
./src/emc/rs274ngc/canonmodule.cc:256:    def("enqueue_FLOOD_ON", &enqueue_FLOOD_ON);
./src/emc/rs274ngc/canonmodule.cc:257:    def("enqueue_FLOOD_OFF", &enqueue_FLOOD_OFF);
./src/emc/motion/state_tag.h:51:    GM_FLAG_FLOOD,
./src/emc/nml_intf/emc.hh:219:#define EMC_COOLANT_FLOOD_ON_TYPE                    ((NMLTYPE) 1406)
./src/emc/nml_intf/emc.hh:220:#define EMC_COOLANT_FLOOD_OFF_TYPE                   ((NMLTYPE) 1407)
./src/emc/nml_intf/canon.hh:647:extern void FLOOD_OFF();
./src/emc/nml_intf/canon.hh:649:extern void FLOOD_ON();
./src/emc/nml_intf/canon.hh:785:extern int GET_EXTERNAL_FLOOD();
./src/emc/nml_intf/emc.cc:141:    case EMC_COOLANT_FLOOD_OFF_TYPE:
./src/emc/nml_intf/emc.cc:142:	((EMC_COOLANT_FLOOD_OFF *) buffer)->update(cms);
./src/emc/nml_intf/emc.cc:144:    case EMC_COOLANT_FLOOD_ON_TYPE:
./src/emc/nml_intf/emc.cc:145:	((EMC_COOLANT_FLOOD_ON *) buffer)->update(cms);
./src/emc/nml_intf/emc.cc:544:    case EMC_COOLANT_FLOOD_OFF_TYPE:
./src/emc/nml_intf/emc.cc:545:	return "EMC_COOLANT_FLOOD_OFF";
./src/emc/nml_intf/emc.cc:546:    case EMC_COOLANT_FLOOD_ON_TYPE:
./src/emc/nml_intf/emc.cc:547:	return "EMC_COOLANT_FLOOD_ON";
./src/emc/nml_intf/emc.cc:2555:*	NML/CMS Update function for EMC_COOLANT_FLOOD_OFF
./src/emc/nml_intf/emc.cc:2559:void EMC_COOLANT_FLOOD_OFF::update(CMS * cms)
./src/emc/nml_intf/emc.cc:2695:*	NML/CMS Update function for EMC_COOLANT_FLOOD_ON
./src/emc/nml_intf/emc.cc:2699:void EMC_COOLANT_FLOOD_ON::update(CMS * cms)
./src/emc/nml_intf/emc_nml.hh:1942:class EMC_COOLANT_FLOOD_ON:public EMC_COOLANT_CMD_MSG {
./src/emc/nml_intf/emc_nml.hh:1944:    EMC_COOLANT_FLOOD_ON():EMC_COOLANT_CMD_MSG(EMC_COOLANT_FLOOD_ON_TYPE,
./src/emc/nml_intf/emc_nml.hh:1946:					       (EMC_COOLANT_FLOOD_ON)) {
./src/emc/nml_intf/emc_nml.hh:1953:class EMC_COOLANT_FLOOD_OFF:public EMC_COOLANT_CMD_MSG {
./src/emc/nml_intf/emc_nml.hh:1955:    EMC_COOLANT_FLOOD_OFF():EMC_COOLANT_CMD_MSG(EMC_COOLANT_FLOOD_OFF_TYPE,
./src/emc/nml_intf/emc_nml.hh:1957:						(EMC_COOLANT_FLOOD_OFF)) {
./src/emc/iotask/ioControl_v2.cc:1223:        case EMC_COOLANT_FLOOD_ON_TYPE:
./src/emc/iotask/ioControl_v2.cc:1224:            rtapi_print_msg(RTAPI_MSG_DBG, "EMC_COOLANT_FLOOD_ON\n");
./src/emc/iotask/ioControl_v2.cc:1229:        case EMC_COOLANT_FLOOD_OFF_TYPE:
./src/emc/iotask/ioControl_v2.cc:1230:            rtapi_print_msg(RTAPI_MSG_DBG, "EMC_COOLANT_FLOOD_OFF\n");
./src/emc/iotask/ioControl.cc:1071:        case EMC_COOLANT_FLOOD_ON_TYPE:
./src/emc/iotask/ioControl.cc:1072:            rtapi_print_msg(RTAPI_MSG_DBG, "EMC_COOLANT_FLOOD_ON\n");
./src/emc/iotask/ioControl.cc:1077:        case EMC_COOLANT_FLOOD_OFF_TYPE:
./src/emc/iotask/ioControl.cc:1078:            rtapi_print_msg(RTAPI_MSG_DBG, "EMC_COOLANT_FLOOD_OFF\n");
grep: ./src/emc/usr_intf/gmoccapy/__pycache__/gmoccapy.cpython-310.pyc: binary file matches
./src/emc/usr_intf/gmoccapy/gmoccapy.py:4122:            self.command.flood(linuxcnc.FLOOD_ON)
./src/emc/usr_intf/gmoccapy/gmoccapy.py:4125:            self.command.flood(linuxcnc.FLOOD_OFF)
./src/emc/usr_intf/axis/extensions/emcmodule.cc:57:#define LOCAL_FLOOD_ON (1)
./src/emc/usr_intf/axis/extensions/emcmodule.cc:58:#define LOCAL_FLOOD_OFF (0)
./src/emc/usr_intf/axis/extensions/emcmodule.cc:1051:        case LOCAL_FLOOD_ON:
./src/emc/usr_intf/axis/extensions/emcmodule.cc:1053:            EMC_COOLANT_FLOOD_ON m;
./src/emc/usr_intf/axis/extensions/emcmodule.cc:1057:        case LOCAL_FLOOD_OFF:
./src/emc/usr_intf/axis/extensions/emcmodule.cc:1059:            EMC_COOLANT_FLOOD_OFF m;
./src/emc/usr_intf/axis/extensions/emcmodule.cc:1064:            PyErr_Format(PyExc_ValueError,"FLOOD should be FLOOD_ON or FLOOD_OFF");
./src/emc/usr_intf/axis/extensions/emcmodule.cc:2471:    ENUMX(6, LOCAL_FLOOD_ON);
./src/emc/usr_intf/axis/extensions/emcmodule.cc:2472:    ENUMX(6, LOCAL_FLOOD_OFF);
./src/emc/usr_intf/shcom.cc:674:    EMC_COOLANT_FLOOD_ON emc_coolant_flood_on_msg;
./src/emc/usr_intf/shcom.cc:688:    EMC_COOLANT_FLOOD_OFF emc_coolant_flood_off_msg;
./src/emc/usr_intf/stepconf/build_HAL.py:198:        if SIG.FLOOD in outputs:
./src/emc/usr_intf/stepconf/stepconf.py:177:            self.MIST, self.FLOOD, self.ESTOP, self.AMP,
grep: ./src/emc/usr_intf/stepconf/__pycache__/stepconf.cpython-310.pyc: binary file matches
grep: ./src/emc/usr_intf/stepconf/__pycache__/build_HAL.cpython-310.pyc: binary file matches
./src/emc/usr_intf/pncconf/private_data.py:177:            S.MIST,S.FLOOD,S.ESTOP,S.AMP,
grep: ./src/emc/usr_intf/pncconf/__pycache__/private_data.cpython-310.pyc: binary file matches
./src/emc/usr_intf/halui.cc:1096:    EMC_COOLANT_FLOOD_ON emc_coolant_flood_on_msg;
./src/emc/usr_intf/halui.cc:1103:    EMC_COOLANT_FLOOD_OFF emc_coolant_flood_off_msg;
./src/emc/usr_intf/emcrsh.cc:480:  "TIME", "ESTOP", "MACHINE", "MODE", "MIST", "FLOOD", "LUBE", "LUBE_LEVEL",
./src/emc/usr_intf/emcrsh.cc:1629:  const char *pFloodStr = "FLOOD %s";
./src/emc/sai/saicanon.cc:617:void FLOOD_OFF()
./src/emc/sai/saicanon.cc:619:  PRINT("FLOOD_OFF()\n");
./src/emc/sai/saicanon.cc:623:void FLOOD_ON()
./src/emc/sai/saicanon.cc:625:  PRINT("FLOOD_ON()\n");
./src/emc/sai/saicanon.cc:748:int GET_EXTERNAL_FLOOD()

Consider the effort it would take to expand that against spending maybe an hour to create a new Mcode remap for a more granular coolant handling and adding a filter script to change the PP output to the new Mcode (or adjusting the PP itself).
  • snowgoer540
  • snowgoer540's Avatar
16 Oct 2024 08:12
Replied by snowgoer540 on topic හොඳ යාළුවෝ

හොඳ යාළුවෝ

Category: Other Languages

Spam removed
  • Aciera
  • Aciera's Avatar
16 Oct 2024 07:31
Replied by Aciera on topic 6DOF robot Limit Issues

6DOF robot Limit Issues

Category: Advanced Configuration

Yes

You can watch the current commanded joint position in the 'halshow' tool under:
'joint.N.motor-pos-cmd'
Where 'N' denotes the joint number (ie 1 for the joint in question).
  • xenon-alien
  • xenon-alien's Avatar
16 Oct 2024 07:09 - 16 Oct 2024 07:59
Replied by xenon-alien on topic Tool in spindle memory

Tool in spindle memory

Category: General LinuxCNC Questions

Hello.
The random tool changer works, remembers the last tool (after adding the 5400 variable in the .var file).
One question is left.
How to put the tool in spindle in an empty pocket? (if needed)
T0 M6 - not helps. (as usually in manual tool change)
In the tool table there is no T0 P0 line...

Helped:
Added In the tool table the T0 P0 line
Changed the toolchange.ngc
O100 IF [#<selected_tool> GT 0]
to
O100 IF [#<selected_tool> GE 0]
 
  • Muecke
  • Muecke's Avatar
16 Oct 2024 05:29
Replied by Muecke on topic Customization of the icon for the LinuxCNC website

Customization of the icon for the LinuxCNC website

Category: Forum Questions

I have just seen in the source code that the icon is somewhere else.
<link href="[url=view-source:https://forum.linuxcnc.org/templates/protostar/favicon.ico]/templates/protostar/favicon.ico[/url]" rel="shortcut icon" type="image/vnd.microsoft.icon" />
  • Muecke
  • Muecke's Avatar
16 Oct 2024 05:25
Replied by Muecke on topic Customization of the icon for the LinuxCNC website

Customization of the icon for the LinuxCNC website

Category: Forum Questions

JT post=312188 userid=32471]
The guy that pays for hosting is not around but he still pays for it. I don't have any contact information for him. I do have access to the forum host admin.


It is very commendable that the person continues to finance the hosting, but this is also a risky situation. If the server goes down, it would be difficult to restore it without direct contact.

Perhaps we could contact the provider and ask them to forward an email to the operator? A suggestion for the message could read like this:

‘Dear Sponsor, we appreciate you continuing to sponsor the hosting of the web server. However, a lot has changed in recent years and we would like to update the system. However, we are missing certain credentials (usernames and passwords) to do this. We would like to politely ask you if you are in possession of this data and could provide us with access if necessary.

Our aim is to bring the website (linuxcnc.org/), the wiki and the forum up to date and to ensure that everything works without errors.

We would be very pleased to receive positive feedback.

JT post=312188 userid=32471]Ok that is what filled up the disk space... it needs to be off loaded as we are at 95% now. 

If you mean the storage space on the server, I assume (my English is not perfect, but if I have understood the hoster correctly) that we will be permanently at about 95%. The hoster dynamically provides exactly as much memory as is currently needed and automatically expands it as required.

Nevertheless, it would be helpful to know how many GB of memory we are currently using. Of course, a little tidying up never hurts!
  • sameedansar
  • sameedansar
16 Oct 2024 04:08
Replied by sameedansar on topic I'm trying to install LinuxCNC on Ubuntu 20.04 arm64 and encountering some issue

I'm trying to install LinuxCNC on Ubuntu 20.04 arm64 and encountering some issue

Category: Installing LinuxCNC

Could you please explain how to download linuxcnc 2.9 on ubuntu 20.04? The whole process if possible
  • foam man
  • foam man
16 Oct 2024 03:20
Replied by foam man on topic controller and motors not fully communicating

controller and motors not fully communicating

Category: General LinuxCNC Questions

  In this box? 
  • okielaxplyr
  • okielaxplyr
16 Oct 2024 02:06
PNCconfig error was created by okielaxplyr

PNCconfig error

Category: General LinuxCNC Questions

I have encountered this error after restarting a configuration in PNCconfig. I have attached a screen shot. 
Please advise on how to proceed.

Regards

John
  • spumco
  • spumco
16 Oct 2024 01:47
Replied by spumco on topic Time to revisit coolant mapping of M-codes in Linuxcnc

Time to revisit coolant mapping of M-codes in Linuxcnc

Category: General LinuxCNC Questions

are you at liberty to share those mappings ? 

They're just basic xxx.ngc subroutine files, specified in the INI file. Not an actual remap of an existing M-code with new behavior and -P/-Q passthrough params.
[RS274NGC]
PARAMETER_FILE = lathe.var
USER_M_PATH = /home/lathe/linuxcnc/configs/LATHE_REV1.53/MCODES/
SUBROUTINE_PATH = /home/lathe/linuxcnc/configs/LATHE_REV1.53/subroutines
RS274NGC_STARTUP_CODE = F10 S0 G7 G18 G20 G40 G49 G54 G64 P0.001 G80 G90 G91.1 G92.1 G94 G97 G98
;ORIENT_OFFSET =
#REMAP=G12.1 ngc=g121
#REMAP=G13.1 ngc=g131
REMAP=M200  modalgroup=10   ngc=m200
REMAP=M201  modalgroup=10   ngc=m201
REMAP=M202  modalgroup=10   ngc=m202
REMAP=M203  modalgroup=10   ngc=m203
REMAP=M210  modalgroup=10   ngc=m210
REMAP=M211  modalgroup=10   ngc=m211
REMAP=M212  modalgroup=10   ngc=m212
REMAP=M213  modalgroup=10   ngc=m213
REMAP=M220  modalgroup=10   ngc=m220
REMAP=M221  modalgroup=10   ngc=m221
REMAP=M222  modalgroup=10   ngc=m222
REMAP=M223  modalgroup=10   ngc=m223
REMAP=M268  modalgroup=10   ngc=m268
REMAP=M269  modalgroup=10   ngc=m269

M210 to M213 are my extra mist valves.  Subroutines look like this:
o<m210> sub

;MIST 2 ON

;MIST2 VALVE             motion.digital-out-00
;MIST3 VALVE             motion.digital-out-01

M64 P0                                  ;TURN ON MIST2 VALVE

o<m210> endsub [1]
M2

The other ones are main and sub drawbars, and 268/269 are G10 front/back tool rotations (hoping to incorporate that in post processor so the display automatically flips to the right orientation).

I could have mapped them to a more logical M-code number... Maybe I'll see if m207.1.ngc & m207.2.ngc work and not cause LCNC to vomit.
  • acourtjester
  • acourtjester
16 Oct 2024 01:22
Replied by acourtjester on topic Parse Error

Parse Error

Category: General LinuxCNC Questions

Thanks for you time Phill The tool numbers were generated by the sequence they were created in SheetCam. As it sits now it is usable for me to do work. As I assume the bit size and positions (inside, out side, and one the line) should be kept correct by SheetCam and EstlCam. This should keep the dimensional size correct for my projects.
your statement

This is all using the axis_mm sim config.
does that mean I need to use metric measurements or is there an inch version??
  • Benb
  • Benb's Avatar
16 Oct 2024 00:47 - 16 Oct 2024 01:24
Replied by Benb on topic linuxcnc-dev is missing?

linuxcnc-dev is missing?

Category: Installing LinuxCNC

Couple of months ago I installed Linuxcnc rip on an intel i5 4the generation it installed flowlesslly. Try not to skip any steps, take your time don't rush otherwise you will have start all over again.
[edit] OOPS just realized that you loaded linuxcnc. You must start with Debian 12 os only nothing else. 
  • phillc54
  • phillc54's Avatar
16 Oct 2024 00:06
Replied by phillc54 on topic Parse Error

Parse Error

Category: General LinuxCNC Questions

This is all using the axis_mm sim config.
Downloaded your zip file 4washersLinuxcnc.zip and extracted the contents.
Created a tool #23.
Loaded 4washersLinuxcnc.tap which gave a parse_file interp_error.
Duplicated 4washersLinuxcnc.tap and renamed it 4washersLinuxcnc.ngc
Loaded 4washersLinuxcnc.ngc which gave a parse_file interp_error.
Created several tools, #9, #10, #19, #20.
Changing tool numbers in the files and then loading the files showed that tool numbers greater than #9 always gave a parse error and tools #9 and below mostly loaded without error.
I did see that your file had dos style line endings so I changed that to unix style and it made no difference to the above.

The above makes no sense to me and is all I have time for at the moment.
​​​​​​​
  • kennetek
  • kennetek
15 Oct 2024 23:47
Replied by kennetek on topic Axes no longer home/move

Axes no longer home/move

Category: General LinuxCNC Questions

I checked every STEP-/STEP+ and DIR+/DIR- pair, there was no meaningful potential between any of them. I only checked STEP0- and DIR0- relative to GND and no meaningful change when jogging. I guess that means both are shot.

Replacing those two chips should not be too hard. I don't like that I don't know what caused the failure, I guess maybe some chip shorted it, since I have not messed with the electrical system in a while. I don't know how that would damage both chips, though.

Also, what are the overheating signs on U7? Is it that blob covering the 5?
Displaying 20056 - 20070 out of 24222 results.
  1. Forum
  3. Search
Time to create page: 0.417 seconds
Powered by Kunena Forum